A new breed of peer to peer web technologies like IPFS and Blockchains is coming, that has the potential to change the internet as we know it and make the cloud and servers in general the thing of the past. But how does it all work and how can you benefit from it?
DevOpsDays London 2017 - a breath of fresh air in the land of conferences, showing us how it's done when it comes to Diversity, DevOps and Developers.
Accessibility is a massive topic, and, if you are a developer who doesn't have much control over the designs, it can feel like a lot of it is out of your control.
With a few simple coding changes, we can make our features accessible. In this blog post I will walk you through how I approach making an existing feature accessible in three steps.
You will know that the microservices pattern is very popular right now. For good reason, because it enables Evolutionary Architecture. Each service’s bounded context allows it to evolve on its own roadmap. This gives us great domain-based separation of concerns so we can move very quickly while being more scalable and highly available. When done properly.
After a brief summer hiatus, the React London monthly meet up made it’s way back to Skills Matter in Moorgate. Three very interesting talks followed....
Programming is a vast landscape, though you'd be forgiven to think otherwise. You just might've been sucked into the bubble of Ruby of Rails bonanza for the last 10 years. Or you've been busy solving the halting problem. Or maybe you've been building this language which has types for its type (types) and you have not written a line of it but it's all in your proofs. Or you are upgrading to Angular 5. But lately, you've been having this feeling at the back of your head: is this all there is? Surely not?
Last month I spent a week in a summer school in castle in Bertinoro, Italy, learning about programming language implementation. As soon as I saw friends talking about this summer camp my eyes were shining with excitement. It was a great opportunity for me to know more about research in programming languages and deepen my current knowledge on it.
This month’s React meet-up was at Skillsmatter (near Red Badger’s HQ); there was plenty of pizza, beer and React geekery.
Similar to the three pigs building progressively sturdier houses, we gradually arrived at solutions providing better maintainability and a more efficient developer experience. From beginning with straw, progressing to wood and now iterating further with stone, here is our story.
Find out why Amazon’s "Hello World" example might set you off on the wrong path when it comes to building Alexa Skills.
Have you seen Star Trek? If you haven’t, you should. One of the pieces of future tech that is quietly on display throughout the show is the ability to talk to the computer. Whether it’s asking the computer where someone is or ordering a cup of earl grey tea - the computer has no problem understanding the questions it is asked, and who’s asking them.
Karma Tracker is a Red Badger project, implemented in Clojure, that tracks contributions to OpenSource projects by the members of an organisation.
Neglecting accessibility in development is not an option if you want your end-product to have mass appeal.
Automation should help us to achieve the speed to market we all aspire to. So why do so many teams insist on overloading their test suites to the point that they become a counter-intuitive burden?
Continuous integration servers like Jenkins and CircleCI can display summaries of test results, surfacing information like “which of our tests are slow?” and, crucially, “which of our tests are failing?”. We've released an open-source plugin for Clojure projects to make it easier to identify and diagnose test failures in these summaries.
On the weekend of the 4th & 5th February I went to Brussels to participate on FOSDEM, Free and Open Source Software Developers' European Meeting, for the 3rd time. FOSDEM is the biggest free and open source software conference in Europe and it is the one event I absolutely can’t miss ever since I moved here.
A good test harness is an essential safety net in any code base. Tests save us from ourselves – from writing bad functions, regressing existing features, and creating user journeys with dead ends. Most importantly, they give us a sense of trust that what we release to the world, while never perfect, is at least functional and getting better and better all the time.