I’ve wasted entire days with people like that because they couldn’t be fucking arsed reading error messages and figuring things out by themselves.
I’ve had a couple interview tasks that are like “clone this repo and run it. Try to do [action]. Tell us any errors you find and how to fix them”
One of them was some sort of redux app, and the problem was a state mutation. Another one, the CSS had some weird so stuff rendered crazy. Both were pretty easy to track down and fix. You could probably also do something that’s like an error thrown, but people would probably just feed that into an AI now.









There’s definitely a lot of cargo cult* thinking in software. People don’t understand the why of things but they want the results. That’s why most “agile” I’ve seen is a waste of time.
*Is there a less problematic phrase for this?