bravery.

Nope. I'm just being honest. It's live living in the dark ages. One needs to adapt.

folks who are earning money from their primary sources - primarily mid to large orgs - and do not want to spend time vibe coding half-baked apps which they need to maintain forever. this is the reason why companies like Atlassian will not cease to exist for a long time.

are long as devs are not "vibing hard"... should be okay.

Filezilla.

it’s out today.. six months later 🙂‍↕️ pdf + epub on leanpub chapter 6 is free if you want to see if it’s your thing leanpub.com/secondtimeisabug #secondtimeisabug

There's a particular kind of unfinished project that keeps coming back. You stopped working on it months ago. Then you come across something that reminds you of it. A new tool appears. Someone mentions the problem you were trying to solve. You think: I should get back to that. And you mean it. For a few minutes. The project might be a half-built app, a document full of notes, or an idea you've explained to three friends. It still feels possible. You just haven't decided what to do with it. Collect enough of these and you have what I think of as "the someday folder". It doesn't have to be an actual folder. Some of it lives in browser tabs. Some in old repositories. Some entirely in your head. The difficult part is deciding which ideas still deserve your time. Try opening one this week and writing down what would make it worth returning to. What would you need to find out? That might give you a smaller, more useful next step than "finish the project".

At this point, building your own version control system, CI/CD pipeline, and deployment stack almost feels as secure as relying on the established ecosystem. With the growing number of attacks targeting open-source software and software supply chains, the trust we've placed in our development infrastructure deserves some serious scrutiny. And somehow, "just shut everything down until we figure this out" is starting to sound less like a joke.

Nobody: Absolutely nobody: Tech folks on X: "Name one technology that does [something] better than [insert my favourite technology here]. I'll wait." The engagement-bait template that apparently never goes out of fashion... 😂

last bit everyone skips.. write down WHEN to delete it. models get better, rules go stale, and a CLAUDE.md full of dead rules is its own bug...

prove it works. put the mistake back on purpose and check the control catches it. if you never saw it fail you don't really know it works

put it as early as you can. before the edit beats pre-commit, pre-commit beats CI, CI beats a user finding it a week later

then pick the control. a guide (a line in CLAUDE.md) or a sensor (something that fails loudly). for this one a rule was enough: grep for the class name before creating a new one. small enough that it actually gets followed

then root cause... the line that broke barely mattered.. the agent created a new css class called .skip, and a .skip class already existed that hides things. the actual bug was "it never checks if a class exists before inventing one"

symptom first. a dialog's "PDF only" button just disappeared after an agent change. no error, build green, it simply wasn't there

every time my coding agent makes the same mistake twice, it goes through one loop now. walking through it with a real one from a small site I run..

mostly agree... the one that bites later is the data model, everything else is cheap to redo once you have traction

the tradition lives on....

makes sense for auth... curious how you debug it when the app route and the direct server expose different tools tho

works well till they start arguing over the same nit for 3 rounds lol... someone still has to read the diff