There is also just something very alienating when you work in large teams where each dev only contributes a small component, a lack of knowledge about the system is not only a good thing there but an expected paradigm to create reusable code.
No. That is to say, it might be common, it might be expected, but it is often not good. Every time I join a new team and am exposed to a new code base, I’m astonished by the amount of absolute shit code that results from reusing shit in ways that it was never build with the idea of supporting.
Why? Because someone was focused on completing a single story as fast as possible and they created a dependency they shouldn’t have. And this grows and festers until you have an unmaintainable nightmare.
In order to build solid reusable code you must build it with that knowledge and intent. I’ll cut my rant off there, but I recently joined a new team and the wounds are all very fresh.
Oh yeah totally, I just meant more as a best case scenario where you have very well documented very specific functions with a very limited scope that are reused throughout.
No. That is to say, it might be common, it might be expected, but it is often not good. Every time I join a new team and am exposed to a new code base, I’m astonished by the amount of absolute shit code that results from reusing shit in ways that it was never build with the idea of supporting.
Why? Because someone was focused on completing a single story as fast as possible and they created a dependency they shouldn’t have. And this grows and festers until you have an unmaintainable nightmare.
In order to build solid reusable code you must build it with that knowledge and intent. I’ll cut my rant off there, but I recently joined a new team and the wounds are all very fresh.
Oh yeah totally, I just meant more as a best case scenario where you have very well documented very specific functions with a very limited scope that are reused throughout.