4 ms·
How well can you decouple? That's all I need to know about you. If you can do this well, I (or you) can fix all your bugs quickly. I (or you) can fix (most of)
by wellpast 9y ago
How well can you decouple?
That's all I need to know about you. If you can do this well, I (or you) can fix all your bugs quickly. I (or you) can fix (most of) your performance issues quickly. If you can decouple, you can isolate whatever other areas of ignorance you have with ease.
How well can you decouple? Is it instinctual for you to riddle off code architectures and solutions that are decoupled? It takes time + a value system to acquire this skillset (so that it's instinctual) but once you have it, you can move mountains with code.
The sad thing is our industry doesn't create the conditions for acquiring this skillset. (And rarely, like in this scoresheet, do you see it measured in interviews.)
The usual refrain is "I didn't decouple here or there because, um, it was faster to take on the technical debt."
No, you didn't decouple there nor there because you didn't spend several years falling on your face trying to decouple and failing. Because you were too busy getting paid to crank out whatever works in the shortest possible time, all the while saying "I didn't decouple here or there because it was faster to take on the technical debt." You didn't decouple there because you don't know how to decouple there.
- nnd 9y agoWhat do you mean by decoupling?
- wellpast 9y agoAka, separation of concerns. There's a lot of literature on this. But the key point is that it's an objective measure. Given two equally functional solutions to the same problem, one will be objectively more, less, or equally coupled than the other. It's a demonstrable, measurable skill set; the relative coupling of two separate solutions is generally speaking not some subjective measure.