The article leads to a bad example. If i heard from my technical lead such sentence as "feel right" or "feel wrong", i would huh, let me take more research on my own then we'll retry again.
Seniority is different from juniority in the ability to make things explicit as much as possible, from the requirements to the implementation specification.
I think in software engineering, the more explicit, the better.
Nobody ever says that in professional environments. They’ll retroactively develop a plausible-sounding justification for their gut instinct. Sometimes, if they’re not particularly self-observant they’ll even believe the explanation they created is the reason they believe what they believe.
> Sometimes, if they’re not particularly self-observant they’ll even believe the explanation they created is the reason they believe what they believe.
Most people seem to believe their post hoc explanations. Or at least most people wont admit that they are post hoc explanations, it is hard to know the difference since they come up with those post hoc explanations with the intention to manipulate you. That is also the reason it is so hard to change peoples minds in an argument, they wont bring up the real reasons they believe stuff they just bring up the post hoc tings. People seem to think that exposing your real reasoning makes you vulnerable. Like yeah, you get vulnerable to learning new stuff and changing your opinion, that isn't so bad.
Seniority is different from juniority in the ability to make things explicit as much as possible, from the requirements to the implementation specification.
I think in software engineering, the more explicit, the better.