Sounds like GPT wrote this piece based on some tech exec‘s „we must use AI or lose“ „strategy“. Just let engineers use the tools they want instead of force feeding them yet another ridiculous process. For me, if I have to do meetings in the morning (or „write promps“ lmao) instead of clearing out the ridiculous AI slop debt of code agents my product would never ship.
No Coding Before 10am
31–40 of 58 posts
Re: No Coding Before 10am
#32Oh, I also have a rule of not coding before 10 am, but that's because I'm drinking tea and thinking.
Re: No Coding Before 10am
#33So if you specify work the right way, you can move at incredible velocity. If you have the confidence in your setup and ways of working, you don’t need to look at the code being put out.
Genuinely seeking answers on the following - if you’re working that way, what are you “understanding” about what’s being produced? Are you monitoring for signal that points out gaps in your spec which you update; code base is updated, bugs are fixed and the show goes on? What insights can you bring to how the code base works in reality?
Not a sceptic, but thinking this stuff through ain’t easy!
Re: No Coding Before 10am
#34"Agents should work overnight, on commutes, in meetings, asynchronously." If I read stuff like that, I wonder what the F they are doing. Agents work overnight? On what? Stuck in some loop, trying to figure out how to solve a bug by trial and error because the agent isn't capable of finding the right solution? Nothing good will come out of that. When the agent clearly isn't capable of solving an issue in a reasonable…
10 minute is not the limit for current models. I can have them work for hours on a problem.
Humans are not the only thing initiating prompts either. Exceptions and crashes coming in from production trigger agentic workflows to work on fixes. These can happen autonomously over night, 24/7.
Re: No Coding Before 10am
#35Anyone else find reading things like this slightly exhausting? I'm very much pro AI for coding there are clearly significant capabilities there but I'm still getting my head around how to best utilise it. Posts like these make it sound like ruthlessly optimizing your workflow letting no possible efficiency go every single day is the only way to work now. This has always been possible and generally not a good idea to…
Nope, but I do find it revolting.
Re: No Coding Before 10am
#36Oh, I also have a rule of not coding before 10 am, but that's because I'm drinking tea and thinking.
I thought that what article would be. Instead I got article going "we're dumber than Artificial Intern we hired, let's just be their secretary"
Re: No Coding Before 10am
#37> If 10x more tokens saves a day, spend the tokens. The bottleneck is human decision-making time, not compute cost. This seems entirely backwards. Why spend money to optimize something that _isn't_ the bottleneck?
Any human in the loop will be a bottleneck in comparison to AI performance. If we take that to its logical conclusion, I think we can answer that question. Getting rid of humans, unfortunately, also takes away their earnings and therefore their ability to purchase whatever product you are developing. The ultra rich can only purchase your product so often - hence better make it a subscription model. So there is pressu…
Just sell it to govt, then you can take printed money directly instead of having to go thru such filthy thing as "consumers"
Re: No Coding Before 10am
#38Anyone else find reading things like this slightly exhausting? I'm very much pro AI for coding there are clearly significant capabilities there but I'm still getting my head around how to best utilise it. Posts like these make it sound like ruthlessly optimizing your workflow letting no possible efficiency go every single day is the only way to work now. This has always been possible and generally not a good idea to…
I know people like this, theres a form of procrastination where they are busy hyperoptimising their todo lists and workflows but getting only a tiny amount of actual work done. It's a form of the disconnected intellect - they can tell you the problem, they can even tell you the solution, but they can't turn that knowledge into action. Convincing themselves that utterly trivial inconveniences are so productivity and or psychologically harmful they can they can then rationalize all this "meta-work" while simultaneously claiming to be virtuous, when in reality it's usually insecurity in their abilities or cowardice to face the unknown, preventing them doing real work
Re: No Coding Before 10am
#39"Agents should work overnight, on commutes, in meetings, asynchronously." If I read stuff like that, I wonder what the F they are doing. Agents work overnight? On what? Stuck in some loop, trying to figure out how to solve a bug by trial and error because the agent isn't capable of finding the right solution? Nothing good will come out of that. When the agent clearly isn't capable of solving an issue in a reasonable…
Everyone here (including me) agrees on how dumb this idea is, yet I know C level people who would love it. I wonder how our comments will age in a few years. Edit: to add > Review the output, not the code. Don't read every line an agent writes This can't be a serious project. It must be a greenfield startup that's just starting.
> I wonder how our comments will age in a few years.
Badly. While I wouldn't assign a task to an LLM that requires such a long running time right now (for many reasons: control, cost etc) I am fully aware that it might eventually be something I do. Especially considering how fast I went from tab completion to whole functions to having LLMs write most of the code.
My competition right now is probably the grifters and hustlers already doing this, and not the software engineers that "know better". Laughing at the inevitable security disasters and other vibe coded fiascos while back-patting each other is funny but missing the forest for the trees.
Re: No Coding Before 10am
#40It blows my mind how these posts seem like everyone is victim of a collective amnesia.
Literally every single point in the article was good engineering practice way before AI. So it's either amnesia or simple ignorance.
In particular, "No coding before 10am" is worded a bit awkward, as it simply means "think before you write code", which... Does it need an article for saying it?