Changes, Changes, Changes
On a personal front, 2016 has been a year of great highs and lows.
I left JUST EAT in March, and started working at Yubl where I had the pleasure of working with an amazing group of people and had lots of fun building things with AWS Lambda and Node.js. We took an ailing architecture that was hard to work with and difficult to release (and required downtime to release to production) and transformed it completely in the space of a few months.
The number of production releases went up by more than ten-fold, features were sometimes completed and released into production in a matter of hours. The product was starting to do well and featured by the App Store several times and ranked as high as 4th in the social category.
Then everything came to a crushing and disappointing end as funding issues and the reality of a startup reared its ugly head.
What followed was several weeks of job hunting, during which I learnt a lot:
- London has a vibrant tech scene and there are lots of interesting companies doing amazing things
- most companies are still weary of the new serverless paradigm, many are “interested” but few are taking the plunge
- DevOps is super hyped up (and in my opinion, completely misunderstood by most)
- many companies are buying tickets to the Containerization Train, even though the cheaper, faster and more reliable Serverless Express is right next to it
- the money available in the contract market is ridiculous
- there’s a wave of relatively new consultancy firms (EqualExperts, Contino, 101Ways, etc.) that are following the footsteps of ThoughtWorks and doing good things in the Enterprise Consultancy space
After much soul searching, I decided to follow my heart and go back to the games industry. As of tomorrow, I’ll be starting at Space Ape Games studio in Holborn and working with a Scala-based stack.
Learning and Sharing
I spoke at 19 conferences and user groups, delivering talks on a diverse range of topics : F#, Serverless, Neo4j, Elm and APL. I have learnt a lot along the way, and visited Dubai and Sydney for the first time and they were both memorable experiences.
I prepared and delivered some new talks this year:
- Building reactive systems with AWS Lambda
- AWS Lambda from the Trenches
- Fear and Loathing with APL
- Simplify localization with Design Pattern Automation
I took part in and completed all 25 Advent of Code challenges in F#.
- AWS Lambda – use recursive function to process SQS messages (part 1)
- AWS Lambda – use recursive function to process SQS messages (part 2)
- AWS Lambda – constant timeout when using Bluebird Promise
- AWS Lambda – janitor-lambda function to clean up old deployment packages
- Building a random arts bot in F#
- Ransom notes problem in F#
- Equilibrium index problem in F#
- Exercises in Programming Style – Map Reduce
See you in 2017
That’s it folks, happy new year! Wish you all a very productive 2017
I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.
Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.
Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong