[coding] Fucking Programmers

At work:

Intro:  one of the devs--my only dev--seems to have improved considerably during my absense.

Foreshadowing:  seems to

So, he copy and pasted one of my unit tests, and then he uses a FIVE MINUTE THREAD SLEEP in his fucking test.  Who the fuck thinks that's acceptable?  That's worse than a broken test.  When a test is broken, you look at the error message and figure out why.  When a test thread sleeps for a whole 5 fucking minutes, you start to wonder if the ADB bridge went down, or maybe Eclipse put itself in a deadlock, or maybe your fucking phone crashed.  Who knows?  You don't, because you're just sitting there reading reddit with the frozen junit test in the corner of your eye.  The entire test run takes--or should take--less than 5 minutes.

And the most annoying thing is, it doesnt have to be 5 minutes.  I've already written the configuration override gear that lets you change the timing values in the unit tests.  In fact, the lines that change similar config values were part of the shit he copy & pasted from the test that I wrote.

Five fucking minutes.

At the Startup:

The contractor I asked to integrate dropbox functionality has managed to find some kind of mysterious Android SDK that does not appear anywhere on the fucking dropbox website.  I don't even--wait, I just figured it out.  Man that just goes to show:  if you want to solve a mystery, start bitching about it on blogger.

Anyway.  Dropbox thought it would be fun to have one API on their website, complete with documentation, and then another, completely different API, in the .zip file that you download when you download the SDK.  I'm not even kidding.  There isn't a single class file here that matches anything on the website documentation.

Normally, when I write java code, I use a special javadoc website called google, where I just type something like "java InputStream" into the magic box and the javadoc is the first thing that pops up in the search results.  Unfortunately, "java AndroidAuthSession" does not return anything useful.    I'm going to have to actually manually navigate this javadoc folder in order to find the documentation I need.  What am I, Amish?


Conclusions

My accomplishments for the day include fixing the unit tests that someone else broke for the second day in a row, and also finding a javadoc hidden in the bowels of a zip file.