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

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.

The trick with predictions is that once they are communicated they can influence the outcome. We’ll work with the iFixit team to make that article happen!

This reminds me of “what does 4chan think of HN?” posts. Look those up.

HN is HN’s worst enemy.

https://news.ycombinator.com/item?id=23145123 has some links.

http://n-gate.com/hackernews/ kept up something similar for a while.

Nice read, and beautiful website btw.

Indeed to both. I enjoyed it greatly. It was well written and on something that I think about someone's but never implemented.

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!

> Lawyers want this all to work in Word.docx

You've got some bleeding edge lawyers if they're using Microsoft Word. The legal industry is one of the main reasons that WordPerfect continues to exist.

The entire publishing industry operates on Word too. https://www.antipope.org/charlie/blog-static/2013/10/why-mic...

> 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.

When it comes to libraries that handle the messy details of putting data on disk, sqlite is the only one I can name off hand so that's the favorite.

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....

https://www.rubykoans.com/ Last time I looked they hadn't been updated in a while, so may not have support for the very latest & greatest features of rubylang, but find this a great approach to quickly familiarizing with 'core' ruby. Hope you enjoy.

Great article exploring specific colormaps and applications, incl discussion of pros/cons of popular maps [ e.g. Cividis better for color-blind viewing than Viridis, but is a more simplistic blue--yellow scale than others which utilize higher number of colors ]: https://www.kennethmoreland.com/color-advice/

Great, widely-referenced site for quickly generating color scales, w color-blind safe options, and large amount of research behind it: https://colorbrewer2.org/#type=sequential&scheme=BuGn&n=3

At Mapsense we would always refer to Color Brewer https://colorbrewer2.org/. Basically takes the thinking out of the equation.

Great resource in colorbrewer2 - thank you!

I have several color blind colleagues and am regularly concerned I'm not displaying visuals in a way that is easy for them to digest.

"The old Apple laptop would sound like a VAX in a hurricane while building Emacs!"

Sysadmin to a VAX farm in an earlier life -- this brought back some good memories, especially of what our server room sounded like when we pushed a new build... Thanks for that.

To whomever went to the trouble of writing this up, then giving it a dedicated domain -- thank you, you're making the world a better place.