Every single codebase doing anything nontrivial is mess. Show me a code base that you can marvel at it's beauty, elegance, and how neat and tidy everything is organized and one of two things will be true about it.
1. It has never touched the real world, real hardware, or real users.
2. All the mess is hidden in some dependencies that handle the integration points with the outside world.
You cannot escape the fact that the world is full of sharp edge cases, no perfect abstraction exists, all models of the real world are approximate, there is no architecture that survives changes to business requirements, and all assumptions made about the environment where your code runs will eventually be false, which makes a mess out of code that was once nice and tidy.
I’ve worked on a lot of open source projects and large proprietary code bases that I’d call not-a-mess. I’m not sure what that means to you, to me it means well-engineered in terms of quality criteria, rather than aesthetics, as it seems to be the case for many.
You sound very defeatist to me. I’m under the impression you’ve only worked in teams that don’t have an engineering mindset but rather throw-shit-at-the-wall-and-see-what-sticks coding sweatshops. You may want to look for a new company to regain your pride in your work..
I first thought to post some links to code bases that, in my eyes, aptly counter argue your claim.
Then I realised that you have already solidly placed yourself in a corner and are bound to defend that corner no matter what I am going to post. Since there's no objective measure of what constitutes as a mess (in contrast to what is simply not perfect) it's also easy to convince yourself that the statement always remains true.
Probably in a small close-nit team working on something for no more than a year or two that will be impossible to maintain once the authors move on to greener pastures.
Spivak|3 years ago
1. It has never touched the real world, real hardware, or real users.
2. All the mess is hidden in some dependencies that handle the integration points with the outside world.
You cannot escape the fact that the world is full of sharp edge cases, no perfect abstraction exists, all models of the real world are approximate, there is no architecture that survives changes to business requirements, and all assumptions made about the environment where your code runs will eventually be false, which makes a mess out of code that was once nice and tidy.
eska|3 years ago
You sound very defeatist to me. I’m under the impression you’ve only worked in teams that don’t have an engineering mindset but rather throw-shit-at-the-wall-and-see-what-sticks coding sweatshops. You may want to look for a new company to regain your pride in your work..
jstummbillig|3 years ago
Then I realised that you have already solidly placed yourself in a corner and are bound to defend that corner no matter what I am going to post. Since there's no objective measure of what constitutes as a mess (in contrast to what is simply not perfect) it's also easy to convince yourself that the statement always remains true.
Alas.
singron|3 years ago
soheil|3 years ago
langsoul-com|3 years ago
soheil|3 years ago
Ma8ee|3 years ago