A software designer website

Language tourist

Gautier DI FOLCO November 12, 2022 [dev] #dev #programming languages #learning #career

When it comes to programming languages, there is a famous quote:

"A language that doesn't affect the way you think about programming, is not worth knowing."

-- Alan Perlis, Epigrams on Programming.

I hate this one, a bit of background.

I started my journey in the software development world in 2003 (I was in college, which let me a lot of time to explore my programming languages, databases, SDLC approaches, deploying patterns, other software fields).

If I have to collect the programming languages I have learnt these last 20 years in the order of learning, it would look like:

I may have forgotten some, or the order might not be correct, but the idea is to be able to adapt to your environment.

That being said, I distinguish multiple level of mastery:

There are multiples ways to look at the previous:

Whenever I learn a new language, I plan/execute my learning as a trip:

I never learn better than in front of the problem (i.e. initially, I have switched to NixOS to learn about Nix).

My posture is the following: I have to contribute to a code base, most of the time it consists of fixing business bugs (either business changed, other business was not understood correctly), which does not take a lot of semantic knowledge.

Sure, from time to time you need environmental/idiomatic knowledge when you have to build a huge/complete (sub-)system, or debug a nasty behavior (it often occurs in non-linear logic, i.e. exceptions most of the time).

For the rest, I rely on architectural and design principles (transposed SOLID principles, coupling, cohesion, etc.)

Another important factor, when arriving at a base code, is to grasp design choices and habits, in my opinions it's one of the biggest challenge as you cannot really be prepared for that (code review and "culture" can help) and it varies a lot. For example, I have worked in a team which has created and maintained three products at the same time, but had really different styles.

To make things clear, I don't like the introduction quote because learning a programming language is mostly about the environment you are envolving in, and what your are about to contribute to it. Once you have covered the mainstreams paradigm, there is few chances your view of the world change. You could stop there, but it will prevent you to collaborate with people who has something to share.

Back to top