this post was submitted on 09 Sep 2023
71 points (93.8% liked)

Programming

21831 readers
279 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago
MODERATORS
snowe@programming.dev
Ategon@programming.dev
MaungaHikoi@lemmy.nz
UlrikHD@programming.dev
71
Good performance is not just big O (jmmv.dev)
submitted 2 years ago by pnutzh4x0r@lemmy.ndlug.org to c/programming@programming.dev
12 comments fedilink hide all child comments
 

Having a fast and responsive app is orthogonal to “knowing your big Os”. Unfortunately, most tech companies over-emphasize algorithms in interviews and downplay systems knowledge, and I believe that’s one reason behind sluggish apps and bloated systems.

I’ve seen this play out repeatedly. Interviewers ask a LeetCode-style coding question, which is then followed by the ritual of discussing time and memory complexity. Candidates ace the answers. But then… their “real” code suffers from subtle yet impactful performance problems.

you are viewing a single comment's thread
view the rest of the comments
[–] uniqueid198x@lemmy.dbzer0.com 11 points 2 years ago

The vast majority of wall time for most uses is io. You need someone on your team to care about big o, but for most teams, its not the problem