🔗 Coding without the jargon

As part of my day-job I review, debug and fix a lot of code written by other people.

At the same time, I am tracking various influential people; there are a lot of opinions and ‘best ways’ to do things. Patterns, Continuous Development, Dependencies, Injection, Observers and Subscribers… lots of words with ‘deep’ meanings.

Make no mistake: those patterns and principles are very useful, but their meaning is often obscured by jargon and big words.

In practice, I see very little of those ‘best ways’ in the real-life code I am working on.

This is code, written by real people with real problems, and often there seems to be no time for the ‘big word’ principles.

Given an existing code base, it often seems impossible to go from ‘here’ to ‘there’ so we all just stay ‘here’.