This a rant, written at midnight, after battling software errors. Set your profanity filters accordingly.
I despair over the state of software engineering - specifically, stability. We seem to have lost the understanding that computers are there to do the hard work for us. And I don't think we ever believed in a user-centred approach to developer tools.
The last time I developed an Android app all by myself was… fuck… Doughnut? Kitkat? Too long ago. Last week, I found a small open source Android app that I wanted to alter. Nothing drastic, just changing a few strings and a couple of images.
The repo was 3 years old. Surely it wouldn't be that hard to get running again? Ha!
Here's what went well.
- Installing Android Studio. I remember when this was a chore - but I just installed the Flatpak, opened it, and let it update.
- Cloning the repo. Again, simple.
- Importing the project. Couple of clicks. Done.
Then it all went to hell.
Gradle sync failed: Could not find com.afollestad:bridge:3.2.5.
That's annoying. One of the libraries the app wanted to import was lost. Where was it?
It appears to be in MVN Repository with a note that:
this artifact it located at Spring Plugins repository (https://repo.spring.io/plugins-release/)
Things move. I get that. But why isn't there some form of automatic forwarding in place?
I fixed the issue and moved on.
But, as a new(ish) developer - how do I understand the complicated relationship between an app, the tools, the repositories, and all their weirdness? Where's the user-centred design in all this?
Google's Android Studio is complicated. And it puts all the effort on the user. It kept complaining that targets were too low, and needed to be updated. It didn't actually offer to update anything itself. It didn't tell me where the error was. It didn't say "hey, we can automatically update some things. Here are the risks. Want to proceed?"
It just left me in limbo.
So I found the strings and manually changed 5 numbers.
Why don't our tools do the hard work for us? An IDE isn't a screwdriver - it has knowledge about what it is doing and what problems it is encountering. It doesn't need to make changes unilaterally, but it could at least make helpful suggestions.
It reminds me of one of my earliest frustrations when I first started to learn C++ back in the 1990s. The compiler would say "Missing semicolon on line 427." To which I'd reply "If you know what is missing, and you know where it is missing, why not add it back yourself? You useless piece of crap!"
Moving on. Deep breaths. Gradle started complaining that I couldn't use "compile" any more. Apparently it was deprecated. OK. So what's the fix? Again, neither Gradle nor Android Studio would tell me. They knew there was a problem, they probably knew what would get it working. But they stayed silent. Because fuck the users, amirite!?
The fix was simple. I manually replaced the word "compile" with the word "implementation".
I did that a dozen times and it worked. What's the difference between the two? I don't know. I don't particularly care. I'm sure there was a very good reason for replacing one word with another. I'm sure it makes a profound difference to someone. But for me, the end result was the same. The app now compiled.
Imagine a user interface which suddenly said "you must turn things clockwise from now on!" You'd be all like "WTF? What's wrong with anticlockwise? That's the way I've done it for years." And they'd be all like "Dude! Clockwise is the way to go. It all has to change." And you'd go "Mate, can't you just install them backwards or something so I don't have to change my behaviour to accommodate your needs?" And then they'd spit at you.
Why doesn't Android Studio / Gradle / Whatever just go "Mate - you've used
compile here - that won't work. Want me to automatically update the syntax? It'll probably be fine."
Don't make me think. And don't make me waste my time fixing problems that you have caused.
Forums are full of people going "I can't get this project to work - Gradle is throwing weird error messages. Help me. I don't understand. Please - help!"
Gradle does not do any user research. It never sits down with independent developers, newbies, or seasoned pros. It never tests its error messages. It doesn't do developer relations. It doesn't spot bad implementations in the wild and offer helpful suggestion. It doesn't relentlessly focus on making things easier for users.
Gradle focusses on large organisations and caters almost exclusively to their needs. That's fair enough. It's their business and they can run it how they like.
The same is broadly true of Android. Its development tools are focussed on large teams of highly trained software engineers, who all intimately understand every esoteric aspect of App development.
It's great if you're a salaried employee with a large support structure. But for small and amateur developers, it's a nightmare.
I've lost count of the number of projects I've seen which start by saying "Simply install Flargnle in the normal way..." Oh, great, another technology that I need to learn in order to make a cool widget.
I've used this project as an example. And I am being deeply unfair to Gradle, Maven, Android, and everyone else. I'm tired and frustrated.
The job of a computer is to do the hard and boring work for us.