>have issue with code
>not able to solve problem after hours of debugging
>randomly remove a few functions here and there, copy paste from stackoverflow and go crazy with your code
>it starts working
I hate that feeling of ducktaped code, but sometimes its the only way.
>>60159246
Let me give you a few hints .. what you're doing isn't actually coding. You're just flailing around and hoping it works. Also, dumb frogposter.
>>60159246
How do you even know your code is working if you don't understand it? Pro tip: correct results for a few example inputs is not a good indicator of code correctness.
And no, what you describe is never "the only way".
>>60159246
write a mathematical proof on this whiteboard to show that your program works, you should be able to do this.
>>60159246
dumb frogposter
Maybe you just need rest. I tend to be sloppy with fixing problems when I feel tired.
Fucking pajeet, it's not "ducktaped", it's "duct-taped". there's no such thing as a "duck-tape" you chucklefuck
>>60159246
>how to spot your average python "programmer"
>>60160251
educate yourself shitlord
http://duckbrand.com/about
Linux is a clusterfuck of patches and shitty hacks throwed together with zero fucks for quality control.
OP will make a great Linux system programmer, you should start contributing to projects like systemd right away!
>>60159318sin (x) = x
>>60160278
Do you call tissues "kleenexes"?
Do you call cotton swabs "q-tips"?
>mfw you probably do and everyone around you thinks you're a clown
>>60159246
>have issue with code
>not able to solve problem after hours of debugging
>pop a question at stackoverflow
>turns out to be a bug in language / compiler / OS