“I’ve been saving for months to get the Corsair Dominator 64GB CL30 kit,” one beleagured PC builder wrote on Reddit. “It was about $280 when I looked,” said u/RaidriarT, “Fast forward today on PCPartPicker, they want $547 for the same kit? A nearly 100% increase in a couple months?”
I really don’t think anyone is jumping in with zero analysis. Granted I have known some who will jump into something when its just a few words or even before its decided to go forward with a solution but over half the time what they do overnight provides decent info on moving forward or is helpful for gathering requirements. I mean im not blowing out my evening on a maybe but I respect the passion.
I would describe it as “insufficiently thinking about and researching the problems space”.
From what I’ve seen that’s very common because developers have a tendency to want to be hands-on rather than merely researching, myself include.
Even for the sake of figuring out inconsistent requirements or even just big gaps in the requirements, it’s a good idea to really think about it and cross check things.
Personally, the more I advanced in my career and the more complex and larger problems I had to tackle, the bigger the fraction of preparation time vs the fraction of coding time and I believe most very senior devs have the same experience.