My personal journey of balancing Object Oriented Programming (OOP) with Functional Programming (FP) showed me how there are many useful overlapping skills for both professions when it comes to explaining code. The communicative skills needed for knowledge sharing and the foresights/awareness of the “initial situation” are two of the big ones.
Making sure that each component of your enterprise is able to evolve independently of each other is key in evolutionary architecture. But how exactly?
What is code quality? There are a lot of definitions of code quality out there, but I will try to summarize what I understand when someone is talking about code quality. ReadabilityOne of the aspects of code quality is readability. It is very important that code is readable and comprehensive, not only by your teammates, …
After over a year of coding “blind” with a team of Pointers (at peak times we were developing with 6 Pointers simultaneously) we decided to perform a SonarQube checkup. SonarQube is a static code analysis tool, which ensures continuous code quality. As you can see, with 21k lines of code, we noticed 20 bugs and …
The intention of this blog post is to tackle the most occurring obstacles that people find on their way to microservices. SHARED DATASTORE A big obstacle that people will find on their way to microservices, is giving every service its own datastore. This means that they do not share the same datastore with each other. …
This series is intended for an audience that feels comfortable with the basics of Ruby and Rails and wants to learn how to add practical DDD and OOD principles to their toolkit to improve the quality of their code. INTRODUCTION SINGLE RESPONSIBILITY PRINCIPLE (SRP) A core concept behind good OOD and DDD is SRP: giving …
Intro to DDD and ODD coming from Standard Rails, Part 1 Read More »
A lot has already been written on the difference between “Doing Agile” and “Being Agile”.“Doing Agile” boils down to using the agile terminology, because everybody should be agile, but in fact doing business as usual. “Being Agile” is however implementing a new culture, backed-up by a vision and a consistent set of practices. The latter …
PART 2: QUERY OBJECTS INTRODUCTION Typical responsibilities of a Fat Model. Validating data coming through controllers (validations) Keeping track of the relations between the tables (e.g. has_many) Keeping track of events to be fired in it’s lifecycle (e.g. dependent: destroy, after_saves) Constructing queries on the table (e.g. scopes) Doing calculations on itself or on it’s …
Intro to DDD and ODD coming from Standard Rails, Part 2 Read More »
The current feeling about “Agile” in enterprises is a bit on the negative site – Gartner’s trough of disillusionment etc … It seems to be a hype of the noughties (2000-2009) that just doen’t seem to deliver on its promises. The reason why it might not work has a lot to do with “Being Agile” …
ToThePoint Group constitutes of OneDot, ToThePoint and OnTheSpot.
Our address is Veldkant 33a, 2550 Kontich.
