Weekly developer news – July 13th 2018

So, welcome to the next edition of developer news, the place where I try to narrow down the week’s tech news to the top few items that I think are worth checking out if you are like me, a professional software developing striving to improve.

1 : Building the Google Photos Web UI

First up, as the title suggests it a blog post by a developer on the Google Photos project describing how they approached building the web UI for this. This is a good article to read through, as it describes the requirements they faced well in addition to detailing a number of aspects relating to the solutions they arrived at. It is good to see the different engineering problems they face trying to meet all of the requirements, and good to have a walkthrough describing the approaches that did and didn’t work.

2 : Open offices?

Next is an article by the DHH (Basecamp CTO, creator of Ruby on Rails) putting across his opinions on open offices in the tech industry. As he points out, many studies have shown that they are not an effective way to plan an office space and leads to many frustrations and distractions. They have been shown time and time again to hinder, not help communication. It’s not an issue I encounter too often as I mostly work with, and prefer working with remote developers and teams, but every team I do go into an open office type environment I can certainly relate to those pain points.

3 : Microservices to Monolith

Finally is an article by the Segment engineering team describing how they followed the ‘done way’ of going down the microservice route, and then decided to reverse this, favouring a more monolithic approach instead. In the article, they present a good summary of the complexities and trade offs of each approach. For me, I find most people think micro services is the right design, regardless of their level of understanding as to what that really means, but also regardless of any understanding of the trade offs of different architectural approaches. Far to many teams I see go for what they think is a micro service, go about the design of that badly, and also go for an approach that is optimised to a completely different way of working than the team actually desires.

So, that’s it for this week.

If you have any articles, announcements, tutorials, or anything else you think should be included next week, then just drop me an email.

Leave a Reply