Software Engineer at Airbus.
Founder of PiecesHub.

• Clear communication is part of engineering, not separate from it.
• Always be proactive and take ownership of your work.
• Most problems are not technical, they are people problems. Build an environment where it is possible for your team to succeed.
• Understand the domain. I mean really understand it.
• Make it as clean and simple as possible without over-engineering. It is probably not your money you are spending.
• Minimize dependencies unless they add real leverage.

PiecesHub is a side project that my friend and I build to learn as developers/entrepreneurs and to help others learn and grow.

Every decision — from technology selection to social media strategy — we own together. That means understanding not just what to build, but why, for whom, and at what cost. We handle everything ourselves: planning, design, implementation, testing, DevOps, analytics, marketing, and social media.

Building your own product from scratch is the ultimate learning experience. If the product fails, our engineering wasn't good enough or the problem wasn't real enough. That feedback loop is unforgiving and invaluable. Even if we fail, we've learned a lot and are better for it.

Most developers underestimate how much their career depends on communication. The ability to explain what you built, why it matters, and what you learned is as valuable as the code itself.

I sometimes review portfolios, CVs, and project descriptions. Not as a formal mentoring service, but because I think the industry benefits when junior developers learn to present their work clearly.

If you want feedback, make it easy for me to help. Include:

• A link to your portfolio or GitHub
• Your current level (student, junior, mid)
• What kind of feedback you are looking for

I will not respond to generic messages. Be specific, be thoughtful, and respect the time of the person you are reaching out to.