Consulting is an interesting business. You don't always get to see the full lifecycle of the project you architected. You move around companies and...
For further actions, you may consider blocking this person and/or reporting abuse
To me, it seems that if you suggest a solution that you later realize doesn’t work then you would seem more intelligent admitting its wrong rather than asserting it isn’t. It’s ok to be wrong sometimes but admitting when you are is what truly matters.
Absolutely. And the title is a bit tongue in cheek. You can't guarantee a correct answer, but some of these behaviors ensure a wrong one. And others help make the possibility more likely.
This is quiet cool defining th problem is really important. Im heading in to do more kind of stuff like this and i can see its important to get stakeholders to know what you are doing and if it should be done.. will a good explanation of what will be affected beyond just a technical definition (that i would understand). I will see how i will have to step back. I've tried to see how other developers or rather senior developers do it and talk to people invovled.
Excellent points!
Related...
Please Don't Answer This Question
Jason C. McDonald ・ Jul 16 '18 ・ 6 min read