"You are not paid to write code, You are paid to solve problems"
Word to the wise.
Basically - 99% of the problems you have someone have already encountered before and uploaded a working solution to the internet. Find that solution and 90% of your problem is solved. the next 10% is only adapting the already working solution to fit your specific needs.
Of course, you can choose to go the hard way, but then you violate one of my personal top 3 favorite principles: DRTW - Don't Reinvent The Wheel.
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
exactly. many times during standups I can't help but raising my eyebrows in suspiciousness when I hear other devs say a specific task is super complicated and they need to come up with some weird customized implementation to achieve it.
at least 90% of the times with a more accurate google search, or just by digging deeper in the documentation of the library - framework we are using the solution is there.
From humble beginnings at an MSP, I've adventured through life as a sysadmin, into an engineer, and finally landed as a developer focused on fixing problems with automation.
The key words here are "was once"... IMHO, the most important part of the job is to break down super complicated and specific tasks to small, simple tasks.
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
"You are not paid to write code, You are paid to solve problems"
Word to the wise.
Basically - 99% of the problems you have someone have already encountered before and uploaded a working solution to the internet. Find that solution and 90% of your problem is solved. the next 10% is only adapting the already working solution to fit your specific needs.
Of course, you can choose to go the hard way, but then you violate one of my personal top 3 favorite principles: DRTW - Don't Reinvent The Wheel.
exactly. many times during standups I can't help but raising my eyebrows in suspiciousness when I hear other devs say a specific task is super complicated and they need to come up with some weird customized implementation to achieve it.
at least 90% of the times with a more accurate google search, or just by digging deeper in the documentation of the library - framework we are using the solution is there.
Every task was once super complicated and specific.
The key words here are "was once"... IMHO, the most important part of the job is to break down super complicated and specific tasks to small, simple tasks.
that's another very important skill:
always keep in mind the global picture, but be able to split the problem into small simple tasks