One does not simply learn to code
Quincy Larson
5.5K236

Coding wasn’t easy when I learned to code Dartmouth Basic using punch card input on a CDC in the late 1960s. It was even harder using Fortran, COBOL and assembler on minicomputers 10 years later. Today, with all the amazing tools we have (splendid IDEs, an almost limitless array of libraries and advance frameworks) it’s even harder. It’s not the coding that’s that problem, it’s those damned users whose expectations of a wonderful experience advances just as fast as technology does. I may be old, I may be gray but I’m not stupid. Coding is hard and will be that way for a very long time. Anybody who chooses this career path is on a treadmill to continuously stay abreast of advances in technology to deliver ever better. If you don’t derive any pleasure from learning something new, don’t learn to ‘code’. Which is a really simplistic term for the very complex engineering exercise required to deliver seamless, transparent and rewarding user experiences.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.