Fortsätt till huvudinnehåll

Clean Architecture

I have just ordered a copy of Robert C. Martin's (Uncle Bob) latest book, Clean Architecture. I firmly believe that a professional software developer should be able to solve complex software tasks, write clean and highly maintainable code, AND have a good understanding of the system's architecture.

Unfortunately I have a large knowledge gap when it comes to software architecture, sure I am aware of different architectures like the layered architecture, the now so popular microservice architecture, event driven architecture, and so on. But my experience in this area is that someone with the title "Software Architecture" draws a lot of diagrams on he thinks that the system should work and then the development teams implements it the way they want it without paying much attention to the diagrams.

Here I think that both the architectures and the developers need to improve. The architectures should be part of the development team and involved in the daily day-to-day coding, sharing their ideas thoughts not only with diagrams but with real live code. And the developers should put some effort into understanding and try to keep the architecture, with guidance from the architecture.

I will be very interesting to see what Uncle Bob writes on the topic.

Kommentarer

Skicka en kommentar

Populära inlägg i den här bloggen

Codility tasks - Part I

I was recently faced with two codility tasks when applying for a job as an Embedded Software Engineer. For those of you who arn't familiar with Codility you can check out their website here:  www.codility.com Task one - Dominator The first task was called Dominator. The goal was to, given a std::vector of integers, find an integer that occurs in more than half of the positions in the vector. If no dominator was found -1 should be returned. My approach was to loop through the vector from the first to the last element, using a std::map to count the number of occurences of each integer. If the count ever reached above half the size of the vector I stopped and returned that integer and if I reached the end without finding a dominator I returned -1. So was that a good approach? Well, the reviewer at the company rated the solution as 'pretty ok'. His preferred solution was store the first integer in the array and set a counter to 1. Then loop through the remaining i
7 kommentarer
Läs mer

C# Enum as bit field

Bit field enum Whenever you wish to express combinations of properties of an object, bit fields are a good way to accomplish this. As a simple example, consider a file in the file system. It can be Readable , Writable , Hidden or a combination these. The different attributes can be defined as an enum : [Flags] public enum FileAttribute {   None      = 0b0000;   Readable  = 0b0001;   Writeable = 0b0010;   Hidden    = 0b0100; } To indicate that this enum is expected to be used as a bit field I have defined it with the FlagsAttribute . It is important to understand that the FlagsAttribute does nothing more than making some changes to how the ToString method of the enum works, making it possible to print out all flags. It does not introduce any validation or special treatment of the enum in any other way. I have defined the values of the different fields of the enum using binary representation, this should make it even more clear that this is a bit field and which bi
Skicka en kommentar
Läs mer