Code Performance Does NOT Matter

Code performance doesn't always matter. Instead, focus on code readability and maintainability in most cases. It's rare that performance bottlenecks exist in business logic code. Instead, most performance bottlenecks exist in places like network requests and database requests. Minimizing those are much better ways to improve the overall performance of software applications.

Prepping for your frontend interviews? Use code "conner" for a discount on my course FrontendExpert:

Socials:

[FlanGrande]

Hard disagree. This is how we end up with notepad applications that take 10 seconds to open.

[AscentofTrollbane]

My man’s has never done embedded engineering

[gu]

I appreciate your more nuanced take, but we have to refine it even more: In information systems, often the performance bottleneck is either in networking operations or in reading from disk (think of a server that queries a database). So the advice is: when thinking about performance make sure to view the whole path of a use case through all involved systems. Especially when you're a beginner, you might be tunnel visioned on CPU performance because you start out by reading and writing application code and not thinking about the whole Software architecture and the systems it communicates with.
Thanks for the video! Provides a great chance to talk about this important topic

[zackwumpus]

Client side i guess this is like the speed of architecture itself instead of code But code matters a fuck ton too.

[DefiantStorage]

Who's your customer? The person you're sending pull requests to? Or the end-user?

I guarantee one of those two is going to care about performance.

[alperkaanyildiz]

Agreed, performance first approaches most likely end up with huge technical debts that future engineers has to handle!
👌