Skip to content
Hallway
0:00 / 0:00

#prematureoptimization#cleancode

Premature Optimization

CodeAesthetic

438K subscribers • 3 videos on Hallway

YouTube
  • Recommended by 2 people: 2 in engineering communities.
  • An opinion. It argues one side of a question engineers disagree on.

Beginner. No background in the topic needed.

1M views3 years ago2 recommendations

Software designTools and practicePerformance and optimizationSimplicity and complexityRefactoring and legacy code

An explanation of when to optimize code and why premature optimization can be harmful to software design.

When should you optimize your code? Access to code examples, deleted scenes, song names and more at patreon.com/codeaesthetic

Why it's here

2 people recommend this

What people say. Engineers recommend this video for its balanced perspective on when to optimize code versus keeping it simple.

Moments people linked to

u/arocniesin r/Kotlin • Recommends

On “Which one is faster, forEach() or the good old for loops?”

[video Speed does matter! Just don't prematurely optimize. Sure you can save 13.6 milliseconds of loading time because you chose one loop over another... Good stuff, you only spent a whole hour of dev time for those gains. Instead, you could've made batch requests in your app's networking and saved 10 seconds and only spent an hour of dev time. I get it though. Worrying about Big-O on a loop over three elements is something you do right out of college. Remember, we write code for humans, not for computers!
3View on Reddit

u/Lumethysin r/dotnet • Recommends

On “Sharing validation rules with a frontend?”

>For single developer like me "Premature optimization is the root of all evils". If you are a solo dev, you will almost never hit a performance ceiling. Unless you are doing something really, *really* performance extensive like game, video processing or live streaming. 10 or even 20 more api call from a form hardly means anything when it comes to a performance standpoint. And for a solo dev, a simpler deployment and maintaining process is much, much, **much** more valuable than, idk 1ms faster on validation. this video illustrate very well on "premature optimization" topic My advice is: just do server-side validation, and ***when*** it become a problem, add client-side validation later…
2View on Reddit