Easy being defined as "usable by easily confused programmers who don't understand it or the trade offs."
Nice one. That's a deep concept. Programmers and projects generally get themselves into trouble because of a misunderstanding of the trade-offs.
It's rookie programmers who are enamored with a new bit of tech, but don't understand the downsides. It's managers who have an inaccurate estimation of risks and so lack the confidence to make decisive moves.
This is why experience can be so valuable in the programming field. This is the only way to learn about the cost/benefit trade offs.
Maybe "facile" is a better term than "easy" for this, though.
Comments
I'd avoid making it "easy". Easy being defined as "usable by easily confused programmers who don't understand it or the trade offs."
Easy being defined as "usable by easily confused programmers who don't understand it or the trade offs."
Nice one. That's a deep concept. Programmers and projects generally get themselves into trouble because of a misunderstanding of the trade-offs.
It's rookie programmers who are enamored with a new bit of tech, but don't understand the downsides. It's managers who have an inaccurate estimation of risks and so lack the confidence to make decisive moves.
This is why experience can be so valuable in the programming field. This is the only way to learn about the cost/benefit trade offs.
Maybe "facile" is a better term than "easy" for this, though.