Front-end Tips for Back-end Devs
Please log in to watch this conference skillscast.
We all know the value of dependency management, DRY, abstractions and loose coupling when we're building our back-end architectures, but when it comes to writing the UI for our web applications, we often fall back into the habit of copy'n'paste code reuse, invisible dependencies, mixing presentation and behaviour, using inline styles and JavaScript, and other bad habits.
YOU MAY ALSO LIKE:
- Uncle Bob's Clean Code: Agile Software Craftsmanship (in London on 1st - 3rd November 2017)
- Whole Team Approach to Agile Testing (in London on 6th - 8th November 2017)
- Gojko Adzic's Specification by Example: From User Stories to Acceptance Tests (in London on 7th - 8th November 2017)
- Agile Testing & BDD eXchange 2017 (in London on 9th - 10th November 2017)
Thanks to our sponsors
Front-end Tips for Back-end Devs
Dylan Beattie
Dylan Beattie is a systems architect and software developer, who has built everything from tiny standalone websites to large-scale distributed systems. By day, he’s the systems architect at Spotlight (www.spotlight.com), where he works on HTTP APIs, distributed systems, and the architectural challenges of delivering cutting-edge online services in a company with nearly ninety years of legacy. He’s been working with Spotlight since 2000, and his first-hand experience of watching an organisation - and their code - evolving over more than a decade has given him a unique insight into how API design, distributed systems, Conway's Law, working with legacy systems, and recruitment can all influence a company’s products and culture. Alongside his work at Spotlight, Dylan is actively involved in the software development community. He’s involved in running the FullStack and Progressive.NET conferences, and frequently speaks at conferences in the UK and around Europe about software architecture and development culture.