Last week, I shared my one-year plan to become a remote & freelance developer. I ended my post saying that the next step for me would be to choose a development ecosystem to focus on.
Today, being a “software developer” doesn’t say much about what kind of work one is really doing. The daily work of someone coding the behaviour of a factory robot or a flying drone looks nothing like the daily routine of a mobile app developer working in the banking industry. The tools and languages used are very different, as well as the constraints and the skills required. Actually, there exists almost as many different kinds of developer jobs as there are developers!
Continue reading “Which development ecosystem to choose?”
Last week, I shared how I decided to turn back to software developments as a career (and not just a hobby). I explained how I decided to dedicate 10 hours a week to work on my skills.
The next thing I decided was that I would have to make a plan with clear goals at defined dates.
Continue reading “You want to be a coder? Good! So… what’s the plan?”
I’ve always strived to excel at what I do. There are few things more unfulfilling to me than spending most of my waking hours working on things of mediocre quality. No matter what we do, there are always people impacted by the quality of our work, be they colleagues, bosses, customers or end-users. And we have the power to make their lives harder or easier simply by decreasing or improving the quality of the service we are providing. Therefore, striving to be a good professionnal is one of the most loving and caring things anyone of us could do.
This has always been my mantra. And that’s why as soon as I joined Esker, my current company, as a technical support engineer, my main focus has been from day one to be the best I could be.
Continue reading “My journey back to development”
Last week, I wrote about how the way I perceived developers radically improved for the better during the past few years. This was partly due to a better understand of the law of supply and demand, showing that the value on anything on the market is based on the power balance between what’s needed and what’s provided. In other words, the more I need you (your service or your product), the more you can charge for it, and vice-versa. Today, I want to discuss my current perspective on the way developers are recruited, based on my experience. And as you’ll see, the law of supply and demand will again play a big part.
Continue reading “Beware of companies hiring too easily”
Last week, I shared how I reached a very low view of software development (and thus developers) even though I studied computer science at university. I ended my post saying that things started to change when I saw how some of my friends who were passionate about development got great jobs at prestigious companies, with amazing salaries and work conditions.
In this post, I want to share how my perception of software switched from being a commodity to being one of the most valuable assets for today’s companies, and then how this new perception started influencing my career decisions.
Continue reading “The value of (good) developers”
Last week, I shared how I ended up in a management role after studying computer science at university. This was mainly due to my perception of development and developers. My goal for this article is to explain why this was the case.
Continue reading “Why I perceived code as being a commodity”
After my introductory article, some readers told me that the reasons behind my transition from a management-related job to a development job were not clear. But before explaining why I transitioned, you need to understand how I ended up in a management position after my Master’s degree in software engineering.
Continue reading “Why did I work in management in the first place?”
As I’ve explained in my introductory post, I’m going to blog mainly on the topic of clean coding practices.
Now, you may be wondering what is meant by “clean code”. What exactly does it mean for code to be “clean”?
Well, the answer is tricky. It’s as if you were to ask an architect what makes an architecture “good”. I guess that if we were to ask the top 20 architects in the world to answer the question: “What is good architecture?”, we’d pretty much get 20 different answers.
However, by listening to their answers, we may start to get a feel as to what the important criteria are, and also find recurrent and common themes emerging.
In the classic book on the subject I’m currently reading called Clean Code: A Handbook of Agile Software Craftsmanship by Robert Martin (called “Uncle Bob” in the industry), the author shares the answer to the question: “What is clean code?” by five of the most respected software engineers in the industry.
To help you get a feel for what clean code is, I’ve reproduced their answers below.
Continue reading “So… what is clean code? Let’s ask some giants!”
My name is Samuel Path and I’m currently in transition to become a software engineer at my current company called Esker.
Even though I’ve majored in Computer Science for my Master’s Degree and did two internships as a software developer, I was never really interested in development.
During my coursework, I merely did the minimum to get correct grades. My aim was to simply get the degree, since my university was pretty prestigious in France and I knew it would open the doors to many good consulting jobs (my aim was to work for companies such as Accenture, Atos or Capgemini).
Continue reading “Why am I starting this blog”