Since ChatGPT launch in 2022, we have been bombarded by statements and opinions regarding the future of work being altered by AI, software development included.
It is very hard to sort the crazy from the likely in this tsunami of predictions. Today I would like to add my own to this tsunami, based on previous evolutions of our industry.
After working as a developer for 9 years, I switched tracks to a manager position in 2021 (which is not very unusual in this industry). It’s been a bumpy road, but after 3 years I start understanding things and concepts that, retrospectively, were affecting me as a developer before. It looks like I’m starting to grasp them thanks to the fact that being a technical manager forces you to understand both software development and software business.
Today I would like to share some of these things with you.
This blog posts aims to provide an answer to the following question: ‘But WHY does it takes you 2 weeks to implement this basic button?’ 😆
In this blog post I explain that using a programming language is not entirely free.
As a maintainer of several open source projects for now 3 years, I regularly meet people, mostly about an open source contribution. This allows me to experience all kinds of interactions. Most of them are collaborative and great, and keep me thrilled to work in open source. But some of them are spoiled by common beliefs or preconceived ideas about open source. So I’d like to bust one today.
When a user submits a bug report on PrestaShop open source project, we thank him for the report and ask if he is willing to submit a Pull Request to fix it. To which some people answers “I’m sorry? Why should I fix the bug myself? Why should I do your job?” and that is actually a very important and relevant question.
It might sound cool, but magic will actually hurt your code in the long term. Let’s see what this means and why.
To the 1st time open source contributor, to rebase a branch might look both obscure and scary.
How I am almost always able to answer fast to anyone asking me to decide.
Note: this blog post was written as part of my mission as a PrestaShop maintainer
Following previous post about Minor Release Lifecycle, here is more explanations about software lifecycle at PrestaShop, focusing on patch releases and the release process.
