this post was submitted on 03 Jul 2023
18 points (87.5% liked)

Programming

17299 readers
693 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 [email protected]



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] Olap 10 points 1 year ago* (last edited 1 year ago) (11 children)

I keep telling noobs that writing code is like 10% of what they do, and each line of code is a millstone round their neck. Terse, optimal performance (not optimized!) code meeting user requirements is the route to success. And so, doing less is how to go faster, but not what the video means

[โ€“] [email protected] 1 points 1 year ago (1 children)

each line of code is a millisecond round their neck

My man here thinking performance optimizations= fewer lines of code ๐Ÿ˜‚๐Ÿ˜‚๐Ÿ˜‚

[โ€“] Olap 1 points 1 year ago

Let me rephrase then as you missed my point. Each line of code is a millstone around you, your team, and your companies neck. Maintainability usually corellates to LOC. Performance often aligns to LOC. Understanding your Big-O is far easier with less lines for when you do need to optimize. It's easy to write ten lines of code. The wisdom comes from knowing which of those lines you need and which you don't

load more comments (9 replies)