>write a big chunk of code
>it compiles without errors
Is there a better feeling than this one /g/entoomen?
It compiles, but does it work?
If it works, best feel.
If not, worst feel.
>Write a fuckton of code
>It actually works
>You don't even know why does it work
>>56339170
>compiling code
it's 2016 gramps
>>56339448
Interpret my dick, bitch
>>56339170
When valgrind says everythings fine
>>56339170
Why are shitskin anime females so qt?
>>56339170
It should always compile without any errors. If you get compilation errors then it means that you don't know the language very well.
The real good feeling is when you write a wall of code in one-shot that works exactly as it's intended.
>>56339497
Because India will take over the world in 2020
>write under 30 lines of code
>over 50 errors
JUST
>>56339170
that's not how you're supposed to do it anon.
> define scope of code
> write tests
> write code - tests fail
> update code
>>56339456
What art thou mean by this
>>56339170
fugging that semen demon
>2016
>producing code that does not compile
>not using a IDE
>>56339170
anon you know that there is no relation between working code and it compiling right?
>>56339170
>Write 100+ lines of code
>Doesn't compile
>Missing a ";"
>>56339170
>likes guns
>programmer
>cutie brownie
Umiko is waif material
>>56339170
>>56339209
>>56339448
>>56339531
>>56339823
>Not using superior High™ Performance™ Interpreter™ Languajes™
Sasuga "C"entoos
>>56339170
I don't understand that feeling, because I know beforehand whether or not my code will compile, since I actually know the programming languages I'm using.
>>56339170
That kinda became the norm for me
Now I feel nothing
>>56339438
That's the absolute worst feeling.
>>56339170
why wouldn't it compile ? the only thing i do after writing my code is hunting for memleaks with valgrind and fixing warnings because of some stupid coding guidelines
>>56340172
>>56340248
I don't know which language is implied here but have you really never forgotten to add semicolons or such?
>>56340344
i write C 90% of the time, and i've never forgot a semicolon.
i sometimes forget closing brackets, but as soon as i start the next line and indentation is screwed up in vim i notice and fix it
Doing a few hours of game dev without import errors or a single program crash.
I can imagine how satisfying that must be though.
so, suddendly everyone is perfect and no one makes mistakes
>>56339170
>2016
>writing code
you are the cucks of technology
>>56340505
not perfect, but after actually programming (e.g. C in my case) for a few years writing code that compiles is the norm. but i still have to hunt for memleaks because of some special case where you forgot to clean up everything properly
>>56339170
Most IDEs will tell you beforehand if it won't compile
However it can fuck up at runtime
There is. Seeing the messageSegmentation fault (core dumped)
always manages to fill me with joy.
>>56340438
I write in about 5 different languages regularly and I just end up forgetting semicolons in languages that need them or adding semicolons in languages that don't need any. The logic is usually right but these small differences in syntax are what usually just break my stuff initially.
>>56340707
>I write in about 5 different languages regularly
wth is your job and what 5 languages ?
>>56339438
That just means you're bad, famalam
>>56339170
>head of the programming team in New Game is literally a poo in loo
$ ./a.out
Segmentation fault (core dumped)
$ _
>>56339170
In c that's not a big accomplishment
>>56339497
Because she is from Okinawa.
>>56339438
It's like you get lost somewhere in its making and at some point you're like fuck I can't think anymore, I'll just compile it and work through the errors. no errors.
>>56339170
Before I learned Haskell, that was the worst feeling possible. (Because it means the bugs were not caught at compile time)
After I learned Haskell, this is the best feeling possible. (Because it means I made no mistakes)
>>56339170
SEMEN
E
M
E
N
DEMON
E
M
O
N
>>56341222
She's okinawan.
>>56339170
cumming in a girl
>write big chunk of code
>does not compile
>get ambiguous compilation error
>spend 5 hours googling stack overflow and forums as to what this could mean
>spend another 5 hours trying dozens of solutions
>rewrite entire code 10x times
>15 hours later it werks
WORST FEEL
>>56344694
don't use c
>>56341481
Currently facing this while using Qt - pls kill me..
>>56339170
>Is there a better feeling than this one /g/entoomen?
Only when you decapitate a weeaboo faggot and then rape his corpse with cumming in their windpipe.
Nothing, I mean nothing bets reviving a 7 year old torrent that had one seeder on it when you downloaded it