Skip to main content

A Finnish web developer works as a consultant

If you ask a random Finnish web developer to detail the projects they have worked on, I bet YLE (Finnish public broadcasting company) comes up. If you further ask to rank the projects, it would likely score high. The devs I've talked to and the Yle talks I've listened to have convinced me that taking a gig in Yle is indeed one of the most remarkable things to do in Finland.


I'm not sure, but I think a US developer might not see working for the PBS as their career highlight.


As a taxpayer, especially working in IT, it is fantastic that Finnish talent works on major, often publicly funded, megaprojects. The digital services are made well, robustly, and rate among the world's best. The developers enjoy working in such places because that all-knowing mentor colleague is sitting next to you. There are few Twitters or other desirable "web-scale" projects available locally. Not incidentally, this means that the barrier of entry is high to get these jobs.


The Finnish developer career goes as follows

  1. You get your first job wherever you can get it.
  2. After a few years, you go to one of the handful of major consultancy firms
    • You work there on some significant Finnish institution as a consultant
  3. The endgame is that you start to work as a (semi) independent consultant or a freelancer
    • You continue to work on the same projects as before but with a better compensation


The downside is that few developers trickle down to the smaller companies. Sure, that is true by definition (a mega institution gobbles up workforce). Less-known startups and already established companies with decent offerings are struggling to grow. The general "lack of programmers" is not as convincing an argument to me due to the relatively high coder-per-capita ratio.


It's just that the coders who are senior enough to be able to pick the next workplace choose not to go to the smaller companies. To me, that is a shame.


You guessed it; I work for a small, profitable, and stable private software product company. I've not regretted my choice!


Need some convincing to steer off the path mentioned above?


    Can I code without thinking about billable hours? - Every day!

    Guess when the next SAFe planning days are? - Never! 

    Do I get paid better than in the big consultancy firms? - Actually, I do! 

Labels:

Comments

Post a Comment

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
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

Hubristic developer

Almost half of any Finnish generation goes through a shared experience: the conscript army. An integral part of that experience is learning military slang, a set way people in the army talk. The stories told with said jargon often spread outside of the barracks. It is not uncommon to hear strangers bonding together over beers reminiscing and feeling nostalgic about freezing cold nights spent in tents. There is a similar phenomenon detectable among us coders. To be part of the coder tribe, there is at least one type of story that one must master. That is - of course - ranting about legacy codebases. "Can you believe how much of a mess the previous coders left? Hear, hear!" There is no better way to onboard a new team member than to blame some previous B-team for all the murky parts of the system at hand. This can be seen as harmless, a subject for a good  meme . Rarely do we hold real grudges against "the legacy folk" and can be the best of friends in a social gather
Post a Comment
Read more