Thanks for the article! Super interesting read. Read halfway, will finish later. The section about Toyota hits close to home. In my field I worked with code just like that so intertwined that you get lost in the essence of what is supposed to do.
I worked closely with a software design engineer with 25+ experience while he was watching me browse the code, he shouted "wth is all this bulls*%!" in Norwegian accent. He looked at me and said, "I don't understand why is so complicated", this function calls this one, and this one calls this one, by the time you go deep enough you have forgotten what you are actually looking for.
Simplicity in design is often forgotten, and we create complex systems without thinking about maintainability. Furthermore we don't document these complex systems very good either.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
This article in The Atlantic is well worth reading:
The Coming Software Apocalypse
theatlantic.com/technology/archive...
Thanks for the article! Super interesting read. Read halfway, will finish later. The section about Toyota hits close to home. In my field I worked with code just like that so intertwined that you get lost in the essence of what is supposed to do.
I worked closely with a software design engineer with 25+ experience while he was watching me browse the code, he shouted "wth is all this bulls*%!" in Norwegian accent. He looked at me and said, "I don't understand why is so complicated", this function calls this one, and this one calls this one, by the time you go deep enough you have forgotten what you are actually looking for.
Simplicity in design is often forgotten, and we create complex systems without thinking about maintainability. Furthermore we don't document these complex systems very good either.