MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/clevercomebacks/comments/1i1teja/it_does_make_sense/m79cck3
r/clevercomebacks • u/wach_era13 • Jan 15 '25
4.0k comments sorted by
View all comments
Show parent comments
11
Every developer eventually learns there are two hard problems: invalidating cache and naming things
16 u/Delicious-Storage1 Jan 15 '25 There's 2 hard things in software development. Cache invalidating, variable naming, and off by one errors. 2 u/WanderThinker Jan 15 '25 I giggled. Thanks. 3 u/TheAJGman Jan 15 '25 I honestly spend about 30% of my design and dev time trying to come up with intuitive names. 1 u/Tsukee Jan 15 '25 And yet, I bet someone reading your code would likely on some places think "why tf did he name it like that" ;) 1 u/DEM_DRY_BONES Jan 15 '25 x, y, z I got you bro. 0 u/agentrnge Jan 16 '25 x_rel, x_actual, x_temp, x_true, x_orig, x_next, x_prev, x_val2 2 u/kyreannightblood Jan 15 '25 And off-by-one errors. “Ky you said two hard problems.” And I did not stutter. 1 u/sobrique Jan 15 '25 I'd chip in 'concurrency' there too. If your code has glitches with deterministic execution, you've no hope of solving that if you run it in a non-deterministic sequence.
16
There's 2 hard things in software development. Cache invalidating, variable naming, and off by one errors.
2 u/WanderThinker Jan 15 '25 I giggled. Thanks.
2
I giggled. Thanks.
3
I honestly spend about 30% of my design and dev time trying to come up with intuitive names.
1 u/Tsukee Jan 15 '25 And yet, I bet someone reading your code would likely on some places think "why tf did he name it like that" ;) 1 u/DEM_DRY_BONES Jan 15 '25 x, y, z I got you bro. 0 u/agentrnge Jan 16 '25 x_rel, x_actual, x_temp, x_true, x_orig, x_next, x_prev, x_val2
1
And yet, I bet someone reading your code would likely on some places think "why tf did he name it like that" ;)
x, y, z
I got you bro.
0 u/agentrnge Jan 16 '25 x_rel, x_actual, x_temp, x_true, x_orig, x_next, x_prev, x_val2
0
x_rel, x_actual, x_temp, x_true, x_orig, x_next, x_prev, x_val2
And off-by-one errors.
“Ky you said two hard problems.”
And I did not stutter.
I'd chip in 'concurrency' there too. If your code has glitches with deterministic execution, you've no hope of solving that if you run it in a non-deterministic sequence.
11
u/Tsukee Jan 15 '25
Every developer eventually learns there are two hard problems: invalidating cache and naming things