Balancing innovation with stability is key in managing SaaS legacy code. You explore phased implementations, leveraging existing assets, and continuous learning to maximize legacy code potential. Ideal for tech leads and founders.
Discover effective strategies for managing technical debt and legacy code in software development. This comprehensive guide for founders explores the causes, impacts, and solutions to maintain sustainable growth and high-quality code.
We discuss the challenges of using PHPStan at its strictest level for type checking, particularly with 'mixed' types. It explores solutions like using strval() and creating custom functions, but ultimately, the author opts to lower PHPStan's strictness due to complexity, ending with mixed feelings.
Improve your front-end project's performance and maintainability with our guide to refactoring a codebase. Learn about tackling technical debt, assessing your code, planning a strategy, and exploring refactoring techniques.
Caught in a vendor's web, a client believed a total rebuild was their only option. Discover how we unravelled this myth and saved them time, money, and risk while exposing the industry's flawed advice on web application development.
Should you start from scratch or invest time to refactor your application? * The concepts explained: software rewrite, starting from scratch, and refactoring * When should you create software from scratch? * Making the decision: How to decide to rewrite or refactor? * How to get started with refactoring? Software rewrite vs. starting from...
What is technical debt? How can you fix technical debt and what is the best approach to avoid technical debt?
The set up When developing software, you sometimes come up with ideas that in the end don’t really work out. Depending on the idea and on the time spent finding out it’s a bad idea, it can be challenging to turn back the changes. One of those ideas...
We all had to do it at some point. We’ve all been in the situation where we needed to add some code — maybe a CLI command — just for a one-off operation. Or maybe the code would be needed just for the next month. We promise ourselves to get back...