I've been doing some kind of development work for about 30 years. I've written BIOS code for Z80's, windows code in Intel ASM, more C than I can shake a stick at. And then I transitioned to systems engineering. Part of the reason was that I was spending time learning things who's half-life was too short for the time I was spending on them. But the big reason was that I saw there were problems at the systems level that I wanted to help solve.
I took advantage of opportunities to keep my fingers in the development world. There were chances to take classes on many things - Scala language, Swift language for example. But without actually doing projects, I lost track of a lot of the block-and-tackle of development to the point that I understood things like CI/CD from the conceptual level, but couldn't pass a test on a particular tool set.
Now that I'm looking at finding new opportunities for the first time in about 20 years, I want to take some time and catch up on some of the details I've been missing. This will be helpful if I find another SysEng/Arch position, a Director/VP position, or if I find an opportunity to roll up my sleeves and dig into the guts of a cool project.
This blog will document what I'm doing in this space. It may only be significant to me. Or maybe someone will suggest things to look into that I have a big blind spot for. Or maybe I'll just look over it before I go to an interview.
I have a couple projects in mind that I'll document elsewhere. This blog will just cover the general development-related items I'm working through.
So hear goes!