Adam Cogan sits down with Marcel de Vries and Terje Sandstrom to breakdown the Software Development process. They discuss:
- Evaluating the process
- Getting the latest and compiling
- Making instructions at the beginning of a project
- Using the best code analysis tool
- Looking at the architecture
- Reviewing the documentation
- Using the best code metrics tools
- The common design patterns
- This follows Rule: Do You Make Instructions at the Beginning of a Project and Improve them Gradually?
- NDepend – ndepend.com
- Metrics Numbers – http://geekswithblogs.net/terje/archive/2008/11/25/code-metrics—suggestions-for-appropriate-limits.aspx
- This follows Rule: Do You Look at the Architecture?
- This follows Rule: Do You Review the Documentation?
- [12:22] The reason for this is that many teams mis-use the concept of agility by stopping proper engineering practices. When you create a solution for a customer, you still need to think about the way you implement it! You can sketch out alternatives using diagrams & Powerpoints etc. to decide on the pros and cons. It’s just good engineering practice. You must decide up front what the purpose of the documentation is. Is it just for you to engineer the right solution, or is it for an actual documentation purpose that perhaps needs to be maintained over time so that it can be handed over to e.g. The party that is going to maintain the code later.
- Enterprise Architect from Australia is a great 3rd party tool for Architects: SparxSystems.com.au
- [22:12] Marcel used the case diagram he showed and used that for the code generation. The sequence diagram he showed was a throw away and was only used to engineer the solution. In this particular project they made a decision about which diagrams they would keep and maintain.
- This follows Rule: Do You Use the Best Tool to Run Code Metrics and Find Dodgy Code?
- A code review should not be one person’s opinion but something you agree on before you start
- This follows Rule: Do You Go Beyond a ‘Done’ and Follow a ‘Definition of Done’
- Code should be read like poetry
- You should add comments about decision you made in the code. Eg. Leaving out a lock statement, since that might trigger a developer later to add it just because he needs to rethink what you already decided. So every time you deviate from a common pattern document in the code, the reader will be able to know what you were thinking of.
- This follows Rule: Do You Know the Common Design Patterns?
- Look out for overuse of containers, dependency injection and reflection
- As a general rule, only add complexity when you need flexibility
- Don’t skim. Instead use the tools to drill into the bad code to look for more bad code. Remember bad code seems to attract more bad code
- Bad code attracts warnings
- Look for lots of setters since they indicate you are handing out your internals and you don’t know the constraints.
About the speaker(s)
Terje works as Chief Software Architect at InmetaCrayon in Norway, in the Consulting division. Most of his work is on advising developers, architects, project managers and testers, in larger companies. He is interested in all aspects of software development, even though coding principles are a favorite. Terje have worked with professional and industrial design and development for far more years, than he want to remember, moving gradually from electronic design over to software design. He holds a M.Sc in Physics from the University in Oslo, graduating with a mixture of physics and informatics/software. Terje has programmed in a lot of different languages, but is very fond of the object oriented ones, from his early exposure to Simula at the university. He is very interested in the theoretical aspects of programming languages, design patterns and everything that have a higher level of complexity. His interests goes into areas like databases, OLAP, UML, functional programming, graphics, 3D and more. He has still to learn there is probably a limit somewhere for how much it is possibly to do. Terje has worked with Microsoft technology since the late 80's, and is familiar with a lot of the products made by Microsoft. He has been a Microsoft Visual Studio ALM MVP since 2008, and worked with the TFS family since the product appeared. Terje is running courses, seminars, workshops and speaks, not only at public events, but a lot at internal company events for larger Norwegian companies. He is blogging actively at http://geekswithblogs.net/terje.
Marcel spends most of his time helping customers build enterprise systems based on Microsoft Technology. He has been working with Microsoft technology since he graduated in Computer Science in 1996. He started mainly with C/C++ and MFC.When Microsoft launched its new .NET platform in he immediately used it to write the first commercial application to go life in the Netherlands based on ASP.NET. Marcel writes articles and whitepapers on .NET, Application Lifecycle Management and Mobile solutions for MSDN, The Architecture journal and local magazines like Microsoft .NET magazine. Marcel is a frequent speaker at conferences like Microsoft TechDays, Visual Studio Live!, Microsoft Tech Ed and local user group events. Marcel is Technology Manager at Info Support and in his role he works as consultant in the Architect role for a variety of Financial and Insurance companies. He also teaches courses on topics like Visual Studio ALM, .NET , Mobile and Web development at the Info Support Knowledge Center.
He is writing actively at his blog.