Communication
Communication in software engineering goes beyond simply transmitting information.
Communication in software engineering goes beyond simply transmitting information. It's the ability to explain technical concepts to non-technical people, to document one's work, and to ensure that developed features are understood and adopted by users. If we don't communicate about what we do, our features don't exist in the eyes of users.
Documenting B2B/Odoo workflow changes
In 2025, we made major changes to the data synchronization workflow between Odoo and the B2B site. The new process for sales representatives — particularly for granting their clients access to the B2B platform — was hard to understand. I documented the changes, explained the new workflow to the sales team, and shared step-by-step tutorials.
Result — The tutorials and documentation greatly helped users adapt to the changes, significantly reducing support requests.
- Proficiency level
- Intermediate level, progressing. Documentation and communication work with non-technical profiles is something I want to greatly improve and eventually master.
- Importance in my profile
- Communication is increasingly central to my role. If we don't communicate, how our creations work may not be understood, and going further, if we don't communicate about what we do, our great features simply don't exist.
- Hindsight and advice
- Writing technical articles and user guides is an excellent exercise to improve communication. Writing forces you to structure your thinking and put yourself in the reader's shoes.
- Medium-term goal
- Reach an advanced level in technical communication. Be able to systematically document changes, train users, and write professional-quality articles.
- Current or upcoming training
- Regular writing of technical articles on my blog, creation of user documentation for new features, and improvement of my technical writing skills.