In the past I have written about what a microservice architecture looks like and some of the tradeoffs that come with it. One of the biggest gains this architecture brings you is the ability for many people to be working on different projects at the same time. Inevitably the services you are writing will be used or you may need to consume someone else’s API to get your work done.Continue reading »
When we talk about how to design something for a given user experience we are usually discussing the trade offs between a feature request, and the best solutions we can bring to address it. This solution however comes with varying degrees of uncertainty behind how much we actually understand the user’s needs. As discussed in my previous need validation blog post, this can be a lot more deceptive than it originally sounds to get right.Continue reading »
I joined the Wombat team a few months ago, and have been working on the ThreatSim team. We had a bit of a bug backlog, so I’ve been doing lots of bug fixing.Continue reading »
Emberconf 2018 finished about a month ago, and although I didn’t get to enjoy it live I did take the time to catch up over a weekend to see all the talks. Below are some of my favorites!Continue reading »
Most modern developers don’t work with single applications anymore. Single applications use multiple services like MySQL, Redis, and Elasticsearch with Ruby on Rails or Spring Framework or Django. A single application then becomes many application that all use the same services and as developers, we need to work with all of them.
Tools like Docker or Kubernetes help us organize these apps in our live servers but we don’t need a lot of the complex orchestration on our development box, do we? Well, I think Docker Compose could be very useful.
Continue reading »