I think new forms of media, like radio and television, are worthwhile comparisons to AI. They were hugely influential technologies in the 20th century, making a small number of media companies hugely powerful. That sounds a lot like AI.
The difference to AI is that we regulated the heck out of radio and television companies. I think this is evidence in favor of heavily regulating AI.
> 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.
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.
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.
The difference to AI is that we regulated the heck out of radio and television companies. I think this is evidence in favor of heavily regulating AI.
reply