You learn a framework and for three months everything is new. Then you change jobs, the new place uses a different one, and you feel as though you are starting from nothing again.
You are not, and the reason is that you were never really learning the framework.
Almost every tool you pick up is a convenience laid over an idea that is much older and moves far more slowly. The object mapper you are fighting is standing in front of SQL and transactions. The router in your web framework is a thin arrangement of verbs, status codes and headers that were settled before you were born. The queue library is at-least-once delivery and the awkward fact that a message can arrive twice. The orchestration platform is processes, scheduling, and the question of what happens when a machine disappears mid-sentence.
The people who move between tools in a fortnight are not faster learners than you. They already hold the older idea, so the new tool is a vocabulary lesson rather than an education.
The habit that builds this costs about an hour a week. Whenever a tool surprises you, go down exactly one level and find out what it was shielding you from. Your mapper issued four hundred queries where you expected one. Do not learn the annotation that makes it stop. Learn what a join is doing and why the lazy version exists at all. Your deployment rolled itself back. Find out what a health check is actually asking and what the platform does with the answer.
Read the thing under the thing once, properly, and you keep it for twenty years. The framework you learned it through will be unfashionable in five.
There is a fair test of whether you have it. Imagine the tool taken away tomorrow. If the team moved off the mapper, would you still know how to get the rows out. If not, you have learned an interface rather than a machine.
So pick one foundation a year and spend a few weekends on it. How a database handles two people writing at once. How a connection is made and broken. Nothing on that list will be retired while you are working, and everything on it will make the next tool a week instead of a season.
– Asael Shinder
Top comments (0)