Insight into my specialization
This page gives some insight into the areas, languages and frameworks I specialize in
I consider myself to be a very well-rounded full-stack developer, with experiences in roles as sys-admin, networking, DevOps, Frontend as well as Backend engineer and developer. The hats which I have worn the most often are both backend and DevOps.
I have a knack for backend development, the design of features, infrastructure and deployments. Anything from integrating a third-party application, to interweaving API's into Microservices. It's something I have been good at, and keep investing time in getting better. As the golden thread on my website already outlines, I am very comfortable with Django and Python. But also know my way around PHP and NodeJS as far as Backend development goes.
Coming from an sys-admin & network-admin background, and having covered multiple roles where DevOps was needed for Django, I have gotten quite accustomed at rolling out my own development pipelines for small to medium projects; or getting familiar fast with more complex pipelines in legacy projects.
- Gitlab, Github
- Terraform, Ansible, Pulumi
- Docker, Vagrant
- Kubernetes, Nomad, Consul
I can plan features and projects from start to finish, organize meetings and get all the stakeholders involved. Of course, its never a clear path, mileage always varies, but having Agile principles stamped into my day-to-day process makes things smooth. I'm experienced with KanBan, Jira, Gitlab, Github for project management. My approaches are always Agile and Scrum. While I currently have no aspirations of becoming a project, product manager or scrum master. As a developer, I know very well how these roles connect with my responsibilities, and how to optimize to work alongside these roles.
Some of the integrations I have customized, worked with or have integrated
I work with the following modules on a regular basis
Python & Django
Infrastructure as code
Django & Python
One of the things which I have been doing since before my career in software. Its also one of the things I feel I am not good enough at yet, and spend considerable time improving. Generally, this works well for writing documentation, for both technical and non-technical uers.
I like to think that I am a great self-organizer, and was made specifically for remote work. In the past decade, I have spend more time working remotely than not, and with great results.
Below you can find a self assessment of my own skills and talents when it comes to working on software. By itself, this chart doesn't say much other than the areas in which I am most comfortable when working on a project. I try to update this whenever something changes.