Skip to main content

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 profane. We should all be passionate developers! I wonder how well a job interview in tech goes if you say that you want to do boring stuff?

Perhaps it should go well. Frankly, the term passionate developer is misleading.

A passionate airplane pilot probably does not fly close to the ground or try to do a 747 loop-de-loop. Similarly, a passionate developer doesn't cowboy-code the whole backend with Remix in one sprint just to get a dopamine rush. A passionate developer is passionate not only about being nice to colleagues but also about code quality in a way where their fingerprint remains unnoticed, much like the airmanship of a skilled pilot. 

My airplane flying friend and I derive pleasure from a clean, by-the-book (by-the-documentation tbh) solution. I'm not too keen on leaving my mark on a codebase. The library I (and only I) love shall remain only on my personal pet projects. That must make me a dull, undesirable 1x engineer.

If everyone writes unpassionate code like me, that is likely a bad thing repressing the growth of new, better ideas. Perhaps a codebase needs, from time to time, someone who rewrites the weird auth part over the weekend in a manic flow state. However, my gut feeling is that we developers are a bit too biased towards doing just that.

Labels:

Comments

Post a Comment

Popular posts from this blog

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...
Post a Comment
Read more

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...
Post a Comment
Read more