Skip to main content

2023

It was a year of wrapping up a major project I've been working on for several years. Nothing is, of course, ever truly finished in software, so "fully released" is maybe a better choice of words.

In 2023, I was also part of starting a new, presumably soon-to-be megaproject. This led to me switching jobs.

See this tweet

My new employer is an early-stage startup. I have never been on one, so I wanted to know what that is like. We are a close-knit team, quite different from the 100+ member projects I began my career with.

Before fully committing to the new one, I juggled two jobs for six months. I was a (primarily) mobile developer by day and transformed into a web developer by night (actually, I did most of the coding on weekends). My first assignment was related to setting up the frontend, which I ended up doing with NextJS + Tailwind + shadcn/ui combo. 

My working days have changed dramatically. Earlier in the year, I worked on a reasonably stable and mature organization with an established process providing the basis for us in the software team to do sufficiently good quality work without too much time pressure. 

Now, the pace and focus are different, and for good reasons. We keep the iteration speed fast to try out new ideas rapidly. We gradually understand more what our product should be like and adjust accordingly. Fortunately (or unfortunately 🤔), we do not yet have to satisfy groups of customers, each calling after diverse features which give us an edge on the competition against the giants.

My new role is pleasantly varied. I do not work exclusively on the frontend anymore. On a given day, I might work with Terraform in the morning, K8s helm charts after lunch, and finish the day with some UI polishing work. Sprinkle around a couple of one-to-one sessions with team members where we bounce ideas around, and that is my day!

Some highlights include the experience of building a GitOps way of working. We are still in relatively early phases, but most of the infra and deployments are managed declaratively in git.

As a final pat on my own back, Turso CTO Pekka Enberg tweeted the tech talk I held in April about SerenityOS, and the YouTube recording got a nice amount of views for what it is.

Some non-work-related highlights.

I attended four jazz festivals. The most memorable was Valtteri Laurell's "Tigers Are Better Looking" record, which I had on repeat and enjoyed live not only once but twice!

Another unforgettable performance was from Ronald Langestraat at the Odysseus festival in Helsinki, set against stunning seaside views.

I bought (or technically leased) an electric bike for the winter, and while it is a bit of a luxury item, it has been pretty nice. I plan to write about my experiences with it as a winter commuter later in the year.

Comments

Popular posts from this blog

I'm not a passionate developer

A family friend of mine is an airlane pilot. A dream job for most, right? As a child, I certainly thought so. Now that I can have grown-up talks with him, I have discovered a more accurate description of his profession. He says that the truth about the job is that it is boring. To me, that is not that surprising. Airplanes are cool and all, but when you are in the middle of the Atlantic sitting next to the colleague you have been talking to past five years, how stimulating can that be? When he says the job is boring, it is not a bad kind of boring. It is a very specific boring. The "boring" you would want as a passenger. Uneventful.  Yet, he loves his job. According to him, an experienced pilot is most pleased when each and every tiny thing in the flight plan - goes according to plan. Passengers in the cabin of an expert pilot sit in the comfort of not even noticing who is flying. As someone employed in a field where being boring is not exactly in high demand, this sounds pro

Extracting object properties from an IFC file with IfcOpenShell

Besides the object geometry information, IFC files may contain properties for the IFC objects. The properties can be, for example, some predefined dimension information such as an object volume or a choice of material. Some of the properties are predefined in the IFC standards, but custom ones can be added. IFC files can be massive and resource-intensive to process, so in some cases, it helps to separate the object properties from the geometry data. IfcOpenShell  is a toolset for processing IFC files. It is written mostly in C++ but also provides a Python interface. To read an IFC file >>> ifc_file = ifcopenshell.open("model.ifc") Fetch all objects of type IfcSlab >>> slab = ifc_file.by_type("IfcSlab")[1] Get the list of properties >>> slab.IsDefinedBy (#145075=IfcRelDefinesByType('2_fok0__fAcBZmMlQcYwie',#1,$,$,(#27,#59),#145074), #145140=IfcRelDefinesByProperties('3U2LyORgXC2f_hWf6I16C1',#1,$,$,(#27,#59),#145141), #145142

Canyon Precede:ON 7

I bought or technically leased a Canyon Precede:ON 7 (2022) electric bike last fall. This post is about my experiences with it after riding for about 2000 km this winter. The season was a bit colder than usual, and we had more snow than in years, so I properly put the bike through its paces. I've been cycling for almost 20 years. I've never owned a car nor used public transport regularly. I pedal all distances below 30km in all seasons. Besides commuting, I've mountain biked and raced BMX, and I still actively ride my road bike during the spring and summer months. I've owned a handful of bikes and kept them until their frames failed. Buying new bikes or gear has not been a major part of my hobby, and frankly, I'm quite sceptical about the benefits of updating bikes or gear frequently. I've never owned an E-bike before, but I've rented one a couple of times. The bike arrived in a hilariously large box. I suppose there's no need to worry about damage durin