Kids today will never know the joy of writing apps for Blackberry. You wrote them in Java, which was cool and the gang, but when you tried to compile your app and deploy it to your test device, every library module you incorporated into your app had to be signed independently by RIM's signing servers. If you were lucky this took a few minutes; if you were unlucky it took 45 minutes to an hour. If you were really really lucky it never happened at all because one or more of these signing servers were completely down, and then you could just tell your manager that the signing server was down and go home for the day.
And this would happen even if you'd only changed a single line of code. I got in the habit of making an enormous number of changes before running and testing anything, which is obviously not an ideal practice but was completely necessary in this case. I would also sometimes roll my own code to avoid having to include a particular module. My custom UI, for example, needed to use trigonometry functions but these were part of one of the cryptography library modules which were especially notorious for taking forever to sign. So I wrote my own sin() function instead.
This was probably the main reason Blackberrys were murdered by iPhones, even more than their tiny screens with 16-bit color that RIM refused to upgrade until it was too late. iPhone app development also sucked thanks to its antiquated C-style language, but it was still lightyears beyond Blackberry. RIM was going around offering cash bonuses to developers to write apps for them (my company was offered $30,000 by them) but it still wasn't even close to being worth it.