Writings on building software delivery capabilities and delivering digital & technology outcomes for ambitious organisations.
As a polyglot software engineer, I have discovered some disciplines which I have found beneficial to me. My hope is that readers of this article will find the experience I share here profitable to their endeavours as polyglots (or indeed as monoglots).
An increasing number of retailers are exposing core parts of their business through APIs, delivering a more cohesive customer experience across a variety of touchpoints, making it easier to streamline internal operations, and opening opportunities to interface with external channels.
So, you’ve decided that responding to change over following a plan is going to be one of your guiding values. You look at your plans and think “Gosh a lot of decisions went into creating this roadmap, I don’t want to be changing these without good reason”. Then you start getting conflicted over what good reason is, “How can I be confident that rearranging the roadmap is for the best?”.
Oh no, not another Vim article!
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.
A couple of months ago I gave a talk about PostgreSQL, and specifically using the Array datatype, at London Ruby User Group and I wanted to take some time to dive into this in more detail.
So you are trying to build a fast moving digital organisation, one that responds to market opportunities, is decisive and can get things delivered. One of the challenges you may encounter is a thing we call Analysis Paralysis.
Intersectionality, BAME, cis, anonymous hiring, inclusion. These words are likely not on your ticket if you are playing privilege bingo. Like a canary in a coal mine, a lack of understanding of these concepts will likely mean your daily actions reinforce systemic discrimination.
There have been a few rumblings recently between the subculture of TDD-lovers and the rest of the programming community, as always. I’ve heard reports that TDD doesn’t work, that it is snake oil, and that there are studies to suggest that TLD and TDD are no better than each other in a scientific study.
The primary goal of slicing software is to make it cheap to ship, and inexpensive to ship additional features.
About Made Tech
Our mission is to improve software delivery in every organisation. We work with our customers to deliver modern applications and help them move to a faster, leaner, and more agile software delivery model.