A framework to deal with technical debt
Are there any specific product management framseworks to deal with technical debt?
Are there any specific product management framseworks to deal with technical debt?
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.
Sometimes the code really is unmaintainable and non-upgradeable. Other times, it might just be old and written in a technology that’s dated or deprecated. Learning how to work with legacy code is a skill in itself. Here’s our playbook for modernizing that old PHP project.
A company should have a vision, but a product should also have one. A product vision may sound like something large corporates work on. It may sound like a waste of time. However, a good product vision helps your team make the right choices while building your product.
When applying for a new job, it is tough to understand the culture of the team you are about to join. Use The Steve Test to evaluate the team culture.
Have trouble documenting your infrastructure? Infrastructure as code might be the solution you are looking for.
Do you have an employee handbook? Are senior people required to spend hours answering questions of colleagues? Here's how documentation can help.
In Pulse, a madewithlove podcast, Andreas talks with leaders from the tech startup and scale-up ecosystem. There are also some podcast episodes where Andreas talks with his own colleagues about everything he comes across when working as a CTO in residence for various clients. Sit back and enjoy Pulse! Episode...
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...