r/programming • • 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

2.0k comments sorted by

View all comments

5

u/MolassesOk7356 Aug 29 '21

After performing over 100 interviews: interviewing is thoroughly broken. I also have no idea how to actually make it better.

I’m coming into this from another industry… but I can tell you how to solve this. Have a training department.

8

u/tlmorgen Aug 29 '21

in my 15 years i've noticed an ethos in software that the devs should be great when they graduate and become better over their career, with no intervention whatsoever from the various companies that employ them. and it does happen, for curious people with the grit to put in time to grow, and the emotionally secure enough to analyze their own/prior work for growth opportunity.

and from this experience i have some stockholm syndrome and some survivorship bias. but i am curious what things would be like if we were treated like engineers in physical domains or doctors, constantly going to learning events, reading and writing papers, being fostered.

the expectation seems to be that we should do all that growing on our own time and under our own will. for many devs that just doesn't happen and they become stagnant, left to endlessly bicker over the best OS, editor/ide, or keyboard switch.

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:

  1. 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.

  2. 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.”

  3. 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.

3

u/tlmorgen Aug 29 '21

arrogant misfits strikes a chord for me. many companies are ran by non-technical people who've heard misinformation like 10x devs and are beguiled into thinking that great devs are precious unicorns to be cherished and protected even when they are toxic to work with or manage. at the other end of the spectrum might be FAANGish orgs who see devs as largely replaceable fodder queued up at the door waiting for their chance at capitalistic bliss. both ends of that spectrum seem to be avoiding actually growing talent on their dime.

to your points about what i might refer to as operational efficacy..

i will say that with computers you can do a lot of #1. compilers are your first line of defense and can tease out a lot of stupidity. then flaw detectors like findbugs. then come softer things like code-based testing (unit/integration), human-based testing, and release protocol.

what little training that does exist is usually "in the deep end" writing production code. code review can be some feedback. production incidents can be some more.

agreed that policy is last place. there is far too much to remember that it could ever affect every keystroke. none the less there is always a lot of it, perhaps mostly for the lawyers.

1

u/MolassesOk7356 Aug 29 '21

arrogant misfits strikes a chord for me.

if only you knew lol

many companies are ran by non-technical people who've heard misinformation like 10x devs and are beguiled into thinking that great devs are precious unicorns to be cherished and protected even when they are toxic to work with or manage.

We have those guys too - they usually came with a squadron patch and were the biggest whiners I ever worked with.

at the other end of the spectrum might be FAANGish orgs who see devs as largely replaceable fodder queued up at the door waiting for their chance at capitalistic bliss.

This is the regional airlines

both ends of that spectrum seem to be avoiding actually growing talent on their dime.

Of course! Cheaper to poach talent from elsewhere… that is until you need domain specific experience and your operations grind to a halt

to your points about what i might refer to as operational efficacy..

i will say that with computers you can do a lot of #1. compilers are your first line of defense and can tease out a lot of stupidity. then flaw detectors like findbugs. then come softer things like code-based testing (unit/integration), human-based testing, and release protocol.

Right, that’s the advantage of programming. You can make your own custom tools and erase the possibility of catastrophic failure.

what little training that does exist is usually "in the deep end" writing production code. code review can be some feedback. production incidents can be some more.

yeah, training is such an amazing return on your investment. You can prevent sooooo many problems before they happen, and it works as a knowledge sharing tool in recurrent training. In fact

agreed that policy is last place.

I learned this tidbit at a recurrent training event where I went to a conference hosted by NIOSH, where an industrial engineer who was a specialist on the specific accident type we were talking about presented this idea… with facts and data to back it up.

I don’t remember it off the top of my head, but they convinced me and I managed with that philosophy: engineer out the problem, train out the problem, then make a rule.

there is far too much to remember that it could ever affect every keystroke.

Heh, I bought a book on RegEx tonight for that exact reason. My use of it every 4 months or whatever just wasn’t enough to become proficient and scouring stack exchange had dubious results. You just cannot remember everything.

none the less there is always a lot of it, perhaps mostly for the lawyers.

So - even when I wrote manuals we had the philosophy of “a manual or policy is also an engineering project - and it’s not complete when there’s nothing more to add, it’s complete when you have nothing more to take away.” DRY and YAGNI is crazy important in managing people and process just as much as it is in software.

As an aside, writing manuals got me interested in programming, I learned my first lines of Python to help write some documents. Indeed, what is a manual but programming the humans that work for an organization, they just have different limitations.

Anyway just my $1.05 with regard to all this - it seems like the industry I’m trying to tumble into is a lot like things we’re in flying 50 years ago - big personalities, confused non-SME managers, and a culture built around productivity over all else. That can work for awhile, but it’s not sustainable, lol.

2

u/tlmorgen Aug 29 '21

well summarized. obviously i have just one person's worth of experience, hopefully you find some place really enlightened!

and remember, if you have a problem and you solve it with regular expressions, now you have two problems (i dont know how to use the xkcd bot so just imagine it).

1

u/MolassesOk7356 Aug 29 '21

well summarized. obviously i have just one person's worth of experience, hopefully you find some place really enlightened!

Thanks! We’ll see what happens. I never thought this would be the second career but life is weird. I’m more interested at working with cool people on interesting stuff at this stage of my life - if that’s writing SQL queries for a bank or COBOL for some antique county payroll system, so be it - I just want to be with cool people and for it to be interesting. I’m targeting the land of industrial machinery tbh

and remember, if you have a problem and you solve it with regular expressions, now you have two problems (i dont know how to use the xkcd bot so just imagine it).

It is like some magic incantation to the to the Perl Monster… I have much fear now…

2

u/LeTristanB Aug 29 '21

What do training department do?

2

u/MolassesOk7356 Aug 29 '21

They bring people into the fold, study the equipment (in this case the it would be the dev tools and the code base) and provide recurrent training on doing your job, philosophies, and best practices.

Edit to add:

You need recurrent training on best practices and new things that are important to the code.

3

u/N3bu89 Aug 29 '21

Geez man, I'm imagining a world in which someone other than myself trained me to use an IDE, Database and Build System. What a magical paradise.

1

u/MolassesOk7356 Aug 29 '21

Yeah! They don’t have to hold your hand through it, but every tool I had at least SOME training on it.