Link Dump #90

The weather is great, the reading is here. What else do you need?

Link Dump #89

There's nothing better than something worth reading before the weekend:

Link Dump #88

Ok, so who needs something to read?

Link Dump #87

Sun, coffee and something to read - what more do you need?

Link Dump #86

Don't you think it is a good moment for a break? You've got everything you need:

Link Dump #85

Another amazing week is almost over. Fortunately, there is still something to read:

Link Dump #84

What's good on Friday? Warm cup of coffee and something worth reading:

Link Dump #83

It's reading time again!

Link Dump #82

Hope "your spring" works better than mine ;) But even if not, there's always something to read:

Link Dump #81

I know there is no need to have a reason to read, but did you know that reading makes you smarter ;P

How to make good programming decisions?

Recently I read a great book - "Software Mistakes and Tradeoffs: How to make good programming decisions" by Tomasz Lelek and Jon Skeet. 

I like the idea, the structure, and all the suggestions the authors shared with us. 

The book describes various problems we may face during daily work, how to tackle them, and how to decide which solution brings us the most benefits.

Link Dump #80

New season begins and a new portion of articles worth reading is here :)

Link Dump #79

Do you know what time it is? It's time for the next thing to read!

What is the difference between Document, Event and Command?

What should you use when designing communication between services? When to use Document, Event, and when Command? What are the differences and similarities between them?

 
In this post, I will share a few things that may help you make a good decision.

Link Dump #78

Do you know this great feeling when you simply must read one more page?

You can't stop degradation

There are a lot of patterns, techniques, and approaches that help to write understandable code and build an architecture possible to change. 

The difficult aspect of development is the fact that whatever you will do, the code and the architecture will degrade. 

The question is, why regardless of tries and efforts we cannot change that? 

Link Dump #77

Cheers to all of you who find a time for reading:

Link Dump #76

Hope you booked some time for your reading time:

Infinite work

Improving legacy applications is something I really like to do. Sometimes it is about changing infrastructure, slicing down the monolith, establishing a better architecture for the code base(s), and sometimes it is about all these things. And the work is not only about technical aspects. You need to make sure a supportive culture is in place. A culture that helps continuously pay off technical debt. 

Both tasks are challenging and long-term in nature. You can neither change the architecture nor build an appropriate environment within a month or so. In most cases, this is a plan for years.

And this can be overwhelming.

Link Dump #75

Regardless your weekend plans I think you can find a few minutes for reading:

You need to make decisions to learn how to make right decisions

You don't automatically learn to design architecture when you become a more experienced developer. Even the best programmers may not have the skills required to make decisions that stand the test of time. 

In that case, the question is: how can you learn these skills?

Link Dump #74

This is really great to know that even if you would read all day long there is always something more worth to read:

Link Dump #73

It just started snowing again! That's why you should take a cup of coffee and enjoy the reading:

Best developer as an architect? What can go wrong?

You are working on the application, and there is an idea to move it to a different architecture. It is difficult to convince everyone to take that step, but sometimes you succeed. And then there's a question: who should make architectural decisions? 

Maybe the best people you've got? You want to make it good this time, aren't you? 

Yet, are you sure choosing them is a good idea?

Link Dump #72

What a wonderful day for reading, don't you think?

What is the real root cause of your problem?

The beginning 

There is a project. Code is written, everything is tested, coverage is high, and features get delivered. There are bugs from time to time, but incidents get fixed fast, and no one worries about the situation. Well, business as usual. 

Time passes...

Link Dump #71

It is snowing again! How about a cup of warm coffee and something to read:

Link Dump #70

It is about time to start a new year. And what is the best way to do that? Maybe some reading?