3 ms·
I run a small codebase,where 99% of code is done and dusted and very unlikely to be revisited for years to come. Most of it is written as one off solutions. Cou
by cosmodisk 6y ago
I run a small codebase,where 99% of code is done and dusted and very unlikely to be revisited for years to come. Most of it is written as one off solutions. Could I have written with all the abstractions? Would it have helped?No. So here I am, sitting and thinking whether I'm stupid not to or whether I simply saved the business from using countless hours of unnecessary abstraction.
- jmnicolas 6y ago2 weeks ago was my 11th birthday as the sole developper in my workplace. I embraced KISS maybe 2 or 3 years after starting at this company. I NEVER regretted it. I still maintain a few projects started in my non KISS period. I regret every time I have to touch the code base. Of course YMMV.
- Consultant32452 6y agoMy version of this philosophy is, "Write code a junior developer can maintain." That means unless absolutely necessary don't use unusual language features, use the most common framework on the market for that problem set, no unnecessary abstractions, etc. So far it seems to work well.
- imtringued 6y agoProgramming languages are like any other language. If you use lots of complicated words every time, nobody will understand you.
- raducu 6y agoIt goes both ways. I've seen beautiful abstractions that make a lot of sense, a la DDD that saved companies a lot of money. I've seen a senior architect almost shed a tear when I told him I loved the way he used the Bridge Design pattern in a project and how easy it was to implement some feature because of it (I don't remember the example.)