52: Front-End Tooling in Legacy Code with Jan Jorgensen
We all strive to be “full stack” developers, but many of us feel more comfortable with either back-end or front-end programming.
We all strive to be “full stack” developers, but many of us feel more comfortable with either back-end or front-end programming.
What does legacy code mean to you? Is it a valuable code that is hard to change or a code you are simply afraid to change; a code that makes you money or a code you are ashamed of?
Lasting success is not measured by past achievements but by the ability to change and adapt to new developments and new demands.
The mere fact that any particular legacy code is still in use is a testament of its sustainability. Today we talk with Dr.
The idea of a “lone genius” unleashing software marvels on the world is mostly a myth. Almost all good software is a product of the exchange of ideas, continuous discussions, and collaborations.
Technical debt is just like a financial debt - incurring it responsibly boosts the development and growth, but failing to repay it in time can lead to bankruptcy and complete failure of the program.
The key to understanding real (rather than perceived) goals of any technological project is to understand the people served by that technology.
We take mental shortcuts every day in order to save our energy while achieving satisfactory results.
Edaqa Mortoray grew up programming. From interface design to scientific simulations, including video games and development products, he has coded a bit of everything.
According to Evgeny Demchenko, technical debt and financial debt have many things in common - if used strategically, they accelerate growth, if not repaid diligently, they hinder it.