It’s an odd day for me, today. Russ and i have been meeting weekly since December, discussing what has evolved into the vgo prototype that he’s announced publicly today. There’s a lot to be excited about there:
Managing build time secrets can be a huge pain with docker. If you’ve built a docker image with private repositories, you might benefit from reading this. There are multiple solutions floating around the internet for this problem. We’ll start with the obviously bad ones and work our way up.
Someone: Did you hear that Facebook/Google uses a giant monorepo? WTF! Me: Yeah! It’s really convenient, don’t you think? Someone: That’s THE MOST RIDICULOUS THING I’ve ever heard.
API-first, or “decoupled”, architecture is quickly becoming the most popular way to create world class digital experiences. The pattern gives developers the flexibility to rapidly innovate, while ensuring future-proof builds that don’t require re-creating the entire CMS for new features.
Most software projects involving more than a few contributors end up with some process for having more than one person look at a piece of code before it gets shipped.
So testing, right? We should do it. The thing is, testing is hard, and good testing is reaaaaaaally hard, and tbh I’m pretty bad at testing. So I end up not testing my apps, and then I feel guilty about it, but I’ll stop you now: you can’t run guilt on Travis.
We've been running Kubernetes for deep learning research for over two years. While our largest-scale workloads manage bare cloud VMs directly, Kubernetes provides a fast iteration cycle, reasonable scalability, and a lack of boilerplate which makes it ideal for most of our experiments.
Twitter Lite uses Redux for state management and relies on code-splitting. However, Redux’s default API is not designed for applications that are incrementally-loaded during a user session. This post describes how I added support for incrementally loading the Redux modules in Twitter Lite.
We all know that unit tests help us to be sure that code works as we expected. And one of the metrics we can use with unit tests is a Code Coverage.
What are the pitfalls about running Java or JVM based applications in containers? In this article, Jörg Schad goes over the challenges and how to solve them. This post is adapted from a session presented at Codemotion 2017.
We’ve just launched a shiny new website for Hartwell Insurance – I’m really proud of it. It was tackled it in a different way to most previous Tomango site builds, using some fancy new tools and some vintage web standards.
To make sure it’s robust (no crashes, no hangs) I decided to fuzz it. Parsing text or binary formats is notoriously tricky.
I came across this blog post on ayende.com. Here Oren Eini tries to see how far he could push a simple ipify style of api on an EC2 by running a synthetic benchmark. He hosts the http server on a T2.nano instance and then uses wrk to benchmark it from a T2.small instance.