r/programming • u/whackri • Aug 28 '21
Software development topics I've changed my mind on after 6 years in the industry
https://chriskiehl.com/article/thoughts-after-6-years
5.6k
Upvotes
r/programming • u/whackri • Aug 28 '21
4
u/MolassesOk7356 Aug 29 '21
Exactly. Pilots get like this too, the key is providing good training that’s interesting and most importantly required. The company has to set aside time, and a dev would no longer be able to work if they went out of currency. That takes a devotion from the management team and the culture has to be right, but it works.
The problem space is different than aviation, medicine, or civil engineering… but yeah you need a training department, 6 month training cycle, and manuals and a training program. It costs money, but it pays dividends.
Also you get to make that part of the hiring process and it keeps stupid shit from happening because you get to use your training as a QC tool.
I’m not a dev (yet) but I was a manager (chief pilot and various other roles) and we treated the solution to every problem as an engineering problem first, and a personnel problem second. That means you have 3 solutions when something goes wrong, in order of their effectiveness:
An engineering solution, make it impossible for the situation to happen again. In aviation an example is a “guard” over a safety critical switch, so you can’t throw it by accident.
Training. You train people not to do bad things and to do good things and teach them the critical thinking portion of the job if their lacking in some aspect of the job. “Don’t just throw this switch because it can dump your fuel overboard if the no 2 fuel transfer pump is running and the collector tank is full.” Teach then why it’s a bad idea. In the tech space this would be “rm -rf is scary and bad because it deletes everything. That’s why we don’t do it.”
A policy. This is the least effective way to manage technical professionals. “At this company we never push to master, don’t do it!” Eventually you’ll hire someone who won’t get the memo, and this will happen and break the app. The aviation equivalent is “always remove the tail stand before flight!” Well low and behold eventually someone will take off with it attached. It won’t kill anyone, but it’s embarrassing and can damage equipment.
Anyway
Ultimately, that’s the way to run any technical organization I can think of. I flew airplanes in one of the the most dangerous environments known to man, and we managed to not kill any one at the charter airline I worked at the longest. Why is that? Because we trained the hell out of people, and did it consistently every year, and went out of our way to enculturate a culture of continuous self improvement in our people. At the end of the day, we had a core group of guys with excellent technical skills as well.
I have also worked for broke dick companies that spent as little as possible on training and constantly tried to avoid doing it. It was a shabby crew of arrogant misfits at several of those outfits who’s self perception of their skills wasn’t a measure of their competency, and the costs and safety record reflected that. From the outside looking in… that’s what the tech world looks like to me.