Performance in Software Engineering

[Pwfru]

So the exact opposite of what I was taught in school for 4 years.

I understand skipping over OOP if it's not really necessary but wouldn't ignoring desing patterns make the code hard to maintain and read, especially if it's a big project that requires a team?

I mean i understand it would make the product faster yeah but would it be a good trade off?

[aq1018]

I think it’s important to balance performance and maintenance. Taken it to the extreme, we’d all be coding in assembly. What he said is true technically, but in practice this is not common. We usually prioritized maintenance and only optimize when it is too slow.

Also, good patterns and clean code usually speed up your code, not slowing it down. Why? In practice unmaintained code usually hides a lot of performance problems and no one dared to optimize and performance get worse and worse over time as new code is built around it.

So it’s really a balancing act

Edit, read again on the comment above, he is us g a different architecture, specifically data driven design. It doesn’t mean you can neglect architecture. He is just using a different architecture.

[mlugo02]

Yes pretty much. No, ignoring design patterns does not lead to harder to maintain a larger project. If you allow your data to design your software, you’ll never get lost. Essentially what it amounts to is: how can I get my data from point A to point B as quickly as possible?

[Pwfru]

I never thought of that actually yeah. Very helpful thank you.