You must read at least one book to ride

I love this guy's cynicism and no-bullshit attitude. As someone who lived in Melbourne and has suffered Deloitte's "technology" department, the frustration and anger is warranted.

Like everyone else, Australia has tech brain drain and loses its best software engineers to USA. But unlike almost everyone else it's a very rich country and so can still afford to spend billions of dollars training and deploying engineers who "haven't read one book" to quote-unquote 'solve' domestic and regional technology problems. It's a giant make-work program to keep people busy while property speculation and resource extraction drives GDP growth.

Oh right, it’s the dominating Matlab piledriver[1].

1+ book, playing the guitar, having this one weird hobby, being a semi-pro gymnast—insert whatever you want from your life experience in order to have a story frame to justify a long rant about how you are so good without even trying (or everyone else is a moron).

Reading is more of a facilitator and a start. Practicing is what makes things fall into place. And being interested enough to look up and try different things out.

[1] https://ludic.mataroa.blog/blog/i-will-fucking-piledrive-you...

Interest is most of it. Interest in studying will also make it stick.

I read a comment, possibly on HN, about a college professor who tried an experiment on information recall. The first group had just raw information, and the second had the information crafted into stories with simple, singular ideas each. The second group by far did better at recalling the information than the first. People are story driven creatures, there's a reason our oldest epics are stories. That's why self help books follow this formula, because it works.

And like the other commenter said, there is a huge difference between reading something, understanding that something, applying that understanding, and finally mastering that application.

> Then there are engineers [...] who never try for the entirety of their careers

This matches my experience 100%. I am not a brilliant developer by any measure. I'm competent enough, I can put together good solutions to the admittedly low-scale problems I'm assigned, and I like to think I have a pretty good sense for the right and wrong ways of going about doing so. But I'm not even sure I could land an interview with a FAANG company, let alone a job.

My feeling at work is one of constant vigilance. I feel like if I look away for too long the gremlins will start creeping in. And I'm not talking about some imperfect design or the odd code smell, I'm talking about dropping in on a PR two senior engineers have already approved and spotting a critical security flaw in the first 30 seconds. Or a data loading pattern that works okay with the five records they've tested against but would make 300 database queries per page for a realistic dataset. Or spend 75% of their CPU time hydrating date objects from timestamps that are then immediately discarded.

I think it comes down to a lack of inherent curiosity and/or interest and/or passion in programming. To me good programming is a craft—I won't go so far as to say it's as much art as it is science, but I think there is definitely an artistic element to it. Which for me introduces a need to do something well, rather than just ticking boxes and going home. "Painting the back of the cabinet", as it were. If business requirements force me to ship some monkey-patch fix, it gives me a discomfort I can't really put into words. I immediately want to replace it with something better, because I just don't like putting work I know to be substandard out in the world. I'm not even particularly invested in the product and services my employer creates, but if it's my work I want it to be good.

Something I often hear is "I couldn't work out how to make work so I just did ". It irks to me to no end because without fail, what "I couldn't work it out" always means is "the first thing I tried threw up a minor roadblock so I stopped trying". And it sucks because the worse a codebase gets, the more difficult it is to contribute something you can be proud of.

Have I just had the misfortune of working at particularly crappy companies, or are things really this bad across the whole industry? I'd really like to think it's the former, but I read articles like this and dread that it's the latter.