@shonnaraines@proteo5@allenholub I have to believe Señor Pinto is either provoking or jesting. I have a hard time believing anyone who actually works in software dev genuinely believes what he writes; it is something only an uninformed manager might believe, and it's a surefire way to ruin software dev.
@jadaagraves @nathaliejacoby1 Do you have to BUY a warranty for new products? Here, sellers and/or manufacturers have a legal obligation to fix failures for free for most products. I literally thought that was the definition of a warranty. If you pay, its an added insurance to extend after warranty years(s).
@jessereiss@djsmith42@alexbunardzic Granted, but while you seem to be ok with pretending to know the cost of implementing new and unverified ideas, I'm not. I'd rather drip feed and verify, giving me possibilities to pivot or abort while I can afford to.
There's a reason most "big names" are against estimates.
@jessereiss@djsmith42@alexbunardzic Engineering? Next, you're gonna start comparing SW dev to building houses and bridges? No experimentation and validation of needs? Or you simply deliver what is asked of you, no questions?
If managers make investment decisions based on guesswork, they should be fired.
@djsmith42@alexbunardzic@jessereiss Software being developed means needs can't be met with off-the-shelf solutions. It is something new. Thus no team can know what an outcome will cost before investing in it. The only certainty estimation brings is the certainty of also paying for the time spent estimating.
Reminder: Inflation isn’t being driven by government spending. It’s being largely driven by the fact that a handful for mega corporations have consolidated their market power and can raise prices on consumers.
@scrumtuous To be honest, I thought your tweet was in jest, with so many elegant and/or expressive languages out there, such as Rust, Kotlin, Elixir, Go.
But Java did help build an industry, and it is adding features from other languages, albeit slowly, so kudos. And thanks for the JVM.
@mr_enzzo @WoodyZuill @ZeynepAktasEng That is far from true; for instance, I've helped many experienced teams transition to the cloud, an infra that is unknown to them.
And even so, the thing to be built is still unknown, likely unknowable.
While some teams are busy estimating, experienced teams are busy learning.
@skamille All for gaming metrics, when metrics are based on useful outcomes, e.g. measuring number of new, paying customers or retention. In this case it would make sense to have the whole org involved in "gaming" metrics! The trick is to be able to tie an activity to a change in metric.
@asher_gunsay @WoodyZuill Here I was hoping that by now everyone knew not to parrot this particular nonsense. This could only ever make sense if your goal is to give the customer exactly what they ask for at the outset, instead of giving them what they need.
@uxfra@allenholub Upfront cost? Cost for what? Exactly what the customer asks for? How often is that doing them a favor? Shouldn't you instead spend the time figuring out what they need, continuously until that's what you have delivered? Likely something neither knew. How do you estimate that?
@510home Source? I searched high and low, seems like yet another myth about nuclear. And if the option is to work with coal, I'd say it's a wash anyway.