

For sure, the song of the hero who fixed the production bug is oft sang at meetings but the loser who prevented the bug to begin with gets no credit.
Not much to say


For sure, the song of the hero who fixed the production bug is oft sang at meetings but the loser who prevented the bug to begin with gets no credit.


Classic “test in production” strategy, very solid!


To be fair they would have needed to spend time testing the manual implementation as well.
The problem I see mainly is that even if this rolls out perfectly, the erratic and changing nature if llms still make it pointless as a proof of concept. Next time Claude might fuck up in a fringe way that’s not covered by unit tests and is missed by manual tests.
On the other hand I guess I’ve been guilty myself on numerous occasions to implement fringe bugs into production code, but at least I learn from it.





Unexpected monty python reference!


Not the one you responded to but if I may hazard a guess I’d say they see non-voting as a protest against the two party representative democracy currently in place.
If you’re forced to vote and there is no blank alternative, you are being forced to legitimise it whether you like it or not.


I was in a men’s group once for a few sessions, we talked about everything from anger issues, how to work on improving ourselves, how to handle rough parts of it relationships etc.
It was very nice, we were all very different people with different backgrounds and problems and I believe we all got a lot out of just opening up in a group like this.
This was hosted by the Swedish organisation Man which exists to help men with all the issues modern men are facing, hoping to combat toxic masculinity.
Personally I think a mixed group would’ve worked for me but I am pretty sure some of the people, especially the ones with violent history, felt more secure in a men’s only scenario.


That’s a wild assumption. Lenmy has a well documented API that wouldn’t pass on frontend-related things.
Making a client scrape the frontend seems like a lot of work for a worse result.
You are completely correct, and to be honest I’ve tested commercial product features in prod as well on teams that have the capacity to handle it and make a living on it, unlike this maintainer.
I’m also experimenting heavily with vibe coding and I think it has many uses for a seasoned programmer while getting a lot of flak.
Of course there are issues and problems with it, but for me it had been helping out a lot.