| member | fsfe.org,python.it,python.org |
| member | fsfe.org,python.it,python.org |
Das war in der agilen Community los (Woche vom 05.12. – 12.12.)
Wir hinterfragen, ob wir uns mit "Sprints" eigentlich nur kaputt rennen, lachen (oder weinen) über Teams mit 17% Zielerreichung und diskutieren, ob Agile im Zeitalter der "Enshittification" überhaupt noch eine Chance hat. Wenig Theorie, viel schmerzhafte Praxis.
Hier die Highlights 👇
1/4
RE: https://mastodon.social/@painless_software/115667386959330889
I'm working in a team that just completed a sprint with 17%(!) completion of the planned work. Almost *everything* is spilled over to the next sprint. It's ridiculous.
Large organizations fill sprints to prove they are busy. But what are sprints designed for? To give #confidence! You can't give confidence when you're constantly spilling over.
Just use a #Kanban board to show off how busy you are. Don't engage in #enshittification of #Scrum, treating "spillover" as a chic, must-use word. #agile
RE: https://mastodon.social/@nicklockwood/115553420045122380
Mind-blowing explanation of the current state of #AI and the false promise of #vibe #coding. Read all 10 posts in this enlightening thread! 💡🤯
But the idea that natural language makes it easier for non-programmers to program is a misunderstanding
Programming is not about transcribing English to code, it's the art of turning vague requirements into concrete ones - identifying and filling in the blanks so that an imprecise spec becomes precise
When you "vibe code" you are asking an LLM to do that work - and they are remarkably good at it - but that is not *programming*, because you are not identifying and eliminating those ambiguities