Re:The Worst Programming Environment in the World?
by aaronbrethorst on Sunday September 01, 2013 @07:19PM
(#6312616)
That same company refused to even consider me for a job after I graduated from the University of Minnesota because they thought my GPA was too low. So instead, I ended up in Seattle at Microsoft where I managed a good chunk of the Visual Studio IDE.
It wasn't until years later that I realized I'd totally dodged a bullet.
Re:The Worst Programming Environment in the World?
by saryant on Monday September 02, 2013 @01:42AM
(#6313602)
I once got an email from them rejecting me for a job there.
I had never applied...
Re:The Worst Programming Environment in the World?
by aaronbrethorst on Monday September 02, 2013 @02:56AM
(#6313788)
You might even say that's...Epic.
Or not. I'd recommend not.
Re:The Worst Programming Environment in the World?
by chris_wot on Monday September 02, 2013 @07:38AM
(#6314641)
Ah, thanks! You filled in the final piece of the puzzle.
Re:The Worst Programming Environment in the World?
by gngeal on Monday September 02, 2013 @03:01PM
(#6316563)
variables aren't declared; when you use a name, the interpreter just travels up the call stack looking for somewhere that variable is defined.
You could have just said "the variables are dynamically scoped" and be done with it. :-)
Re:The Worst Programming Environment in the World?
by sillysaurus2 on Sunday September 01, 2013 @05:57PM
(#6312335)
I never understood h1b slave labor. I had personal experience seeing just how hard corporations will work foreigners, and casually fire them if they daren't.
in the beginning, in the 70s or so, ram was very tight and the source was interpreted, not compiled; variable names were shortened to save memory. So the oldest core routines have single letter variable names
variables aren't declared; when you use a name, the interpreter just travels up the call stack looking for somewhere that variable is defined. so if you accidentally use the wrong name, especially with the strong bias to very short variable names, in nested enough code you will find that variable. This led to some amazing bugs
the prefix of the command to delete a node in the internal db (really just global sparse arrays) deleted everything. A coworker fat fingered that in a customer's prod systems and took down a hospital chain you've heard of. I just heard him wail, "Oh SHIT" and sprint out of our office; I later found out he ran for the recovery team.
they also had 15mm lines of vb6
oh, and they love h1b slave labor. Bring them over, abuse them, threaten to fire them if they don't work their asses off, and leave them with no transferable job skills. I presume the ceo uses her billions to salve her conscience.