Oct 21

I've slacked a lot on keeping this up. Various sources claim that it's important, psychologically, to journal what you do every day.

It's possible that where I am right now is a side-effect of the slacking. It's also possible that there's just a lot of frustrating shit going on right now. I want something that I can break. I'm frustrated with absolutely everything.

Google's shitty documentation for Android is annoying as fuck. The number of APIs that fail silently makes me want to strangle multiple people (I'm looking at you, Service interface, and you Intent, and you Alarms)

Lots of bugs and stupid problems. Progress is painfully slow.

I'm also fed up with the conceit that an Android application isn't really a program that starts or stops. Everything fucking stops. Assuming that your app is going to run forever and that you don't _need_ a way to tell when it stops it bullshit.

It turns out that there are (at least) two distinct types of Activities: the initial Activity that starts your application, and every other Activity. The difference is that the onDestory() is NEVER called on the initial Activity, but is reliably called on other Activitys. So ... hey guys, maybe this is a big indicator that you're trying to make the Activity class do a bunch of shit it shouldn't do. Honestly, if you have a method that is NEVER called, why is it there?

Seems like you should always have a shell Activity whose entire job is to start another Activity so that you then have a place to reliably handle onDestroy().

What a shitty day. I really despise days when everything seems like a gigantic chore.

Oct 6

There's a psychological thing, where you're pretty much done preparing, you don't know what else to do, but there isn't any feedback yet for you to know if your work is going to pay off.  It might be the most miserable state of mind to be in.

Lot of trouble the last few days, I think I seriously burnt myself out.  In general, I don't know what the hell I'm working toward any more.

Really angry at the code today, but making slow progress.  Some basic screens in place and some of the basic flow.

Oct 4

Holy *^*@^#!:

https://support.google.com/googleplay/android-developer/answer/141659

I guess I wouldn't be so damn frustrated with this if it actually gave me a useful error instead of just saying "failed, please try again"

To Google and anyone else developing software: if your error message says "please try again" when it's clear from the software's logic that it's NEVER going to work, you are a bad person and deserve whatever terrible fate befalls you.

Also, if you link to a page that's supposed to resolve an issue and it DOESN'T, that also makes you a bad person worthy of having bad things happen.  The above tells you that you can't buy your own apps, points to a page that's supposed to tell you how to work around that, but the target page doesn't explain that.

Oct 1

I swear, today I'm going to drive myself like a crazy boss and get some stuff done for really reals.

I've run out of whiteboards again.

I have a lot of trouble enjoying layout activities ... like making a website or figuring out a UI.  Very tedious to me.  Although ... I'm fairly happy with the resultant website.