I agree that there is no magic bean, you have to learn stuff to make stuff.
But based on my experience, whenever someone says that something is "hard" or "complicated" or "difficult", it means 1 of 2 things:
Either the person doesn't understand it and assumes that no one else could understand it, or the person understands it, just wants to protect his/her job, and keeps everything a secret, forcing everyone else to reverse engineer his/her work. No exceptions. People in the first group also tend to solve these problems on the most complicated way, just to prove their point, until someone takes the time to actually look at the problem behind the solution...
>based on my experience, whenever someone says that something is "hard" or "complicated" or "difficult", it means 1 of 2 things: Either the person doesn't understand it and assumes that no one else could understand it, or the person understands it, just wants to protect his/her job, and keeps everything a secret, forcing everyone else to reverse engineer his/her work. No exceptions.
Not even remotely close to true. Some things are inherently hard, regardless of the motivation of somebody describing them as hard.
We have 80 years of experience building software, millions of bugs - and bugs costing millions, or billions, space explosions, medical equipment failures, national security compromises, and many other everyday issues, plus delayed projects with huge budgets, and going way past their budgets.
All this hard empirical evidence doesn't translate to "building software isn't hard, it's just because of ignorance/job security saying so".
Or, option 3, it is complicated and difficult. The fact that I understand something after 6 months of effort does not imply that it is simple or not hard.
The technically worst team I worked on was the one where no one could admit things are convoluted and difficult. Because team would rather reject that person as stupid then put an effort into simplifying messy complicated systems.
> People in the first group also tend to solve these problems on the most complicated way, just to prove their point, until someone takes the time to actually look at the problem behind the solution...
And that someone else will come in, say it is complicated and difficult ... and you wont believe them. You will thin they did not took time to understand it or they just want to protect their jobs.
But based on my experience, whenever someone says that something is "hard" or "complicated" or "difficult", it means 1 of 2 things:
Either the person doesn't understand it and assumes that no one else could understand it, or the person understands it, just wants to protect his/her job, and keeps everything a secret, forcing everyone else to reverse engineer his/her work. No exceptions. People in the first group also tend to solve these problems on the most complicated way, just to prove their point, until someone takes the time to actually look at the problem behind the solution...