Holy fucking shit!!! This is it then. I work for a big multinational company that make network softwares. They have pages of specification documents, architectural documents and training material. While I worked on piece by piece features assigned to my team for delivery I thought I would never understand how few people at the beginning made this giant software.
What kind of skills they needed to make this software.
After I read 3 chapters of this book;it all make sense now!! Every design and component patterns can be described in terms of concepts told in this book.
Why is this not part of CS major?
Fuck this. I will leave my company to make similar software with my friends. Its very feasible now.
Is there any other book that are deliberately hidden by software (((companies)))??
Listen up, I'm one of the architects writing those documents. No one is hiding those books from you. The issue is, what are we supposed to say? Hey, welcome to our company! Please read this 900 page book and do the exercises. It's degrading. It's not our fault that useless software engineers "learn" specific technologies instead of first principles. Guess what? Your job is to find ways to generalize logic. You failed by not seeking out reapplicable patterns. So, we have to make guides for people like you that apply these principles to our tech stack. It can't make programmers good, but it can make them able to function without wasting the time of good programmers to babysit them.
Jace Peterson
>Design Patterns Back to the 90s we go!
imo the only good thing about the Design Patterns movement/thing was that is brought to light that the constructs we have in our programming languages can contort our solutions such that we sometimes have to choose between things instead of having it all.
People with full mastery of their programming languages already knew pit falls existed, where they came from, and what techniques existed to avoid them.
Jonathan Parker
>The issue is, what are we supposed to say? Hey, welcome to our company! Please read this 900 page book and do the exercises. It's degrading. >It's degrading so its your fault then.
kill yourself faggot.
Adrian Nelson
I paid money to my university to enable me for software development(A part of Computer science). I got shit. Education system is disoriented.
Joseph Cox
Uh... It was part of my CS curriculum. I still have the copy of it that I was required to buy for the class. What shit-tier school did you attend where this was not a requirement?
Want to have your mind blown even further? Pick up "Enterprise Integration Patterns"
David Lee
What are you talking about? Design patterns are essential for architecting any larger application with distinct sub modules. If you really think otherwise then you probably never developed or maintained anything more complex.
Daniel Carter
Did you take some optional course where that book was mandatory or it was regular course?
Listen, no one's going to have job satisfaction if they get hired for 6 figures then has to read what is supposed to be a beginner's book to the subject at hand. Worse than that, we'd have to test them out of it. If you want your company to have a shit reputation because you made your employees do school assignments for the first three months, go ahead. I live in the real world. That's a shitty attitude. Programmers have to learn new things all the time. You can't pay someone to make you learn these things. You should know by now that school isn't going to give you everything you need.
