Definitely a halfling barbarian. Alignment: chaotic neutral.
Oh, you didn’t mean tabletop role playing but job roles? Riiiight…
I don’t think that this blog post will ever be complete, and it will always be evolving. But at this point, some of the things that I see myself doing:
Anything related to Continuous Delivery in software. From my perspective, that may include:
- Test Automation – I’ve done this a lot, I liked it and wouldn’t mind doing more of it.
- DevOps – I’m still not sure if DevOps must be a separate role, or if other roles can work better if they apply DevOps principles. That being said, I have done some devops-ish things, I liked it, and I would sure like to do more of it.
- Software Development – There, I’ve put it in writing. I haven’t done this yet in a work context, but I like doing it and learning about it. And really – isn’t test automation also writing software?
Maybe you noticed that in none of these things I mention a specific technology. There may be tech&tools that I already have experience with, and you can read about that in my CV or on LinkedIn, but that is not what this blog post is about. I believe that technologies can (and should) always be learned, and it’s more of an attitude to work quality-driven.
Technical Storytelling or Technical Community Management
Storytelling can help simplify the complexities of new technologies. It’s a combination of technical skills, communication skills and empathy. It’s about supporting a community by creating helpful content, from sample code to tutorials, blog posts(*) and videos; speaking at conferences; and helping improve a product or technology by collecting feedback from the community. I recently read a blog post on this, and I can totally recognize myself there.
(*) Yes, the blog posts that I’m writing now, are also written with that kind of role in mind.
Also have a look at the roles that I am not interested in (but do get a lot of emails about).