Skip to main content

Making Connections: Epos Now & Kevlin Henney

Norfolk is very lucky to have a thriving tech scene, one which supports growth and encourages its members to help each other where they can. Adrian Pickering from Epos Now experienced this firsthand when he was after an experienced educator for his developers and was introduced to Kevlin Henney.

Adrian saw Kevlin give a talk on ineffective coding habits in 2015 at the annual nor(DEV):con and thought he might be the right person to help train his developers. "He’s a world-class speaker and educator of object-orientated programming best practices.  More than just being hugely capable and knowledgeable, Kevlin is witty and charming, making his lectures pleasurable and memorable. He gave a two-day workshop on code quality, TDD and SOLID practices for our developers at Epos Now, with a lecture-style presentation on day one and a workshop on day two.”

"I ran a software craftsmanship seminar and workshop for them” says Kevlin "covering a range of development practices from alternative ways to think about code and techniques to testing approaches and how to improve their existing code and practices.”

Not being a native Norfolk-ian, Kevlin was in a unique position to see our tech scene from an unbiased point of view. "It seems to have a particular character, very much its own, well interconnected and vibrant. My hometown of Bristol has an increasing number of technical meetups, often very focused (by technology, by process or by discipline for example), and a couple of conferences, but the style and connectedness feels quite different.”

"There are a few key players in the Norfolk tech scene who are fundamental to its very existence and growth” Adrian explains. "These include Paul Grenyer, Huw Sayer, Fiona Lettice, John Fagan and Dom Davis (and countless others). They help to ensure that local events are inclusive and welcoming and their enthusiasm and drive are contagious.”


Join Norfolk Developers here: http://norfolkdevelopers.com

Comments

Popular posts from this blog

Write Your Own Load Balancer: A worked Example

I was out walking with a techie friend of mine I’d not seen for a while and he asked me if I’d written anything recently. I hadn’t, other than an article on data sharing a few months before and I realised I was missing it. Well, not the writing itself, but the end result. In the last few weeks, another friend of mine, John Cricket , has been setting weekly code challenges via linkedin and his new website, https://codingchallenges.fyi/ . They were all quite interesting, but one in particular on writing load balancers appealed, so I thought I’d kill two birds with one stone and write up a worked example. You’ll find my worked example below. The challenge itself is italics and voice is that of John Crickets. The Coding Challenge https://codingchallenges.fyi/challenges/challenge-load-balancer/ Write Your Own Load Balancer This challenge is to build your own application layer load balancer. A load balancer sits in front of a group of servers and routes client requests across all of the serv...

Catalina-Ant for Tomcat 7

I recently upgraded from Tomcat 6 to Tomcat 7 and all of my Ant deployment scripts stopped working. I eventually worked out why and made the necessary changes, but there doesn’t seem to be a complete description of how to use Catalina-Ant for Tomcat 7 on the web so I thought I'd write one. To start with, make sure Tomcat manager is configured for use by Catalina-Ant. Make sure that manager-script is included in the roles for one of the users in TOMCAT_HOME/conf/tomcat-users.xml . For example: <tomcat-users> <user name="admin" password="s3cr£t" roles="manager-gui, manager-script "/> </tomcat-users> Catalina-Ant for Tomcat 6 was encapsulated within a single JAR file. Catalina-Ant for Tomcat 7 requires four JAR files. One from TOMCAT_HOME/bin : tomcat-juli.jar and three from TOMCAT_HOME/lib: catalina-ant.jar tomcat-coyote.jar tomcat-util.jar There are at least three ways of making the JARs available to Ant: Copy the JARs into th...

RESTful Behaviour Guide

I’ve used a lot of existing Representational State Transfer (REST) APIs and have created several of my own. I see a lot of inconsistency, not just between REST APIs but often within a single REST API. I think most developers understand, at a high level, what a REST API is for and how it should work, but lack a detailed understanding. I think the first thing they forget to consider is that REST APIs allow you to identify and manipulate resources on the web. Here I want to look briefly at what a REST API is and offer some advice on how to structure one, how it should behave and what should be considered when building it. I know this isn’t emacs vs vi, but it can be quite contentious. So, as  Barbossa from Pirates of the Caribbean said, this “...is more what you’d call ‘guidelines’ than actual rules.” Resources & Identifiers In their book, Rest in Practice - Hypermedia and Systems Architecture (‎ISBN: 978-0596805821), Jim Webber, Savas Parastatidis and Ian Robinson describe resour...