Aww, that's so sweet!

> Look, we clearly have a problem here. This task was voted a two-pointer and after two weeks we're still here talking about this. This shows me that there's a skills mismatch between you and what we expect from someone in this role.

This is depressingly real. So much agita is caused by tasks that are initially underestimated.

Claude Code

No Gemini-cli competes with that, this competes with the web-interface-around-agent-with-it’s-own-machine space,

not the pair-programming-on-your-machine space I would put the cli tools in

They even had to choose a French-sounding name to make the comparison clear?

dont shoot the messenger, but it's supposed to be like a "butler sounding name"

Got it - and Jenkins and Hudson were already taken.

Wadsworth is free. brb startup

Steve Jobs just came up with the number. There was no deep reasoning behind it.

Shouldn't future work like this just go into the backlog of your ticketing system?

In theory perhaps. In practice, if you're stuck using the likes Jira or ADO, the friction of getting something into the ticketing system is excessive. If you're using a ticketing system designed for programmers and not project managers, then maybe it could be organized for a flow like that.

> I want to emphasize that the coding journal is not a todo file or code comment. It contains things I have to think about not things I have to do.

The author mentions that a lot of these will eventually end up in comments or elsewhere, but it’s nice to capture random thoughts without adding the friction of deciding where it should land, what priority the ticket should be, etc, etc is quite nice.

This matches the spirit of Getting Things Done's "Inbox" quite well. The goal is to minimize friction for recording thoughts/ideas/todos that come into your head. You write them down and into the Inbox they go, to be sorted/dealt with at some later time.

Or never.

I write notes throughout the day. Hardly ever search back in it. It's just to let me stop thinking about thing X while I'm working on thing Y. If X is important it'll come up again or show up in a ticket somewhere.

And that's why we now require any pilot flying VFR within 60nm of DC to get special training:

https://www.aopa.org/advocacy/advocacy-briefs/air-traffic-se...

This is partially a collective action problem. It might be socially optimal for people to take more risks working on crazy ideas, but for individuals there's less risk in working for a large corporation on incremental improvements.

Which would be fixable with a UBI. Make it feasible for everyone to live a life of failing at high risk endeavours, not just the privileged ones

UBI is hardly sufficient to fund most high risk endeavours.

No, but if you can spend decades building up convincing PoCs and pitch decks without needing to worry about starving, rent or healthcare you are more likely too. Sweden is more entrepreneurial than most of the rest of Europe for this reason afaik

If I spent decades on PoCs they’d be obsolete before they saw the light of day.

This species of mosquito isn't native to Florida in the first place, so I don't see how we can wreck the ecosystem by removed this non-native species.

I wonder how long till Substack starts aggregating writers. Subscribe to these 5 for 20% off, sort of thing.

You could aggregate writers within a niche to get a full view of that area. Or you could aggregate across topics to get something approaching a traditional newspaper.

Now that's it possible for the machines to be operated remotely, how long till those operator jobs are offshored?

I wouldn't jump to that conclusion so fast.

Having hired subcontractors from offshore I can tell that there is always a background difference that decrease the value.

Covid has shown that a lot of office work can be done remotely, but that does not mean that all the businesses suddenly will go away offshore. It just becomes a perk of the job.

And, thus, we're close to having machine operators working from their beds :)

you should read the article my friend :)