If you look back at the sci-fi movies that came out soon after lasers were invented, you could see that people had all sorts of crazy ideas of what a laser could be used to do and that a lot of them had absolutely no idea of what a laser really did. Ultimately, we’ve found out that most of those imagined uses were pure bullshit or extremely impractical, at least with the current state of the technology. It didn’t mean that the technology was useless. We ended up finding all sorts of useful purposes for it that they had never imagined, like disk players or barcode scanners. It only means that it took time for people to better understand what the real world applications of the new technology was and a lot of the initial assumptions were dead wrong.
AI is going through the same process. It will take time before the technology’s strengths and weaknesses are better understood by the masses so it can be better applied to more realistic uses. And for the commercialization of snake-oil applications for it remains confined to fringe markets.
Sprints aren’t for you, it’s for the higher ups to have a digestible view of what’s going on in the team by presenting work done over 2-3 weeks, calibrating budgets, etc.
As a dev, yeah, sprints feel restrictive and artificial as fuck lol
If you still do the sizing (it’s not entirely wasted as it’s a reasonably effective tool to gauge understanding across the team), This can still be done without the artificial time boxing.
“How much work have we done in the last two weeks?” Just look at all the stories closed in the last two weeks. Easy.
“When will X be delivered?” Look at X and all its dependencies, add up all the points, and guesstimate the time equivalence.
Kanban isn’t a free for all, you still need structure and some planning. But you take most of that away from the do-ers and let them do what they do best… do.
I prefer V-cycle for when you have a software with known specs & Kanban for when you don’t really know what the client needs/wants. I mean those magic clients you hear about but never sees…
Take a shot anytime the non technical scrum master/product owner wants to “help” by trying to get someone else involved the moment you mention any kind of detail/problem/thing you’re working on
I’m glad my company speaks a different language than English, and can’t use all the word soup completely. That said, my company is also wondering why my timesheets never add up to the entire day because always in meetings, scrum, or “can we jump on video chat for a sec because it’s easier to explain vocally than in writing”… And that “sec” turns into a 30 minute tutorial I have to give.
The problem is that the areas us consumers would want it is not going to be place that companies put it. They’re gunning as hard as they can to monetize and minimize costs. Not what is most useful
Those cases are probably not profitable and will become enshitifcated when the VC money runs out and they start trying to turn a profit, so enjoy it while it lasts 😂
It’s sad that the best most startups can hope for is to be bought by a giant corporation. Not a lot of people are interested in just having a successful long-term business.
Whenever we say some work is going to be difficult and time consuming now, management reflexively ask if we can fix it with AI. It’s like an excitable little kid getting a bicycle for their birthday and wanting to do everything on their bicycle now, including eating, sleeping and homework.
programmer_humor
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.