Please log in to watch this conference skillscast.
Generally they start easy at the beginning, as you add complexity, pressure from business to get features out and new team members, it becomes difficult. Short cuts are taken to deliver faster, the time to restructure code takes longer, the patterns for newer team members seem vague, and the tests become unreadable. These are tradeoffs we continually make as part of our jobs, which becomes the pain we continually have to deal with on a day to day basis.
Through implementing a few architectural patterns right from the beginning, you’ll have the right foundation to continue building on, allowing you to scale not only the application but the codebase with clear patterns for team members.
Please Note These are hands on sessions, so please bring a laptop and power leads as well as
- Visual Studio 2013
- Git (whatever your favourite Git tool is)
- RabbitMQ http://www.rabbitmq.com/
YOU MAY ALSO LIKE:
Building Reactive Applications
Toby Henderson is currently an Application Architect at Huddle. Previously he worked in the finance sector as a developer, operations manager and technical architect for over 15 years. Very fussy about coffee, likes good food and booze.