Skip to main content

How To Overcompensate For Something

In the spirit of the old name of this blog, Ranting Techno Rave, this is a rant about a personal experience. This happened in the line of duty, so it is on topic. Has anyone else dealt with this kind of thing? Tell me about it.

This title is purposefully "provoking" and if you're the one I'm talking about, you know who you are. This might even apply to you if you're someone else with the same kind of behavior. Maybe you know or have to work with someone that exhibits the particular personality traits I've had to deal with. In whatever way this applies to you now or in the future, beware as much if you are this type of coder as if you have to deal with one of them.

The lone ranger was a terrible cowboy.

Assertive personalities are important. They point out mistakes, instead of allowing problems through inaction. There is an issue of tact, as a line one needs to watch as they walk the road of the assertive. Code review requires assertion as you tell someone, "You're doing it wrong."

Rather than try to artfully explain and avoid the background of this post, I'm going to just present you with A List of Rules When Joining a Team:
  • Don't insult the code you were hired to work on. Don't insult the coders you were hired to work with. This was actually legacy stuff I was trying to replace, myself, but "What kind of an idiot wrote this?" was a bad enough question when you only thought I wrote it. If I had, I would have removed you immediately (and I should have, anyway)
  • Before you write a single line of code, don't claim you can write all of it yourself.
  • When your new team's lead developer leaves you with a set of bugs before leaving on a pre-scheduled holiday, don't let him return to find the existing code base deleted and a bunch of new stub files checked into a new repository.
  • Respond to email.
  • Actually do your job before taking the money.
  • Last, but not least, please, please, please let me be in the position to yay or nay your application a second time.

Comments

Marius Gedminas said…
Interesting. I don't have quite the same reaction to "What idiot wrote this?", but that's perhaps because I'm part of the team who developed the software in question from scratch, and in most of those cases a quick svn blame showed that the idiot in question was myself. Now that I think of it more, I'd be reluctant to use the phrase when working on someone else's code.

The rest of the points sound pretty damning.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be u

How To use Sphinx Autodoc on ReadTheDocs with a Django application

Sphinx is awesome for writing documentation. ReadTheDocs is awesome for hosting it. Autodocs are great for covering your entire API easily. Django is a great framework that makes my job easier. Between these four things is an interaction that only brought me pain, however. I'm here to help the next dev avoid this. Autodocs works by importing your modules and walking over the classes and functions to build documentation out of the existing docstrings. It can be used to generate complete API docs quickly and keep them in sync with the libraries existing docstrings, so you won't get conflicts between your docs and your code. Fantastic. This creates a problem when used with Django applications, where many things cannot be imported unless a valid settings module can be found. This can prevent a hurdle in some situations, and requires a little boilerplate to get working properly with Sphinx. It require a little extra to get working on ReadTheDocs. What makes this particularly h