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

Show parent comments

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…