Most large IT departments are collections of specialists, and many of these people don’t know anything about professional coding. Security folks often need good understanding of the overall technology, but these jobs are usually mostly focused on creating policies, keeping systems patched and up to date, reviewing audit trails, and so on.
This was something I noticed when I was building my career. GOOD generalists are hard to find. Generalists who both understand enough about the programming and the systems and the network and the politics to figure out a reasonable path for the company to make or save money with IT, are useful. And companies always have a few who glue the specialists together.
I can’t code worth a damn. But I can code. You read my code and it’ll be a dog’s breakfast but it’ll be commented well enough a specialist can figure out the idea and make it a LOT better, and it’ll be in whatever language du jour is needed for that particular team and project. I’ll spend an inordinate amount of time figuring out how to write it in something one of the specialists on the team knows and loves. I hate coding.
But...
If I’m coding, something is REALLY broken. And it’s probably not just software, it’s something that’s killing the business. Either via outages or very ticked off customers or lack of automation wasting more than one person’s time. Examples might be stupid crap like a policy pushed by a customer or third party certification that says X, Y, and Z reports must be run quarterly. Most companies will start by hiring some person to sit there and run the reports. That’s stupid. Automate the report and gain a brain that can be used to do something else more useful.
Or customers screaming about how manual and crappy the installation process is, and how it leads to huge human errors. I have to freaking learn REXX to fix that one, and write an installer that accounted for the decisions the humans made during install and then testing the crap out of it. It became part of the product and then I had to go train customer service on how to use it and more importantly what it was doing under the hood with the questions that got answered. Those questions and actions were learned by observing multiple installs BY customer service walking customers through horrid written documents by hand. The spec for the installer was literally already written. It was that document. Why no one wrote an installer from the document was beyond me, so I did. Why read a document to someone over the phone a hundred times? Waste of resources.
Troubleshooting. People look for problems only inside their specialty. They miss the big picture. Break the problem up into testable theories and poke a stick at each specialty’s piece. Is it network? Server tuning and performance? Software performance? A generalist digging into all of it to find the root-cause problem then showing it to a specialist, gets things fixed.
Training. Is the real reason this thing keeps blowing up in everyone’s face just a lack of standardized training? Analyze the “need to know” times and put a class together. Even just the act of creating common terminology can make a bunch of specialists work better together if they’ve all had the same training. (Lots of companies miss or screw up this one. They point s specialist at a problem on day one and the specialist never sees the forest for the trees on how the whole system works together.)
So, there’s a place for generalists. But we are few and far between. Ifs been good for me but the repetitive mistakes seen over and over are a little tiring nowadays. Good people with good personalities make it bearable. Especially smart ones who know we’ll see that mistake go by again in a few more years.
And it’s not like I don’t fall into the trap either. I know better than to let a Broadcom product anywhere near a Production System. Guess what but me square in the ass this week, a decision made three years ago? Should’ve bought Intel cards. I know better. We were being ultra cheap. A major partially covered up and hard to find problem will be fixed with $140 worth of Intel cards. I should’ve argued harder three years ago when my gut said Broadcom surely has gotten their crap together by now... right?
Nope. Screw Broadcom. Ha.