To add to this, they have to be developers who aren't already using a fullstack observability solution, since it's fairly straight forward to add the eval startup featureset to an existing observability solution, and easier (plus cost effective) to just keep it all in one place.

Do it right and you can send the first underwater explorers to Europa.

Hard to find the right way to monetize in the early stages though. SpaceX had a variety of options.

“Move fast with stable infrastructure” as they say.

Everyone will have a “reasonable” explanation though for why they have to stay in the terminal even when they aren’t really coding anymore and it wouldn’t be hard to have a window next to your terminal if you really have to, but live and let live. Whatever makes you happy as be all become managers.

I too like a cyberpunk interface even if it’s last the need :)

1. Full carrying cost of an employee is much more then their salary so this math is not as straight forward if you’re just cutting time and salary to account for that time.

2. You should assume most people aren’t counting hours in places like Meta, reducing to a 4 day week imho will start making people think more about counting exact hours they’re working. It’s partially why the “4 10s” concept is also a bad idea that permeates the defense contractors.

3. Staying focused 5 days a week for one person probably has better compounding effects for that week than a few people working part time and taking longer to get the work done with longer breaks in between “sessions”. Harder to measure of course but it’s one thing I’d be worried about. Easier to think about if you say each person works 2.5 days a week for half their pay, I’d rather just have one person.

4. Layoffs let you cut by performance.