HackerTrans
TopNewTrendsCommentsPastAskShowJobs

jefecoon

no profile record

comments

jefecoon
·letzten Monat·discuss
class action lawsuit?

maybe i'll eventually get a settlement for my multiple Office Mac licenses that won't buy me a latte. what a joke.

note to self: never buy anything from MSFT ever again.
jefecoon
·vor 5 Monaten·discuss
Here's my workflow, hopefully concise enough as a reply, in case helpful to those very few who'll actually see it:

Research -> Define 'Domains' -> BDD -> Domain Specs -> Overall Arch Specs / complete/consistent/gap analysis -> Spec Revision -> TDD Dev.

Smaller projects this is overkill. Larger projects, imho, gain considerable value from BDD and Overall Architecture Spec complete/consistent/gap analysis...

Cheers
jefecoon
·vor 7 Monaten·discuss
I'm impressed by the depth of snark from GPro3 here, e.g. - Google kills Gemini Cloud Services (killedbygoogle.com) - The unexpected return of server-side rendering (htmx.org)

And, how GPro3 clearly 'knows' HNews and knows what makes it to frontpage, e.g.: - Restoring a 2024 Framework Laptop: A retrospective (ifixit.com) - Show HN: A text editor that doesn't use AI (github.com) - Is it time to rewrite sudo in Zig? (github.com)

Good laughs.
jefecoon
·vor 11 Monaten·discuss
Nice read, and beautiful website btw.
jefecoon
·vor 2 Jahren·discuss
Few misc thoughts here: - Lawyers want this all to work in Word.docx

- Many [ / most? ] law firms have a large, overly-complicated "doc database." These have Word plugins, and they're usually required to 'check-in' each version they prepare prior to sending out. This seems like a very natural point of attack for a dramatically superior git-esque solution.

- Most lawyers / firms have a massive distrust of cloud-hosted tools. I've heard "well, Google can read everything in Google Docs!" more times than I can count. Maybe the public is better educated now, but... maybe don't count on that.

- Toolset for bundling up *ALL* edits compiled by one side, having these "merged" and some sort of formal "approved to send" step would be huge.

- Please continue to track which person made every edit, when, and ideally, if said edit was "merged" and "approved to send" to counter-party.

- Over-invest in super easy UX & eye-candy: you're trying to overcome engrained use of a tool that's about as ubiquitous as the air we breath -- you're going to have to deliver 10x value, and ease-of-use will be critical for adoption. The current demo, and dragging links between boxes.... well, imho, perhaps not quite there yet.

- Finally, I've worked inside MSFT publishing docs & books, worked on hundreds of contracts in biz-dev & corp-dev & investment banking, and please let met state very clearly the need for this product is overwhelming. Please please please build this, and wish you all the luck in the world.

PS: Contractual.ly was pretty great. Wish it had caught more traction.

Happy hunting!
jefecoon
·vor 2 Jahren·discuss
> Using a very well designed library for your use case is not nonsense.

Could you recommend your personal favorite(s) of such libraries? Enquiring minds want to know! Thx.
jefecoon
·vor 2 Jahren·discuss
100%

If equity is going to be a material component of compensation, then the argument "you're not committed enough, you deserve nothing if you leave..." is utter nonsense.

Imho, many/most of these draconian equity / option terms are nothing more than attempts at 'golden handcuffs' to make it more challenging for employees to leave these startups.

Sadly, they work: I know many who couldn't leave roles til they'd saved up for years, or could finally ink second mortgage on their home, etc in order to purchase all their equity in their 90 day post-exit windows....