Some really good tips here for knowledge workers in general, not just developers/engineers. Questioning my bias has given me the best results to my career, because it let me grow where previously I'd have ignores an avenue.
I also come back to "is it a bug, or is it a feature?". Sometimes features are just not inclusive enough, they represent a past bias expressed somewhen else. Then by questioning what was actually expected... Sometimes we can come up with a very different solution, instead of compounding and confusing the bias further.
Trouble maker and Problem solver ⚙️🔧
Loves simplicity, hates bullshit 💩.
Productivity obsessed, avid learner 🖥🚀
Sport and outdoor freak 🧗⛰
Metalhead 🎸🤘 Father of 2 👨👩👦👦
Opinions are my own
Some really good tips here for knowledge workers in general, not just developers/engineers. Questioning my bias has given me the best results to my career, because it let me grow where previously I'd have ignores an avenue.
I also come back to "is it a bug, or is it a feature?". Sometimes features are just not inclusive enough, they represent a past bias expressed somewhen else. Then by questioning what was actually expected... Sometimes we can come up with a very different solution, instead of compounding and confusing the bias further.