EngineerBetter
Joined 11 years ago
Joined 11 years ago
https://github.com/re-cinq/claudit
What's amusing is that I specifically made a comedy license for it, because I thought trying to protect the IP of such a thing is madness in the AI-native era. Then within days I find out it's a massively funded startup!
https://github.com/re-cinq/ai-native-application-license/
I've got Claude Code adding Gemini and OpenCode support to my tool currently.
It'd be interesting to see the experience of folks in continental Europe, where I gather wine with meals is much more commonplace.
We run Concourse London User Group, and the first few instances were like some kind of Jenkins survivor's support group.
Long trips in a Tesla are totally doable.
Hear, hear!
If you can accurately estimate how long a software task will take, you should have already made a reusable component or automation to generate that code.
Estimates are meaningless. I've seen PhDs waste endless hours faffing with estimate-calculating spreadsheets.
Fundamentally, the universe is unpredictable. Chaotic and complex systems require their starting conditions to be measured to an infinite level of precision to be predictable. The Heisenberg principle means this is, as far as physics can tell, impossible.
On a more practical macro level, a complex adaptive system becomes unpredictable once three feedback loops are present (the three body problem is related).
Modern computer systems are unpredictable because we cannot predict the interplay between levels of abstraction.
It does not matter how smart you are. Unless you have perfect knowledge of all levels of abstraction in the system below you, even in a macroscopic sense you cannot predict the future. Precise estimates will be inaccurate.
Confidence ranges and superprobabilities are of some use. Discrete and precise estimates are an utter waste of time at best, and are dangerous and misleading at worst.
EDIT
Written on a mobile waiting for plane take-off, hence lack of citations. For more on complex adaptive systems, I recommend the works of Murray Gell-Mann and the research output of the Santa Fe Institute, particularly Scott E. Page.
Don't do sprints. Have a continuous backlog. Don't do overtime. Don't make estimates. Always do the simplest thing. Only ever do the most important thing, as defined by the stakeholder.
I've written and talked about this at great length. The fact people suggest agile gives you burnout reinforces my experience that Scrum is largely misinterpreted and people incorrectly focus on sprint commitments. If Scrum is so commonly misinterpreted, it is flawed.
https://www.linkedin.com/pulse/scrum-makes-you-dumb-daniel-j...