This month we continued our Made Tech team interview series with our Senior Engineer Lewis Dale to better understand his role and to feature the great work he has been doing.
Cloud and engineering
Learn more about our cloud and engineering service.
Made Tech Team Interviews: Charlene Hunter, Lead Engineer
This month we had our first interview in our Made Tech team interview series with our Lead Engineer Charlene Hunter to better understand her role and to feature the great work she has been doing.
A tale in adopting Alpine Linux for Docker
If you read Wikipedia you will find that Alpine is a Linux distribution that is based on musl (more on this later) and BusyBox.
React and MVC
React is improving the way we build frontends, but I find common patterns are making our apps more complex to write and manage, and more difficult to understand.
Automating infrastructure provisioning with Terraform and Packer
Here at Made we’re always trying out new technologies that will automate repetitive tasks we need to perform on each new project.
Black History Month spotlight: Advice from Black Made Tech Engineers
To celebrate Black History Month, we asked 3 Black Engineers on our team, Renny, Derek and Charlene, about the advice they have for Black people working in tech.
Kubernetes: The Good Parts
This is the start of a blog post series that will discuss the various aspects of Kubernetes. We’ll try to guide you through the myriad of choices when choosing the type of Kubernetes installation, setting up a continuous pipeline to deploy your application to a Kubernetes cluster and how to secure said cluster.
Vim Considered Harmful
Oh no, not another Vim article!
9 Techniques to Support and Improve Software Quality
Most software systems will suffer from a deterioration of quality over time. Codebases become bloated, software is changed to solve problems nobody knew existed when it was initially written, and the cost of change keeps increasing.
9 Benefits of Test Driven Development
Test Driven Development is the practice of writing a test for a piece of required functionality, before writing any implementation code. This test should fail when first run, and then, you write the code to get it to pass. It doesn’t have to be the most perfect code, just so long as the test passes. Once it does, you can then safely refactor your code.
