~/ sverzel (Stefan Verzel)
About me: I enjoy computers, programming and reading. When I get tired of electronics, I enjoy astronomy, photography, trekking and beer. And traveling and meeting people.
Sites I frequent are Slashdot, Ars Technica, The Register, XKCD and NASA picture of the day.
I enjoy physics and science in general. When I get bored or find the time, I crank out some code, most likely in Perl (picked up in 1995 by studying in the library by reading Programming Perl). Lately I've found an interest in the Rust language, which has potential to be compact but strongly typed (and fast).
Professionally I usually go where I seem to be most needed, whether programming or "architect" work, including advice, sound technological choices, etc. Today's wide selection of tools and platforms are challenging and navigating them is difficult. I therefore spend some time both learning, helping and guiding where possible.
I focus on getting to a sustainable solution, meaning that it can be maintained for many years. That includes cutting away details which are not imperative. Building sand castles on a beach seems not as worthwhile and sometimes the correct decision is to not solve a problem, if it's not possible to make sure it stays solved for a substantial amount of time.
When it comes to complexity, I think it's a bit troublesome and growing on cloud platforms. Especially handling microservices seems to be a quite large pain in the butt when investigating issues. Currently there seems to be close to zero incentive for vendors to rationalize.
In the old text here I somewhat complained slightly about agile and planning, but whether agile or waterfall or any other methodology seems to all lead straight to hell when applied blindly. Therefore the method is less important than the people working together, where the right people can accomplish gargantuan tasks.
Sites I frequent are Slashdot, Ars Technica, The Register, XKCD and NASA picture of the day.
I enjoy physics and science in general. When I get bored or find the time, I crank out some code, most likely in Perl (picked up in 1995 by studying in the library by reading Programming Perl). Lately I've found an interest in the Rust language, which has potential to be compact but strongly typed (and fast).
Professionally I usually go where I seem to be most needed, whether programming or "architect" work, including advice, sound technological choices, etc. Today's wide selection of tools and platforms are challenging and navigating them is difficult. I therefore spend some time both learning, helping and guiding where possible.
I focus on getting to a sustainable solution, meaning that it can be maintained for many years. That includes cutting away details which are not imperative. Building sand castles on a beach seems not as worthwhile and sometimes the correct decision is to not solve a problem, if it's not possible to make sure it stays solved for a substantial amount of time.
When it comes to complexity, I think it's a bit troublesome and growing on cloud platforms. Especially handling microservices seems to be a quite large pain in the butt when investigating issues. Currently there seems to be close to zero incentive for vendors to rationalize.
In the old text here I somewhat complained slightly about agile and planning, but whether agile or waterfall or any other methodology seems to all lead straight to hell when applied blindly. Therefore the method is less important than the people working together, where the right people can accomplish gargantuan tasks.
Page updated in September 2026
E-mail address: stefan (at) mydomain
PGP key
PGP key
