Schembri on Software
Schembri on Software
Jamie Schembri
A freelance software engineer in the Netherlands with a focus on building value. I'm Jamie. Pleased to meet you! I'm an English/Maltese man on the wrong side of thirty, and I live in the Netherlands with my wife and three dogs. My day job is as a freelance software engineer, primarily with Ruby on Rails. I've worked with everything from tiny agencies to multi-national corporations, which has made me rather versatile.
Latest Posts
Let's delve outside of our comfortable groups of like-minded engineers to explore the unknown once in a while. It's healthy!
A conference can be so much more than just its talks. These were my experiences at Friendly.rb, as a once-skeptic.
The dependency inversion principle is about inverting dependencies. Right? Actually, maybe not.
The Interface Segregation Principle is about designing thin, cruft-free interfaces which results in reduced coupling.
The Liskov Substitution Principle applies to any OOP language. On the surface it is a structural principle, but its true lesson is concerned with behaviour.
We visit the second SOLID principle: the open–closed principle (OCP). Does it still hold up, or is it bad advice in today's agile world?
The Single Responsibility Principle is harder to grasp than its name implies, with a history of misleading definitions. We're going to be pedantic about the definition right out of the gate, to ensure we come away with the right...
The SOLID principles are required learning for software engineers dealing with object-oriented code. Think you know them? Let's take each one apart together.
Dependencies are free chunks of functionality, except when they're not. They come with hidden costs which need careful consideration.
Start writing now with a Ghost blog on PikaPods! This guide takes you through all the steps for a production-ready Ghost install, complete with newsletter support.
One person's complex is another person's simple. Budget complexity intentionally and embrace simplicity of the whole.
An annoyance I came across when running tests in my app, leading to poor visibility.
We use git all the time, so configuring it to work better with us is a worthwhile investment. Here are some changes I like to make.
Some useful snippets for a better time with the Eleventy framework.
We know that premature optimization is the root of all evil, but we can't know if it's premature without a wider context outside of the codebase.