4 ms·

Do people out in the industry care about these designpatterns? I'm studying a software engineering course right now and part of it is knowing what things like O

Do people out in the industry care about these designpatterns? I'm studying a software engineering course right now and part of it is knowing what things like Open close principle and dependency inversion are. It just feels like jargon to me

sopooneo 5y ago
I would agree those terms are "jargon", but in this case a legitimate use of it. The concepts are important, and warrant the creation of such specialized vocabulary.
that_guy_iain 5y ago
Care about design patterns, yes. You have two kinda of tech interviews. You have the algorithms ones and according to nearly every review I've heard of people accepting those jobs they don't do algorithms. These are normally FAANG, etc based. For those read cracking the interview or just do what you're doing at your engineering course. Because again as everyone says it's basically that level of knowledge that is required to pass them. The reason people need to study for these are they're basically exams for knowledge you don't use day-to-day but learn at uni. Then you have ones where they care about SOLID, DDD, etc these are normally Java/PHP/Kotlin jobs and more mid-level and enterprsied based. Also project recovery agencies also use these. These care about production knowledge and what you can actually do. These require experience to pass. In my experience the main difference between the two styles is companies that have a massive reputation and can afford to reject lots of compentent people do algorithm tests. Startups who think they're cool also do them at the start. These companies can also afford to have lots of developers who can't actually do high level work because most of their work is very basic and the hard stuff is dealt with by others. Companies who need a large percentage engineers to come in and do hard things and deliver real value will care about your ability and knowledge to write clean code over your ability to do university level quizzes.

sopooneo 5y ago

I would agree those terms are "jargon", but in this case a legitimate use of it. The concepts are important, and warrant the creation of such specialized vocabulary.

that_guy_iain 5y ago

Care about design patterns, yes. You have two kinda of tech interviews. You have the algorithms ones and according to nearly every review I've heard of people accepting those jobs they don't do algorithms. These are normally FAANG, etc based. For those read cracking the interview or just do what you're doing at your engineering course. Because again as everyone says it's basically that level of knowledge that is required to pass them. The reason people need to study for these are they're basically exams for knowledge you don't use day-to-day but learn at uni. Then you have ones where they care about SOLID, DDD, etc these are normally Java/PHP/Kotlin jobs and more mid-level and enterprsied based. Also project recovery agencies also use these. These care about production knowledge and what you can actually do. These require experience to pass. In my experience the main difference between the two styles is companies that have a massive reputation and can afford to reject lots of compentent people do algorithm tests. Startups who think they're cool also do them at the start. These companies can also afford to have lots of developers who can't actually do high level work because most of their work is very basic and the hard stuff is dealt with by others. Companies who need a large percentage engineers to come in and do hard things and deliver real value will care about your ability and knowledge to write clean code over your ability to do university level quizzes.