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:
Thanks to our sponsors
Front-end Tips for Back-end Devs
Dylan Beattie
Dylan Beattie is a systems architect, developer, and Microsoft MVP, who has built everything from tiny standalone websites to large-scale distributed systems. He created his first web page in 1992, and he's been building data-driven interactive web applications since the days of Windows NT 4. He's currently the CTO at Skills Matter in London, where he juggles his time between working on their software platform and supporting their conference and community teams. From 2003 to 2018, Dylan worked as webmaster, then IT Manager, and then systems architect at Spotlight (www.spotlight.com), where his first-hand experience of watching an organisation and its codebase evolve over more than a decade provided him with a unique insight into how everything from web standards and API design to Conway's Law and recruitment ends up influencing a company’s code and culture.