Writing simple code in practice with domain driven design
In my previous post, I introduced (shamelessly plagiarised) the idea of simple code. I outlined four rules-of-thumb which, in my experience, serve as useful guides when doing web development:
Writing simple code, or the art of maximising the amount of work not done
As I outlined in my previous post, the so-called principles of SOLID are not principles at all. I actually don’t believe it’s possible to create a universal set of principles for all contexts and domains, so I’m not going to try. Instead, I’m going to outline some practices which have helped me when writing websites and web-services. I call this approach simple code. (I certainly didn’t come up with the name.)
All that is SOLID melts into air...
Every software developer (hopefully) strives to write code which is robust and maintainable. We’ve all worked on projects where a simple code-change broke a million seemingly unconnected features, or random bugs kept popping up in production as soon as the system was used by more than three people, or vast swathes of the codebase were deemed untouchable because nobody could understand how they worked. Over the past three decades, a number of architectural principles, design patterns, cure-alls and get-rich-quick schemes have emerged, promising a life free of production bugs and technical debt.
Focusing development for delivery
Working for a start-up can be a very intense business, which has kept me from updating this blog as much as I'd like. This week I tackle problems that have been a key focus of my work with Intelligent Hack. What does it mean to do Agile and Scrum? Is it simply about following procedures and processes, or running meetings with fancy titles? How do we focus teams on delivery instead of methodology?
READ MORE
Serialising complex objects in Javascript - an introduction to tanagra.js
This week, I introduce a simple, lightweight node.js serialization library supporting ES6 classes (including Maps).
READ MORE
Setting up this blog - why I opted for static content over a CMS
When I decided to start this blog, one of the first decisions I had to make was, what stack should I use to build it? Should I build the site from scratch, use a CMS, use a static site generator such as Jekyll?
READ MORE
Converting .xlsx files to Google Sheets in C#
In my previous post I looked at handling hyperlinks when importing Google spreadsheets via the C# SDK. Today, I continue the GSuite theme with a short piece on importing Excel workbooks into the Google Sheets format via the C# SDK. (Since these posts are so closely related, I decided to post them together.)
Handling hyperlinks in the Google Sheets C# SDK
Recently, when writing a script to import data from Google Sheets into a database using the C# SDK, I came across a problem handling pasted hyperlinks in the source spreadsheet. The solution in the end was, thankfully, fairly straightforward, but Google’s documentation was quite poor, and I found little useful information on the web. Hopefully this post will save a few developers some time (and prevent a few grey hairs in the process).
Welcome to tietokone.io!
Welcome to my blog, where I’ll be sharing my thoughts on writing beautiful, clean code, making remote teams work well together across multiple continents and timezones, doing automated testing in a pragmatic, effective way, and many other topics (including the occasional detour into Star Trek, Golden Age science fiction, and Huddersfield Town).
