@AbrahamMarin I like to think that if we believe we have the skills necessary for a successful rewrite, we should already be at the level where we can effectively work with the existing application. Thus, in most cases, a rewrite is not needed.
Code interviews are like citizenship tests. We expect all outsiders to memorize and know all fundamentals by heart. Most of us who are already here would fail those same tests.
@jchacana With sufficient knowledge sharing and mentoring inside the team, I have not found this to be an issue. But eventually, it's up to the team to decide how they want to work. They know their constraints and weaknesses and can design a workflow that suits them.
#continuousintegration Certification Test
💻Every developer commits at least daily to a shared mainline
🛠️Every commit triggers an automated build and test
💣If build and test fails, it's repaired within ten minutes
https://t.co/AcZU2FX6SM
@mattication@martinfowler To me, this is one of the key takeaways. Running #Jenkins against feature branches helps but changes are made in isolation. Regularly rebasing from master helps, but a feature branch is not aware of changes made in other feature branches.