Everything can be made up for—except modularity
Good modularity lets you tolerate crummy code locally and fix it later without breaking everything.
Good modularity lets you tolerate crummy code locally and fix it later without breaking everything.
Don’t ask, “How long will this take?” Instead, ask yourself if you can break your work down into even smaller pieces.
Producing high-quality software involves organizational aspects that go beyond technology and can undermine the CTO’s efforts.
A lack of modularity is costly. Investing in a modular architecture protects your software and prevents massive financial losses.
Here are a few pieces of advice, drawn from my experience working with companies, that I wish I’d had back when I was a manager.
Co-creating your product with your first customers is a good thing. However, that doesn’t mean giving in to all their requests.
Sequential methodologies do not work for business IT, primarily because of the tunnel effect. The alternative? Agility.
Developing quickly without mastery invariably leads to the accumulation of technical debt. Invest in it now—it will cost you less in the long run.
Now, let’s hear from one of my clients, Ovrsea. Antoine, the CTO, explains how the idea to bring in coaching for his teams came about and what it has changed.
Technical debt is dangerous because it accumulates silently, until the day the company hits a wall. CEOs, take the lead.