7 ms·
I once worked with a person who had an advanced degree in nuclear physics. They were sharp as a tack, a skilled programmer in multiple languages and on several
by doodlebugging 5y ago
I once worked with a person who had an advanced degree in nuclear physics. They were sharp as a tack, a skilled programmer in multiple languages and on several platforms, and grossly over-qualified for the job they had taken but Congress had just killed their position with the SSC in Texas so they needed to switch gears for a while.
Though they were super smart and a rapid typist they were also dyslexic. To make it worse, they would never take responsibility for any mistakes resulting from their failure to double-check the figures entered into the software they needed to run. As a result, we were constantly forced to rerun processes they had worked on because the person never reviewed the parameters they entered into the processing modules before running the jobs. Very simple mistakes like entering 1005 instead of 1500 would cost us a day or more rerunning jobs. It took me weeks to detect the pattern of failures and link them conclusively to this individual since other jobs by other people I supervised also failed but for different reasons.
Once I saw the problem and could easily document the issue I took a few moments to sit with them privately to show what I had found and made the recommendation that they should double-check everything they typed before submitting the jobs so that we could eliminate that class of failures. This person was adamant that I had to be wrong and that they were a perfect typist and somehow someone else was responsible.
Try as I might I could not get them to adopt a simple review-before-submit plan so, since they were a valuable team member who didn't need to lose their job during a period where good jobs were not easy to find, after consulting with my superiors it became my job to review everything they submitted, correct any input parameter fat-fingers or dyslexic inputs, and resubmit those jobs so that we could eliminate those failures.
It was easy enough to do so we made it work and they were never informed I was bird-dogging their work so closely. They remained a valued member of the team until one day they put in their notice.
They had been applying for any positions anywhere that would allow them to use their programming skills on problems that a physicist might find challenging. They had been offered and had accepted a position as a programmer with Raytheon working on missile guidance systems. After their exit, we joked that one day we would hear about a fat-finger mistake sending a missile to an unintended location.
This person was not connected at all to this event since their work with Raytheon was several years after this event occurred (SSC shuttered in 1993). I have no idea what they worked on while there but I hope that someone noticed the issue and insured that two sets of eyes hit everything they typed. Those were the days.
- bbarn 5y agoCan you really be a skilled programmer if you refuse code reviews and constantly ship buggy code? I might be an outlier here, but I absolutely think that makes a shit developer. No amount of code knowledge is worth hiring someone that won't work with others. I absolutely hate the trope of the brilliant genius coder who has to be left alone. The reality of that is exactly what you're describing.
- doodlebugging 5y ago>Can you be a skilled programmer... The answer is no. I agree with you and there is a chance that I could've been less generous in my description. I think they were ashamed to be confronted since they had a more advanced education and experience level than most of the rest of the team. They worked well with everyone, would gladly help others improve skills, had a great personality and sense of humor but their main defect was the unwillingness to accept the fact of their own fallibility, causing production lags and extra work fixing problems that shouldn't have happened. We handled it and it all worked out in the end.
- engmgrmgr 5y agoCan you be a good musician if you always make mistakes while performing? Maybe you’re a better composer or producer then, but it’s on whoever leads the group of musicians to organize that. Jerks who randomly push buggy code straight to master might be the reason you have a job. Most of them probably aren’t, but some of them are the reason a bunch of other people have a job running around fixing stuff and being mad about it. It’s really hard to see yourself as a regulating component in some messy system, but nothing is better for velocity than pissed of engineers heroically fixing all the stuff they hate from some other engineer that’s pumping out mostly working high impact stuff left and right.
- lostlogin 5y agoThis was a good read, thanks. > but I hope that someone noticed the issue and insured that two sets of eyes hit everything they typed. I think you mean ‘ensured’.
- 5y ago