blacob

> Then where does the rigor go? Similar to the Thoughtworks report, my first bet would be specifications (which is not the same as prompts) and tests (which is not the same as TDD).

This is what we're building for at Saldor (https://saldor.com). It's a hard problem, to get a team in the habit of writing good specs. Probably because it's a hard thing to do: thinking of the behavior of your program, especially at the edges. But I agree (biased) that this is probably the way forward for writing code in the near future. I'm excited to see other people thinking about it.

Crusoe Energy | ONSITE (SF, DENVER, CHICAGO, NYC) | Full-Time & Interns

cruseoeenergy.com | crusoecloud.com

Crusoe is on a mission to align the future of computing with the future of the climate by unlocking stranded sources of energy to power crypto, cloud and data centers, we are creating a future for compute-intensive innovation that reduces emissions rather than adds to them.

We recently raised our Series C: https://www.bloomberg.com/press-releases/2022-04-21/crusoe-e...

Hiring across disciplines and locations, learn more about roles and apply at: https://www.crusoeenergy.com/careers

Questions? Feel free to reach out to me at jbland at crusoeenergy dot com