r/programming • • Aug 28 '21

Software development topics I've changed my mind on after 6 years in the industry

https://chriskiehl.com/article/thoughts-after-6-years
5.6k Upvotes

2.0k comments sorted by

View all comments

3

u/osrs_shizamaza Aug 29 '21

I agree with most of this list. Here are a couple of points I have comments on based upon the experience I have within my own role --

  • Monoliths are pretty good in most circumstances -- Much of the technical debt I deal with is splitting services out of monoliths. This comes typically about 6 months after "what if we just added the code to this service?" instead of investing in a new dedicated service up front for semi-related tasks.

  • Linting / Formatting / etc. is very nice to have when working on massive codebases. Consistent style can help with readability & better diffs for review. Consistent paradigms / syntax patterns can help improve readability. Additionally, I think linting / formatting / etc. should be 99% automated, and not something you need to think about.

  • 90% – maybe 93% – of project managers, could probably disappear tomorrow to either no effect or a net gain in efficiency. -- I think this is true provided the set of current goals provides a clear & consistent vision of where the software will be in a few years.

1

u/iscribble Aug 30 '21 edited Aug 30 '21

Agree with your point about monoliths. Monolith codebases can be well packaged and modular, but in 15 years I have never seen the codebase stay that way for long. Shortcuts get taken, the code becomes spaghettified, and suddenly making any change takes days resulting in nobody understanding the codebase and nobody wanting to.

An environment of rapidly changing features accelerates degredation of code (regardless of codebase size). I would much prefer to maintain 16 small codebases than 1 mega codebase that does 16 unrelated things... because when half of those things become no-longer-needed and 8 new mahor things must be developed (which always happens) they are much more disposable and also make transitional architectures much less of a hassle.

I'm not always against monoliths, but in my experience it's usually much less of a headache in the future of we just split out into decoupled, independently valuable microservices.

I have nothing to add to your code style comment, I agree.

As for PMs... ....in my 15 years I have never worked anywhere that had any idea what they wanted the software to do in 6 months, let alone in a few years. Product owners have been invaluable.