Juan P. Romano·3d agoWhat makes an engineering team truly autonomousAutonomy is not the absence of managers or process. It is the ability to make good decisions, ship them and own the consequences without…
Juan P. Romano·Nov 6How to decide between building, buying, and doing nothingAlmost every team I have worked with eventually hits the same conversation. Someone proposes a new capability, a vendor pitch lands in a…
Juan P. Romano·Oct 30Why observability should influence architecture from day oneIf you cannot see how a system behaves in production, you do not really know how it was designed.
Juan P. Romano·Oct 23How to modernize a legacy system without breaking the businessThe hardest part of modernization is rarely the new code. It is keeping the old promises while you change everything underneath them.A response icon1A response icon1
Juan P. Romano·Oct 23How to tell whether an engineering team is busy or actually making progressAlmost every engineering team I have worked with looks busy. The board is full, standups are long, pull requests keep moving, and everybody…A response icon1A response icon1
Juan P. Romano·Oct 16Technical debt: what should be fixed and what can waitEvery engineering team I have worked with eventually inherits a backlog full of technical debt, and almost every one of those backlogs…
Juan P. Romano·Oct 9What engineering managers should still understand about the codebaseYou don’t need to write code every day to lead engineers well, but you do need enough technical context to see the system they actually…
Juan P. Romano·Oct 2The hidden cost of adding one more technology to your stackAdding a new technology to a software stack often seems like a relatively small decision.
Juan P. Romano·Sep 25Why simple architectures often outlive clever onesSoftware architecture is often judged at the moment it is designed.
Juan P. Romano·Sep 18When a rewrite is actually worth itFew ideas are more attractive to an engineering team than a clean rewrite of well… everything.