Teemu
Yo! I like to write code. Most of the time I also like to get my hands dirty with all the ops side of things. I like when the system is architecturally well thought, the team is so proud of it, they use the polishing clothe even though it is already impeccable.
In my mind, the team building the system should have all the freedom in the world to make the decisions how to make it and from which matter to make it. The team should be able to focus on its task and not to any unrelated administrative tasks. Whenever I am a team lead, these are my goals.
Currently I'm studying domain-driven design, because it seems to answer to many of the problems I have encountered with various codebases. It clicks so many pieces that have been moving in my head for years finally together.
Bad Code
I like the practicality and a bit more higher level definition of bad code. More often than not these kind of definitions go way too deeply into the details, listing things such as how long a function should be, that are also very much context dependent. Giving these kind of definitions might even be unproductive when they are followed too literally.