From the river to the C

My favorite:

for (int i = myArray.Length; i --> 0; )
{
    //do something
}

Perfectly valid in C-style, even if it does look a bit puzzling at first.

I started coding professionally using Visual Basic (3!). Everybody made fun of VB’s On Error Resume Next “solution” to error handling, which basically said if something goes wrong just move on to the next line of code. But apparently nobody knew about On Error Resume, which basically said if something goes wrong just execute the offending line again. This would of course manifest itself as a locked app and usually a rapidly-expanding memory footprint until the computer crashed. Basically the automated version of this meme.

BTW just to defend VB a little bit, you didn’t actually have to use On Error Resume Next, you could do On Error Goto errorHandler and then put the errorHandler label at the bottom of your routine (after an Exit Sub) and do actual structured error handling. Not that anybody in the VB world ever actually did this.

Mediocre pop star.

Visual Basic isn’t dead … it’s just resting!

I forewent (?) skin-washing instead. Now I take a shower like once every two weeks. I ask people periodically if I stink and nobody says I do, so I dunno. TBF I also forego most of my tasks and most of my unconsciousness as well.

OK, which one of the things I mentioned do you think is vastly and objectively superior to all others? Genuinely curious here.

I’ve worked professionally on Windows and Mac; using Visual Basic, C#, Java, Objective-C and Qt Creator (which is C++ and Javascript); for web apps, desktop applications, and mobile apps (iOS, Blackberry and Android). I have my personal preferences but they’re all viable platforms/languages/frameworks/devices and anything that needs doing can be done on them one way or another. The idea that one of these is vastly and objectively superior to all others is just pseudo-religious nonsense.

Windows Phone was great. I’d done Windows Mobile since 2005 and it was nice to be able to continue developing with C#/.NET and Visual Studio (back when it was still good) in a more modern OS. One thing that really spoiled me permanently was being able to compile, build and deploy the app I was working on to my test device effectively instantaneously – like, by the time I’d moved my hand over to the device, the app was already up and running. Then I switched to iOS where the same process could take minutes, also Blackberry where it might take half an hour or never happen at all.

Funny thing: RIM was going around circa 2010/2011 offering companies cash bounties of $10K to $20K to develop apps for Blackberry, since they were dying a rapid death but were still flush with cash. Nobody that I know of took them up on the offers. I tried to get my company to make a Windows Phone version of our software but I was laughed at (and deservedly so).

so you can focus on what really matters… meetings! collecting unemployment!

That would be incredibly ironic given that they completely fucking gave up on mobile devices when the iPhone came out.

It’s kind of funny how eagerly we programmers criticize “premature optimization”, when often optimization is not premature at all but truly necessary. A related problem is that programmers often have top-of-the-line gear, so code that works acceptably well on their equipment is hideously slow when running on normal people’s machines. When I was managing my team, I would encourage people to develop on out-of-date devices (or at least test their code out on them once in a while).

That’s obvious. I’m pointing out that your logic doesn’t support your opinion.

Reminds me of asking operations to help me move furniture in my office: “ya wanna move something, ya gotta move it with yer mind!”

My girlfriend once asked me how I knew she liked me when we first met. I told her it was because she would lightly touch my arm when we were talking. She said she didn’t remember doing that, and also that she didn’t actually like me when we first met.

Tales from the Crypt

It would have been cool if they’d renamed themselves “Calloway”.

run our design past a focus group before implementing it

once you’ve built something, you’re not asking users for whether it’s perfect

I once ran afoul of our UX guy for suggesting that we run our design past a focus group before implementing it. Dude literally said “users don’t know what they want”.

I had a job like that back in the day (circa 2000). I remember one stretch where for a solid month around 50 developers did nothing but call in to Who Wants To Be a Millionaire? to try to become a contestant. Ironically, one web app I wrote for them (with Visual Basic and “Classic” ASP) is still in use today – and it was a front end for a mainframe system that dated to the 1980s, which means that’s still up and running as well.