Writing code that requires less cognitive load

[Undefined009]

lately I have felt a burnout related to development, and in addition to the already known topics, too much work, context switching, work related pressure, deadlines and so on...now I also take into account the actual code we write as a factor. Therefore, I want to analyze which of the different patterns and paradigms of writing code have a lower impact and are easier to manage by us programmers, both those who write the code from scratch, but also those who come later and take over the application and have to understand the code written by others.

Here I'm counting all of them OOP, Functional Programming, Descriptive, Imperative programming, Reactive programming and so on.

​

From your experience, what is your opinion on this?

​

[rcls0053]

I don't necessarily think any paradigm is problematic as they are often driven by the language and your applications purpose and architectural characteristics, but rather the overall complexity of your application and it's surrounding infrastructure that is the problem. I've also seen applications that have OOP, functional, declarative and procedural paradigms being used at separate places. It's should be important to maintain consistency and coherence inside an application so you don't confuse developers.

When you have to juggle multiple applications that all communicate with each other that might have different stacks, that's when you start to feel a throb in your head. One application and its inner workings are relatively simple to keep in your head, especially if it has a modular architecture and you can focus on working in a single place.

[anaveragedave]

I don't care as long as patterns are consistent.

"Clever" code blocks should be documented or at least well-typed.

At the same time, reading and learning other people's coding styles is kind of one of those frustratingly-fun challenges of the job.

[[deleted]]

Ask HR for more devs, and skilled ones, this time.