I agree with this completely. These days it’s too easy to pick up some shiny framework and start making bad software without even understanding what makes it bad.
I also agree (in theory), but not completely. in a professional environment, knowledge of CS fundamentals and understanding what makes a framework bad is only meaningful if the entire team values craftsmanship and quality software. otherwise, your just fighting an uphill battle.
I really agree with this, I have worked with so many bad code base and all the time when you apply for job position 70-80% of the time is to go fix someone else design decisions.
I know, right? it's so frustrating. but, this is also exactly why I disagree that CS fundamentals are important (especially in a professional setting). it's easy to forget that Microsoft and all the FAANG companies are a minority. the vast majority of companies are small and mid-sized shops that barf out garbage code.
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.
I agree with this completely. These days it’s too easy to pick up some shiny framework and start making bad software without even understanding what makes it bad.
I also agree (in theory), but not completely. in a professional environment, knowledge of CS fundamentals and understanding what makes a framework bad is only meaningful if the entire team values craftsmanship and quality software. otherwise, your just fighting an uphill battle.
I really agree with this, I have worked with so many bad code base and all the time when you apply for job position 70-80% of the time is to go fix someone else design decisions.
I know, right? it's so frustrating. but, this is also exactly why I disagree that CS fundamentals are important (especially in a professional setting). it's easy to forget that Microsoft and all the FAANG companies are a minority. the vast majority of companies are small and mid-sized shops that barf out garbage code.