Agile programming
It is very common for a team to pick up a piece of software and look at what has been written and decide, it’s simply trash. People believe that it can be built better. That the tools that the legacy software was built in have been superseded and the product …
You often hear technical debt described as a personal failure for software developers of the Scrum team. Why didn’t you code with greater rigor? By creating technical debt, how could you have made life harder on people working in the code? More often than not, technical debt is the result …
Many Java codebases contain code that is overly complicated, hard to understand, and hence expensive to change. It doesn’t have to be that way, and in this presentation you will see how easily obtained version-control data let us uncover the behavior and patterns of the development organization to prioritize and …
Technical debt is a natural byproduct of every successful software system. Great teams learn how to use technical debt to their advantage to improve time to market and balance short-term gains with long term pains. This talk shares some experiences creating, measuring, and paying down technical debt by sharing how …
This talk will bring you on a refactoring journey. It starts from code that is easy to write but hard to read, and gradually advances to a level where the 4 C’s of good code are satisfied: Correctness, Completeness, Clearness, and Compactness.
At Eclipse, new actors are challenging the classic Eclipse IDE: * Che: the next-gen Eclipse cloud, putting the developer workspace and the IDE on your browser * Orion: an extensible browser IDE * Flux: a new message-based architecture for cloud-based developer tooling
