Friday Faves: 2014-10-17 3

Another week has come and gone, and I have more links for you. I’m sorry again, but it’s just links again this week. Yeah. I know. This is the second week in a row I’ve done this.

Last week, my fellow software engineer (there are only 2 of us on the team) committed a ton of code for a new feature. Well, it turns out he only implemented about 10% of the features, and of what he did implement, about 90% was so buggy, I had to yank the changes and rewrite them from scratch. I think I left 3-4 lines of his code untouched and wrote another few hundred more on top of that. I also had my own deadlines from my own projects to get done. During this time, I’d read and bookmark articles to let me brain (and temper) cool off between the unending hours of coding frenzy. This means I have links from the week (and one from last week that came out after my post was scheduled,) but that is all. As it stands, it’s almost 6PM on Friday, and I just now finished up with his stuff, and I still have 4 more items in my list of things to do before I can call it a week.

Of course, you didn’t come here to hear me lament about the craptacular job my fellow engineer (and I use that term loosely) did and the hole he left me in.

On with the links!

[Friday Map] New Orlep
RPG characterization wisdom from a 5yo
Abandoned Islands – Iconic Adventure Settings
Troy’s Crock Pot: A Player Race for Your Table
The Hunt 107: Your Tools Are Only As Good As You Are
Memorials To History – an ‘a good name’ extra

3 thoughts on “Friday Faves: 2014-10-17

  1. Mike Bourke Oct 17,2014 7:24 PM

    My first thought on reading this was “The changes were committed without testing!?”

    My second thought was that there appear to be serious communications problems at play throughout the process, as though you and the other engineer weren’t pulling in the same direction from word one of the upgrade project.

    Purpose and required functionality drive specifications. Specifications produce design. Design drives code and code structure. And code delivers exactly what was spelled out back in step one.

    And my third thought was, “Where was the oversight and management?” when all this was going on? It’s supposed to catch things like this before they result in an emergency situation.

    All of which is fine in an ideal world – but every software engineer, programmer, and systems analyst knows that sometimes there are cracks in the system the size of the grand canyon, and entire passenger liners fall through them from time to time. Hopefully you’ll be finished throwing life preservers after this particular vessel soon 🙂

  2. Hungry Oct 17,2014 7:37 PM

    None of his changes hit production. He just dropped them off in our code repository and then ran away to somewhere in the Mediterranean area for a week. He claimed they were done. Our manager/QA guy (yeah, we’re a small team) caught the fact right away that things were not done, and since this was the highest priority item, it landed on my plate to get done. The checks and balances worked just fine…. it was this one asshat that didn’t do his job properly. He had clear specifications and good design. He just didn’t follow them at all. Just one of those weeks. I can’t wait until his contract is up in 6 weeks, then I can move forward with some quality development time.

    Thanks for backing me up with some sympathetic words. It’s greatly appreciated!

Comments are closed.