I have just read The Pragmatic Programmer and I feel as I had learned years of experience in dozens of days. Of course I have to implement the knowledge acquired. However I really like to study the concept of things, I learn easier when I read concept and try to implement by myself. My first experience doing it was when I have done a course about data structures and algorithms. I have implemented binary tree, linked list and more using Go.
About The Pragmatic Programmer I got some skills to implement on my projects. This book was born in 1999 and its concepts still impacting the way to develop, maybe more impactful now than before.
What will I apply on my existing projects ? I'll starting by logs. Recently I had lots of issues on my job and most of them I might solve faster if I had good logs or some times any logs. Last week I had to deploy just logs in a micro-service to understand what was happening, because the application had more than one try without catch or controller returning just BadRequest().
We know that bad codes are written for many reasons: time, pressure, technical debts or anything else. I suggest you to avoid evaluating the developer without appropriate context and sometimes you'll write bad codes. Because of that you should evaluate the product, the code written excluding the person related with.
I'm trying to apply semantic logs. The goal is increase time spent to find root cause and consequently solve it as soon as possible.
Nowadays we have a lot of artificial intelligence resources and it has been very useful. I believe if you mix it with 'programming for interfaces and not for implementations' you might create good apps and save a lot of time. It has been my favorite way to develop using AI providing context, a way to follow and 'boundaries' to respect.
We are in a tight line between improve productivity and delegate too much to Artificial Intelligence. The approach is the same: focus on the "whys" rather than the "hows."
Top comments (0)