The answer was apparently pilchard. I thought it'd be pollack, but I was wrong.
(Strictly speaking the fish types are iwashi (Sardinops melanostictus, the pilchard or pilchard sardines) and tara (gadid, or fish of the Gadidae family, incl. haddock, cod, whiting and pollack).)
And a rather curious poll today:
What do you suppose scares programmers? • Infinite loops • Spaghetti code • Someone else's execution code encroaching on their own coding region • Abrupt spec changes • There's code here I don't remember assembling! And it's bug-free!
Gah! said: This is why "goto" is forever forbidden between programmers...
Also, Butt♥
There was a time when the equivalent of a GOTO was the only way to implement a loop or react to the equivalent of an IF. There's nothing inherently wrong with it; it's just incredibly easy to misuse.
As for what scares me as a programmer, that would be abrupt spec changes.
BadRoad said: There was a time when the equivalent of a GOTO was the only way to implement a loop or react to the equivalent of an IF. There's nothing inherently wrong with it; it's just incredibly easy to misuse.
As for what scares me as a programmer, that would be abrupt spec changes.
Yes! Especially when they come the day before the deadline.
It's not "There was a time", it still exists. There will always be an unconditional jump. There will always be assembly language underneath whatever high-level language is popular at the time.
What REALLY irritates programmers are other "programmers" who read only the title of a famous paper and then interpret it as a direct edict from God himself, with absolutely no knowledge or understanding of the author's actual meaning or intent.
Suzuran_Majere said: It's not "There was a time", it still exists. There will always be an unconditional jump. There will always be assembly language underneath whatever high-level language is popular at the time.
What REALLY irritates programmers are other "programmers" who read only the title of a famous paper and then interpret it as a direct edict from God himself, with absolutely no knowledge or understanding of the author's actual meaning or intent.
GOTO is just too easily abused by kids who don't really know what they're doing, and it kind of impedes code readability.
Ryvian said: Spaghetti Code. Guilty of doing it myself actually. Shit can get pretty weird once you hit multithreading.
You will love this quote from the ZeroMQ guide: `` If you've spent years learning tricks to make your MT code work at all, let alone rapidly, with locks and semaphores and critical sections, you will be disgusted when you realize it was all for nothing. If there's one lesson we've learned from 30+ years of concurrent programming it is: just don't share state. It's like two drunkards trying to share a beer. It doesn't matter if they're good buddies. Sooner or later they're going to get into a fight. And the more drunkards you add to the pavement, the more they fight each other over the beer. The tragic majority of MT applications look like drunken bar fights. ''
Moonspeaker said: (Strictly speaking the fish types are iwashi (Sardinops melanostictus, the pilchard or pilchard sardines) and tara (gadid, or fish of the Gadidae family, incl. haddock, cod, whiting and pollack).)
And a rather curious poll today:
Oh god if I ever saw correct code I didn't make I'd be shitting my pants and calling an priest. Apart from that, I'd say it's spec changes. Infinite loops are just yet another kind of bug, any encroaching programmers can be dealt with via a punch to the face and spaghetti code is a pain but a reality you (sadly) get used to. OTOH, spec changes might mean you'll have to scrap entire swaths of code.
Someone else's execution code encroaching on their own coding region
means...
Like artists, programmers develop their own "style" of writing code. There's no universal template that programmers adhere to. And even the best programmers can get confused when their own coded programs start resembling something else. Hence -
There's code here I don't remember assembling! And it's bug-free!
My fear would have to be abrupt spec changes.
Whenever that happens, I'd have to scrap the current work and start over. So actually, not much fear and more like rage-inducing.
• Someone else's execution code encroaching on their own coding region
This would have to be my worst fear, especially if everything about how their code is written differs from mine. I dread when someone who uses the underline system and an over-complicated error-catching system starts to encourage onto my own code. Then I have to spend hours trying to understand what they did.
Ofc thats still much better than those who completely change my code and end with a segfault.
TMOAGTIEB said: This would have to be my worst fear, especially if everything about how their code is written differs from mine. I dread when someone who uses the underline system and an over-complicated error-catching system starts to encourage onto my own code. Then I have to spend hours trying to understand what they did.
Ofc thats still much better than those who completely change my code and end with a segfault.
Hahaha I remember my first 5+ man programming project. That was disastrous. I especially hate it when their error catch don't do anything important, and rather are purely added because it was included within the scope of the course.
This nerimono tastes amazing, doesn't it. Nerimono: Boiled fish-paste productWaitress?Huh?!Hold on, I'll go ask!I just asked......and you know what the ingredient was?JumpWhat was it again?I'll go ask again!This infinite loop is scary, right?
One of 2ch's meme-like texts.
Butt♥
What kind of surimi is it made of? Surimi: Minced fish that's mashed into paste.
