Duplication of Knowledge is the Worst
Code is a Liability
Senior Developers: Trust but Verify
TDD Is Legit, and It’s a Game-Changer
Evidence is King
Duplication of Knowledge is the Worst
Ah yes, the 2 years old Xamarin project where i had the honor to explain the dev who wrote about 90% of it the term "technical debt".
Seems fitting for points 1 and 2 XD
Works now.
Erm. Duplication of code is ok. Removing absolutely every duplicate function is just premature optimization imho.
If you have two different customers with slightly different workflow then go ahead and create two mostly the same functions. When you will have 4 different customers with slightly different workflow, then its a time for refactoring, maybe extract basic same functionality into separate function/object, maybe introduce dynamic workflow using finite automata, maybe extract these functionality to separate modules.. but never do it prematurily.
Imho, sometimes ,removing of duplication very much increases complexity and code became hard to understand and hard to modify.
https://en.m.wikipedia.org/wiki/Rule_of_three_(computer_programming)
Copy for twice, abstract for thrice. I've followed this since I learned it and it's served me well.
Edit: Wikipedia links are fucky
My understanding of that article was that it was not necessarily about duplicated code, but duplicated data. If you have two places storing the same data, and different parts of your app go to each of it, you need to somehow keep them in sync, and that's often a pain.
I'm trying to be very rigorous about avoiding that, duplicated code I'm a bit less rigorous about.
Microservices and document db's go brrrrrrr. Data duplication is completely fine as long as there is only one source of truth that can be updated, all copies must be read only. Then the copies should either regularly poll the source or the source should publish update events that the copies can consume to stay in sync. It's simple stuff but keeps your system way more available and fast than having multiple services talk to a shared db or worse, multiple services constantly fetching data through a proxy.
I spent about 10 of those in roles where my primary function was to write code. The other 10 have involved managing programmers, coaching them, consulting with organizations about how to manage them, running a codebase assessment practice and these days, well, actually content marketing.
Therein lies the biggest lie in development. There is no career path. I've been programming professionally for 25 years, and in all 25 of those years my primary function was to write code, because I turned down any promotion that would put me in management and away from doing what I love.
Why the resentment? There are obviously many career paths, and these can be just as fulfilling, challenging, technical and effective as any other (if done right).
Evidence is king. Basically every point before it is supported by the last point, which is more than a programming point, but a life lesson
This guy seniors, but, where can I vote for him?
I don't understamdduplicatiomn of knowledge. Can someone explain?
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Follow the wormhole through a path of communities !webdev@programming.dev
