What do you consider a rite of passage in order to become a real programmer?
>>60498119
Not commenting any of your code, going back and trying to fix/change shit and not understanding any of it.
>>60498119
>What do you consider a rite of passage in order to become a real [insert profession here]?
Making money off it.
>>60498119
Being a kissless virgin your whole life.
>>60498184
Bonus point: Going back over code in a project, thinking "Who wrote this, I can't remember when I've seen code this shitty", and then checking and finding out you wrote it.
>>60498210
this, only people that are "real (insert profession)" would focus only on thier job, none everything else
>>60498119
Adding features to your simple, embedded scripting language until it becomes an abomination.
>>60498119
making your own language, even if it's a toy one
>>60498119
Write your own kernel in asm.
>>60498119
getting rid of windows and installing a real OS
>>60498119
Know C, Python and Haskell.
>>60498119
If you can write useful code for yourself without some kind of tutorial then you are a real programmer!
>>60498119
Realizing that Arch Linux is the superior OS.
Writing a bubble sort from memory
>>60501405
that is cute girl what is his name? vladimir the impaler?
True programmer=make your own compiller.
I made 12 of them already by copy pasting what i found on google in-to notepad+++++
non-retadedly traversing a singly linked list in reverse
>>60502333
Using double pointers?
>>60498184
i never comment, but i always understand it when i go back
>>60502304
she (male) is felix/ferris argyle
>>60502375
best is to reverse the links
>>60502400
How big is your average program you've written though? 15,000+ lines and you still understand it?
>>60498119
Running over CIA niggers.
activated borg implant in the head
>>60498199
almost right.
I'd say: when someone else starts making [more] money thanks to your program
Pulling an all-nighter on friday night running code through gdb, figuring when the bug is at 5 AM, facepalming after seeing all the random crashes were from a single typo, drinking a glass of whiskey and going home.
>>60498491
This. When you write bad code and realize that you will have to read it in the future, you take more precaution to make it readable in the future
Also, spending an obscene amount of time looking for a bug in one place of your code, meticulously going over every line, every operation, every bit of punctuation until you're at the brink of sanity, only to realize that the problem is somewhere unrelated entirely.
>>60504350
Almost right. I'd say covering the costs of a pregnant missus thanks to your codefu
>>60502400
>I can come back to my fizzbuzz and i understand it without comments
>>60498119
Chopping off your own dick and becoming the legendary super programmer.
>>60504786
>I can come back to my fizzbuzz and not understand it without comments
u mad, i write thousands of lines of nodejs spaghetti code with no comments and I can still understand what I did when I come back to it
>>60504839
>Trying this hard
>>60498119
Passing Calculus 101