3 ms·
I enjoyed that. It was an honest, humble, useful reflection, and I wish the author well. They seem like a decent sort, and our poor industry desperately needs m
by ChrisMarshallNY 3y ago
I enjoyed that. It was an honest, humble, useful reflection, and I wish the author well. They seem like a decent sort, and our poor industry desperately needs more “decent sorts.”
I had a similar background (especially the hardware core). I feel having a start in hardware, gave a tremendous foundation to all that followed.
One of the biggest epiphanies that I had, was when I realized that tech had gotten way too large for even the brightest polymath (which I am not) to master. I had to pick a direction, and walk that way, avoiding getting distracted by squirrels.
At the same time, I learned to keep long-term plans extremely vague, and go into focus on only the most immediate tasks. This is also how I tend to do my development architecture. I plan to change plans, and my architectures tend to have a lot of modules, “hooks,” bottlenecks, and “flex points.” Makes pivoting and repurposing straightforward. It’s basically habit, these days. Also, a pretty heavy-duty focus on code quality and documentation[0].
WFM, YMMV.
For myself, I’ve learned that I really enjoy “making things that people use.” UX, usability, accessibility, localization, and affording mental models. It gets sneered at, a lot, but is a huge challenge, to get right. Many great projects fail, because their engineers think that the UX is just “useless chrome that any schlub can do.”
Designing UX is designing around human nature; one of the most complex and unpredictable systems on Earth.
What gets a bit grating, but is also just basic human nature (so isn’t going anywhere, and also isn’t just a tech phenomenon), is folks that insist that if we aren’t experts in <TECH THEY ARE GOOD AT /> don’t use <TECHNIQUE THEY ARE PROUD OF /> or don’t use jargon, that we are “bad programmers.”
Personally, I find people that are truly good (as opposed to just facile) in stuff that is not my bailiwick, to be fascinating, and I appreciate having them around. I like to work on “heterogeneous” teams.
I think tech is wonderful. It isn’t a monorepo. There’s a hell of a lot of submodules, and each is a flourishing, rich, interesting world, with the ability to engage and enrich you. If you don’t like one, move to another.
I will say that shipping software, is different from writing software. There’s a lot of hard, grinding, boring work that we need to power through, and, sometimes, that work exceeds the actual engineering and design work. It’s not for everyone, and demands a different skillset from your standard geek arsenal.
[0] https://littlegreenviper.com/miscellany/leaving-a-legacy/ https://littlegreenviper.com/miscellany/leaving-a-legacy/