@herbertograca

I've just published a new post on my blog, about Dev rules of thumb: Views/Templates. You are welcome to check it out, and give me your thoughts about it. :)

This post is part of my Dev rules of thumb series. In them, I leave you with a poster with a few rules I follow for each concept, which you can print out and scatter around your office, and a brief explanation of what that pattern is about. You can also find a PDF of the poster at the bottom of this post, for better quality printing.However, please remember, a dev rule of thumb is a Principle…

I've just published a new post on my blog, about Dev rules of thumb: Value Objects. You are welcome to check it out, and give me your thoughts about it. :)

This post is part of my Dev rules of thumb series. In them, I leave you with a poster with a few rules I follow for each concept, which you can print out and scatter around your office, and a brief explanation of what that pattern is about. You can also find a PDF of the poster at the bottom of this post, for better quality printing.

Value Objects

Value objects are sometimes confused with…

I've just published a new post on my blog, about Dev rules of thumb: DTOs. You are welcome to check it out, and give me your thoughts about it. :)

This post is part of my Dev rules of thumb | DDD Tactical Design Patterns series, a series of posts about Design Patterns commonly used in Domain Driven Design, most of them from the Eric Evans seminal book “Domain-Driven Design : Tackling Complexity in the Heart of Software“. In them, I leave you with a poster with a few rules I follow for each pattern, which you can print out and scatter around…

Documenting Software Architecture When we need to explain to someone else (new developer, product owner, investor, …) how the application works, we need documentation. But what documentation options do we have that can express the whole application build

This post is part of The Software Architecture Chronicles, a series of posts about Software Architecture. In them, I write about what I’ve learned on Software Architecture, how I think of it, and how I use that knowledge. The contents of this post might make more sense if you read the previous posts in this series.

We learn how to code and we build some cool applications, and then we learn…

Reflecting architecture and domain in code In my previous posts of The Software Architecture Chronicles I've talked about many interesting ideas. However, how do we actually put it to practice in our codebase?!

This post is part of The Software Architecture Chronicles, a series of posts about Software Architecture. In them, I write about what I’ve learned on Software Architecture, how I think of it, and how I use that knowledge. The contents of this post might make more sense if you read the previous posts in this series.

When creating an application, the easy part is to build something that works.…

This chapter is a transcript of a paper Brooks wrote back in 1986 titled "No Silver Bullet - Essence and Accident in Software Engineering". In it, Brooks addresses the essential tasks of building software.

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

This chapter was added to the 20-year anniversary edition of 1995 and is a…

Documentation is needed. Others need to understand what our application is, what it does how it does it, how it behaves. Then the question is: What and how to document?

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

Documentation is needed.

Others need to understand what our application is, what…

Plenty of projects, if not the vast majority, end up getting delayed... Some more than twice the initial estimations. This has always happened and I feel it is, sadly, very common. But how does this happen? How can we prevent it?

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

Plenty of projects, if not the vast majority, end up getting delayed… Some more…

The challenge is not simply to build something that "works". It must work in the way the end user needs it, with conceptual consistency, minimal technical bugs, and that can be maintained and extended throughout a long life.

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

Curiously enough, Brooks starts this chapter by mentioning something I say every…

The work quality and efficiency of a crafter depends a lot on the tools at hand. In this chapter, Brooks makes a case for this statement validity and gives a list of essential tools needed for software development.

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

The work quality and efficiency of a crafter depends a lot on the tools at hand.

I…

Experience tells Frederick P. Brooks that the first system built is always barely usable. So many years after the book was published, that is also my experience...

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

Experience tells Frederick P. Brooks that the first system built is always barely…

Why should we have formal documents?

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

Why should we have formal documents? (more…)

In this chapter, Frederick P. Brooks, tells us about performance requirements. Of course, the context was different, so the examples and terminology need some translation to today's context...

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

In this chapter, Frederick P. Brooks, tells us about performance requirements. Of…

8. Calling the shot This chapter deals with estimations, which still are somewhat of a problem nowadays...

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

This chapter deals with estimations, which still are somewhat of a problem…

7. Why did the Tower of Babel fail This seventh chapter is about how a software development department should communicate and how it should be organised.

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

This seventh chapter is about how a software development department should…

6. Passing the word

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

The question this chapter tries to answer is “how shall the manager ensure that…

5. The second system effect The most dangerous points of our career are when we are, undeservingly, extra self-confident in our knowledge and experience. We think we know it all about the problem at hand and how to solve it...

This post is part of a series of posts with my personal notes about the chapters in the book “The mythical man-month” by Frederick P. Brooks. I write these posts as I read through the book, and take notes on the concepts I find more relevant. I do, however, advise reading the book to get the full benefit out of it.

The most dangerous points of our career are the ones when we are, undeservingly,…