CODE IT RIGHT CONFERENSE SOFTWARE
CODE IT RIGHT CONFERENSE CODE

Most of us have been working with some kind of legacy systems with lots of technical debt. Let's break it down and see why it works. They not only write code, but solve problems. True СЃraftsmen can be an order of magnitude more efficient than narrowly skilled developers.

The term 'full-stack' is often applied to developers being responsible for all aspects of their work, but XP/craftsmanship practices go further - we should also take our communication, requirements, operations, testing, etc. This leads to inflated teams, inefficient communication, lack of each developer's responsibility, low team's truck factor, and inability to solve production/design problems once and for all instead of applying patches here and there. Nowadays developers split even more into front-end/back-end/Android/iOS/whatever else. In the past there was always the conflict of DB developers vs application developers, or DBA vs developers vs testers.

CODE IT RIGHT CONFERENSE SOFTWARE

Software Craftsman, Co-Founder, Developer CodeborneДevelopers and IT people in general tend to specialize and become narrowly skilled. This new perspective on software development will change how you view code. The specific examples are from real-world codebases like Android, the Linux Kernel. This language-neutral approach lets you prioritize the parts of your system that benefit the most from improvements, so that you can balance short- and long-term goals guided by data. So what if we could mine the collective intelligence of all contributing programmers, and start to make decisions based on information from how the organization actually works with the code? In this presentation you'll see how easily obtained version-control data let us uncover the behavior and patterns of the development organization.

CODE IT RIGHT CONFERENSE CODE

In addition, there's always a trade-off between improving existing code versus adding new features so we need to use our time wisely. Prioritizing technical debt is a hard problem as modern systems might have millions of lines of code and multiple development teams - no-one has a holistic overview. Many codebases contain code that is overly complicated, hard to understand, and hence expensive to change and evolve. Prioritizing Technical Debt as if Time and Money Matters Founder and Developer CodeScene, Author of Your Code as a Crime Scene

Code it right conferense