Test Driven Development requires a fresh take on programming but yields a wealth of benefits when working towards a robust, extendable & upgradable application.
Entering a new project phase: end to end software design from concept to deliverable, including documentation, testing, academic dissertation, retrospective and methodology. A first-hand opportunity to tackle the multiple facets / skills / bodies of knowledge wielded by development teams across the world. Humbling and insanely gratifying.
Today software development projects operate on multiple levels with more emphasis on the user experience and domain relevance. Although supremely powerful code is a given, it needs to go hand in hand with 21st user expectations of system design, usability, multiple platforms & devices…from the ground up! This really points at the necessity of a multi-disciplinary development team including developers, testers, GUI specialists, UI/UX specialists, domain experts and end users…Kanban, anyone?
Product Backlog / User Stories to elicit requirements. UML / class diagrams to guide structure, functionality & system architecture pattern. Test Driven Development to generate outcomes…THEN we code…
Past experience with large scale projects in which the end was dwarfed by the how-to-get-there, agile seems to me to be a panacea that offers a solid process foundation & structure on which to build reusable, adaptable, effective & valuable team solutions.
If you remember the film Jurassic Park, one of the trapped group’s responsibilities was to negotiate the computer run security system. That visualisation of a Unix structure has stayed with me to this day as an excellent (and dramatic) object oriented model.
From Visio / PowerPoint modelling to HTML / CSS prototype to UI design & workable code: modern application development with a visual focus.
The next level of learning underway: object oriented programming, database queries & software development methodologies…
A broken link, an image that won’t load, no hyperlink on text, faulty formatting, old information, old contact details, confusing navigation layout…the number of details that can actually make a website a hindrance not a help…this means that you have to be your own worst critic and guinea pig to iron out all the bugs BEFORE going live.
In a world of increasingly accessible digital tools, training and expertise across multiple media, is the goal to produce work of a universally recognised professional standard? Are the criteria for this standard based on work from a time when production was in the hands of a highly trained and experienced few? How is this changing and what effect is this change having on the overall quality and creativity of new work?