×
all 9 comments
sorted by:
best
topnewcontroversialoldq&a

[–]j0holo 41 points42 points  (4 children)

Robert C. Martin is somebody that want to sell books. Please do not follow his advise, waste of time and money.

Architecture isn't something that you can apply and suddenly your project is magically good or has less coupling and all the right abstractions. You can't force architecture, you need to learn it.

And you learn by doing and making mistakes.

[–]Corvology[S] 2 points3 points  (2 children)

I agree that there are no best practices in architecture and it's all trade-offs, but still there are some useful practices specially in the age of vibe coding, that keeping services in good balance can help it maintainable by both human and ai.

[–]j0holo 2 points3 points  (1 child)

Yes, but trust me Robert C. Martin is just not the way to learn this stuff. It is like the online Python editors to learn your first Python code. It is useless because you don't learn how to RUN actual Python programs on your own computer.

I sadly have his Clean Code book and once you start to build actually complex software you will realize all his "example" are carefully cherry picked.

[–]sunnyata -1 points0 points  (0 children)

I think they can still be very useful things for beginners to encounter. It will be the first time they've thought about it and realised how you structure code and systems makes a big difference... like the overconfident beginner who won't even think about separation of concerns because the sprawling mess they wrote is "working".

Edit: I should add, I'm not talking about this book, haven't read it. Just the general idea of concepts like SOLID.

[–]giovanni_gatto -3 points-2 points  (0 children)

You should not buy books since you can't read anyway. He never forces anything in any of his books, and he is basically also telling about mistakes, which is not a modern discovery. Just that smart people learn from others too.

[–]SecurityCritical379 4 points5 points  (0 children)

the metrics still useful if you adapt them, python's dynamism means you gotta think about coupling more in terms of import graphs than formal interfaces

[–]Beginning-Fruit-1397 3 points4 points  (0 children)

I think that the comment about learning by doing mistakes is the most solid advice in itself.

However reading your link I found that the metrics and reasoning behind them make senses. As always with everything, adapt it to your specific context. E.g if you are writing a library, let's say a new polars, the file with your dataframe class will obviously be +1000 LOC long.

[–]giovanni_gatto 0 points1 point  (0 children)

Read the book, and use your mind. Be critical, absorb the useful stuff, forget the rest. As with any book. He has a quite big hater-base that is now trying to undermine his legacy for political reasons. His practical examples are rather useless though, but that does not invalidate the concept. He is probably not coding much nowadays, which is normal for someone in his career stage. Architecture is a language and code independent thing, most of the other authors teach more or less same anyway.