Imposter syndrome

[quasi solar]

Guys I am worried about the very small details in my code, by small I mean small stuff such as breaking up even 2 lines of code into functions obsessively trying to right perfect code. It's not allowing me to enjoy coding. I feel like these small questions are blocking me from things that actually matter.

I feel like if I don't write perfect code I'm not as good.

[silk osprey]

perfection is an illusion

no one is perfect

even the best devs u know, even those billion dollar companies end up having critical vulnerabilities in their code

because they do not write "perfect" code

i don't either, and no one does

[silk osprey]

up even 2 lines of code into functions obsessively trying to right perfect code
you are not trying to write perfect code, you are writing bad code

function call is expensive

[quasi solar]

Thanks

How do I learn about all these anyway

How to properly structure code etc?

[tepid plank]

1 assembly instruction SKULL

i remember at school some dude who was a perfectionist wanted me to remove a for loop since it was 'expensive'

and to hardcode it for each item instead, claiming that it wasent bad since it was only like 4 items

[tepid plank]

https://www.youtube.com/@CodeAesthetic i watch this guy

he does good content on this

and he even made a video about what you were talking about, which is too much abstraction

https://www.youtube.com/watch?v=rQlMtztiAoA

[silk osprey]

no?

[tepid plank]

JMP

2 if you count the JPM at the end of the function

anyway its not nearly as bad as some other things

[silk osprey]

a function call requires:

• push the return address
• push arguments (maybe)
• save register values (push to stack)
• do your stuff
• restore all the register values (pop from stack)
• pop the return address from the stack and jump

[silk osprey]

he is not wrong

that's called loop unrolling

that's a compiler optimization

[tepid plank]

idc

it was in a non critical code area where it didnt mater if it took 2 nanoseconds instead of 1

[tepid plank]

and all of this takes how long for your computer to execute?

for most use cases it really doesnt matter unless you are repeatedly calling functions over and over

[tepid plank]

also dont a lot of compilers just put the function right into that part of the code as an optimization

[silk osprey]

100~300 cycles in case it misses all caches (i might be wrong)

[silk osprey]

yes they do, i am just telling how a function call in assembly actually looks like

[silk osprey]

that's exactly why a recursive function will cause a stack overflow after a few thousand iterations while the same code using loop can run technically forever

[silk osprey]

and yes, the compiler can optimize a shit ton of stuff, but depending on the compiler optimizations, writing suboptimal code thinking "the compiler will optimize this" is pure gambling

cherry on the cake, if you're writing code in interpreted languages, function calls are way more expensive than compiled ones as they can't really inline most functions

[silk osprey]

i was thinking about interpreted langs when i said this

[tepid plank]

gj keeping all that in mind in your next hello world program

[tepid plank]

.

[silk osprey]

u realize i frequently write low level and embedded code

i even participate in challenges which requires u to write code which runs as fast as possible

so yeah

thanks for the advice, i will keep that in mind

[tepid plank]

usually you write the code as fast as possible

[silk osprey]

not really

[ionic hull]

If you're a beginner, don't.

Write shitty code

It will get better later on