That's the wonderful thing about the Agile Manifesto - it says so little you can use it to justify anything.
Specs? The agile manifesto never said to stop writing specs!
Standups? Checmkate waterfallists, the agile manifesto never mentioned that!
Real software engineers have written written real papers on these things. We can forego the manifesto, which is just a few platitudes from consultants on a website.
The places where I've seen unequivocal wins with AI are repetitive tech debt tasks that apply the same transformation across a large amount of code or refactor under a pre-existing test suite with good coverage.
I agree with this, but I'd add the caveat you have to do your own digging and researching (as the article says) to identify these tasks well. If you ask it for ideas, it gets painful.
YMMV (and I am very open to getting better at this).
I still don't know it very well, and it's been well over a decade. I think it's a combination of a few things:
- I find it uninteresting. My version control needs are very simple.
- Most teams I have been in use a small subset of it.
- It's confusing terms and inconsistent cli are huge warning signs to not go down that rabbithole. Today instead of learning Git I read some Tony Hoare, much better.
I've been at once place where they rebased, and it was awful. Complete waste of time. (great place otherwise though)
The first five links (i.e. not the book) are each only a few printed pages worth of text each or less. All together they are equivalent to like a single chapter of text in a book.
It really won't take hours. You probably read more than that just looking at HN for like 20 minutes.
If I talked about how I needed to recover from being raised in a progressive environment, it would not be so well received in well-respected tech circles.
There's an assymetry here no one wants to acknowledge.
I don't know anyone who had to "recover" from being raised by "progressive" parents. Is this actually a thing? What would there be to recover from exactly?
Anecdotally I find I connect more with what I write by pen as well.
Ultimately I want things to in text documents though (typst for me these days). If there was a non-slopware solution to ocr scanning to a typst doc, I would do it a lot more .
I have been using LLMs for this and they excel and understanding my very poor calligraphy. All I do I take photos of the pages I wrote by hand, and then ask the LLM to convert those notes to markdown and convert any diagrams that I might have to mermaidjs style, and worked wonders for me.
Hmmm - I guess all the "chatbot" web interfaces for LLMs have an option to upload images. And they're really good at this now you say? That's a really useful tip; thanks.
Specs? The agile manifesto never said to stop writing specs!
Standups? Checmkate waterfallists, the agile manifesto never mentioned that!
Real software engineers have written written real papers on these things. We can forego the manifesto, which is just a few platitudes from consultants on a website.
reply