Pawel Kadluczka

No person can function properly without building mental models to understand the world. The reality is simply too complex to deal with as is, so we need to abstract it. Software is no different. growingdev.net/p/using-mental…

"Weeks of coding can save you hours of planning." It's true that junior engineers tend to fall into the trap of jumping straight to coding without thinking about the problem. However, senior engineers often fall into a different trap: overthinking. growingdev.net/p/overthinking…

Joining a new team is intimidating. There is always so much to learn - new people, new processes, and... a new code base. Learning your new team’s code base is difficult but is crucial to your success. So, how do you do it quickly? growingdev.net/p/how-to-quick…

Coding is essential for junior engineers, but it rarely is the biggest differentiator at senior levels. Every senior engineer is expected to have solid coding skills, and moving up based on coding is rare. If coding is not the skill to grow beyond senior levels, what is it?

One mistake I've seen junior software engineers repeat is their lack of understanding of why they work on tasks they work on. This confusion can be justified by the their relatively small scope but it limits growth and slows downs career progress. growingdev.net/p/understand-t…

As a junior engineer, I felt the urge to jump on each new project that showed on the horizon. As a result, I always had too many projects. To save my butt, if my manager mentioned one of my projects I switched to it. It worked but hurt everyone. growingdev.net/p/want-your-pr…

I learned what unmaintainable software is the hard way. But there is an easy way to ensure the basics and avoid on-call nightmares. growingdev.net/p/a-simple-way…

100% of software engineers who don't keep their skills sharp become obsolete[*]. Many who do keep their skills sharp also become obsolete. It all boils down to what skills they focus on. #softwareengineering #career growingdev.net/p/the-three-ca… * citation needed

Code reviewing is not taught at school, so every software developer must figure it out themselves. Mastering it takes time and practice. To make it easier, I gathered five crucial habits all great code reviewers I know have in common. growingdev.net/p/these-5-habi…

On-call anxiety is real. I've been there, and I know engineers who experienced it. Many factors contribute to it, but from my experience, three stand out ➜ Unpredictability ➜ Too many alerts and incidents ➜ Middle-of-the-night alerts

Every developer wants to get better. But they sometimes don't know how and feel stuck. The good news is that there are a few simple ways to improve coding skills that many developers neglect. Most can be done as part of a regular job, so they don't require additional time.

Happy to share that my post "What it is like to work in Meta's (Facebook's) monorepo" was featured in the DEV community weekly "must-reads" list. This list contains the top 7 DEV community posts of the week. Here is the post: dev.to/moozzyk/what-i…

Overheard: "Code reviews are a waste of time - they don't find bugs! We should rely on our tests and skip all this code review mambo-jumbo." And I agree - tests are important. But they won't identify many issues code reviews will.

Meta uses monorepo to manage its code. I was skeptical about this idea when I joined the company a few years ago. How could it work with such a massive codebase? But I was wrong. I found working in Meta's monorepo to be a pleasure. Here is what working in Meta's monorepo is like

I didn’t know what “gold plating” was until a senior engineer called it out on one of my diffs. I was clueless about what he meant, so I went to talk to him. This meeting ended up being a memorable lesson in my software engineering journey.