> I considered widespread and universal about Software Engineering and Computer Science
Could be relative, depending on level of experience, opportunity of hands-on implementation and retention of knowledge.
When I was at an interview from an eCommerce startup, they were all over the case of DB concepts and transactions. Then I was at an enterprise, where they swore by the design patterns and heavily pushed wrong patterns in wrong places because a senior engineer said so. Then I went to a hardware manufacturer, and they had zero concept of any best practices, it was bit manipulations and inline optimization all the way through.
Depending on where one is exposed for a long enough time, some concepts are lost, some are reinforced.
At the end of the day, theories don't bring any values, whatever gets the job done and brings in the money making the machine churn away is crucial.
Could be relative, depending on level of experience, opportunity of hands-on implementation and retention of knowledge.
When I was at an interview from an eCommerce startup, they were all over the case of DB concepts and transactions. Then I was at an enterprise, where they swore by the design patterns and heavily pushed wrong patterns in wrong places because a senior engineer said so. Then I went to a hardware manufacturer, and they had zero concept of any best practices, it was bit manipulations and inline optimization all the way through.
Depending on where one is exposed for a long enough time, some concepts are lost, some are reinforced.
At the end of the day, theories don't bring any values, whatever gets the job done and brings in the money making the machine churn away is crucial.