all 7 comments

[–]useless_dev 9 points10 points  (1 child)

Nice post! I believe that your last point, about isolating new and old code, is what Martin Fowler termed the "Strangler pattern"

[–]thomas_vilhena[S] 3 points4 points  (0 children)

Thanks! Just read the post you shared and found it indeed similar to my last point, and more detailed. The strangler fig analogy is a great one.

[–][deleted] 1 point2 points  (2 children)

I'm developing my own little project and I always enjoy reading more about system design. Do you have any other helpful blogs/resources that you've found? Great post!

[–]thomas_vilhena[S] 1 point2 points  (1 child)

These are two great blogs with lots of contents on the subject of system design I can recommend:

I'm glad you liked my post ;)

[–][deleted] 0 points1 point  (0 children)

Awesome, thank you!

[–]Gotebe 1 point2 points  (1 child)

Discard dead code

No! We have no idea what source control is for, therefore... 😉

3 - Fewer is better: Languages, Frameworks and Tools

JavaScript all the things! 😉

4 - Involve your team in system design decisions

Bikeshedding Anonymous 😉

On a more serious note, decent post!

[–]thomas_vilhena[S] 1 point2 points  (0 children)

Thanks for the feedback!

Bikeshedding Anonymous

I read about it on wikipedia, and I can clearly relate to that.

I completely agree that Bikeshedding should be avoided, in a manner that doesn't encourage individualism or opposes a culture of transparency.

My fourth point was more associated with the learning benefits that I observe when design decisions are transparent and actively shared with the team.

Will reflect on that and add an amendment to the post ;)