Accelerating Development With Technical Excellence
To develop faster you need to develop as though you have all the time in the world. Technical excellence means doing the things right. Doing the things right will get them done in the quickest way. To reach technical excellence you need to start doing things right.
Are you ready to invest time to move faster?
Developing together, as a team
Developing complex products, quickly, is all about teamwork. Who is part of the development process, who jumps in to help, how to work together, how to get it done quickly and efficiently, are all questions that the team should learn to answer.
Change the code so it will be easier to change
When working on legacy code, we need to start by preparing the code for new changes so changes can be applied easily and in a timely manner. We may need to add tests, extract classes and methods, rename symbols, to name some of the most common refactorings. This requires time but will pay off enormously very fast.
Develop high quality code, fast
Development should start with a clear goal, reachable within minutes — a test. The test drives development and the design emerges from writing the code. The design may change with new goals but the software is written in a way that allows the design to change easily.
Our clients' experiences:
“We first decided on which class we are going to work. We decide on …, a Class with 4830 lines!
The method chosen was Mob Programming. All the team works on one computer and the keyboard is moving every 5 minutes to the next developer. Everyone is participating in an open discussion and 1 is typing. We discovered that things go very quick this way.
To make a long story short, we spent most of the day trying to create mocks that will enable running this method. We succeeded. The team was very pleased!”
“Last week N., one of our leading developers, told me she wanted to take a new item from the backlog. Then she told me, ‘before you ask, yes I made sure no one needs my help to complete their current task.’ Then I knew things have changed”
Shachar
Change is possible
The way you write code is at the very core of your organization’s DNA. It is reflected in the way the system is written. Changing it is not trivial. We are aiming for a gradual change. We will help you find a good place to start. Gradually the system will change together with you. It is a worthwhile endeavor.
Research on your own
Read Michael Feather’s Working Effectively With Legacy Code end Joshua Kerievsky’s Refactoring to Patterns. Learn about Cypress and Testing Library. Cucumber is a great framework to implement BDD.
And whatever you do, don’t miss Kent Beck’s Extreme Programming Explained.
Some firms we're helping develop faster, with higher quality
