News for hackers. Stuff that matters.

A comment on The Death of Microservice Madness in 2018. Parent comment

Re:The Death of Microservice Madness in 2018 by elgenie on Sunday January 21, 2018 @08:35PM (#16201243)
The critical distinction between "it's all crap, so just ship whatever already" and what the grandparent wrote is that "technical debt" doesn't reside in easily disposable code/components, but rather as may-need-to-be-rectified-but-maybe-not-right-now downsides in what is enormously useful and producing value.

Good developers create code that's prepared for the possibility of being modified repeatedly and becoming foundational; on the other hand, preparing for code/components to be thrown away is a no-op.

[ Parent | on HN ]
Re:The Death of Microservice Madness in 2018 by humanrebar on Sunday January 21, 2018 @11:00PM (#16201818)
> ...preparing for code/components to be thrown away is a no-op.

You might be agreeing, but I find that the bad code that sticks around is bad code that is hard to get rid of. So in that sense, code that is removable isn't a no-op. It takes some effort, for instance, to keep a clear dividing line between two components so that either may be replaced someday.

[ Parent | on HN ]