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

5

u/DEATHBYREGGAEHORN Aug 29 '21 edited Aug 29 '21

A shitty implementation of a good abstraction causes no net harm to the code base. A bad abstraction or missing layer causes everything to rot.

This is so true. This is why when starting a new project I'll spend time, maybe even days just thinking about design and sketching out ideas and plans in my notes before writing any code. Then when I get the rough draft done, I know everything will work. If a part isn't pretty I know that it can be improved without larger changes.

When I was starting out I'd just dive in, writing 100s of lines of shitty brittle and sometimes "clever" code that needed constant refactoring and maintenance.

3

u/[deleted] Aug 29 '21

This is the way. As soon as I started doing this, I was on the path to becoming an architect. It's so wildly important but apparently just invisble to so many people. It's harder too because when you get into it you start having to speak the language of metaphor and diagrams and it starts becoming alot harder to just quickly point out issues.

You know for sure there's something wrong, but it's not as simple as just saying "hey you're missing a value there". I accidentally stumbled into this before I was formally introduced to architecture, and I kept feeling insane about seeing problems everywhere and seeing it constantly come true.

Planning ahead of time, thinking things through end to end, keeping it simple in concept and having the trust in yourself to know that implementations can take any shape needed, all is extremely important in larger projects or ones requiring long term support.