GuideSmiths are very proud to sponsor St Albans City Youth u13s football team.
Evaluating nightmare.js for end-to-end testing
A couple of months ago I was working on my Carving Up Legacy With Microservices presentation when I was notified of a new github issue raised against the jobs platform my presentation was about. The development team were a few men down so despite being on leave I decided to take a look...
If one of the buzzwords of 2016 is microservices then the other is DevOps, but from what I see, read and hear, many teams are doing it wrong. To really 'get' DevOps you need to understand the problem it was designed to solve, and this requires knowledge of Lean thinking.
As well as tidying up your room, refactoring your code whenever it's needed is essential to make your code habitable.
GuideSmiths are pleased to announce the opening of our new office in Madrid. Working with clients such as TES Global, MATCHESFASHION.COM, Utility Warehouse and The Nido Collection, this new location enables us to significantly increase our high quality talent pool of experienced Node.js developers and quickly adapt our solutions according to client needs.
GuideSmiths are delivering a talk in Madrid on Thu, 3rd of March 2016. The talk will be titledCarving Up Legacy with Microservices. Click here for more details or to sign up. The talk will also be streamed live on the day.
Yes, this article has a cheesy title, but it is appropriate. Trust me. In the computer development business, almost everything we do is a sequel or a remake. Think about it, when was the last time you really started with a blank page rather than basing your work on a previous example?
Like any theoretical field, software is full of checklists and rules of thumb. In this article I shall discuss my own set of hints for distributed systems, which I refer to as "The Four Ts".
The history of software development is peppered with fads and fashions; things which seem like inevitable progress at the but are later discarded as flawed dead-ends. Even temporary infatuations leave their marks; legacy software, books, web content, "best practices" and so on. Among all this debris it can often be hard to identify things which have stood the test of time.
The most frequent question I am asked about microservices is how small should they be. This is the wrong question. It’s not the lines of code that matter, but whether the service does one thing and does it well.