Developing an Android project. Teammate is a programming genius. He just writes code I simply can't understand with the level I have. And modifies the project and the IDE without notice making it even more confusing a language that's already confusing to me! Code is unnecessary complex and on top of that, Buggy! Frustrating Experience!

But I won't give up. As soon as we beta-test that monster-of-a-game I'm leaving the project. Will start working on my idea, on my preffered language at my own pace. There will be no other who to blame rather than myself!

Lucky you, hardcore programming buddies are hard to find That sounds like a really huge project too

In some sense, yes. I'm eons ago from what this guys knows. Sad part is he writes without comments and I have to catch up with his code. Most of times I end up understanding up to nothing... that level I wrote was almost a miracle and it was strongly based on what he did for his level...

Wait - does he program and you beta-test? And if you both program, how is that gonna work?

Well, he programs. I just try to follow his pace. We've a meeting with them beta-testers this friday. And that's where our association ends. I've become almost a deadweight for the guy.

So did you "hang on" to him, or did you please him to do it?

We decided to work on Unity first. Interface was intuitive to me, but my partner wanted greater control over the code. After a month working on Unity by myself (partner DID hang on), partner decided we should Switch to Android Studio and right then he started typing all this code I've been struggling to read.

He says it's quite easy so he writes no comments on it's code, making it kinda diffcult for me to read it. As a first impression I though it'd be easy to write on Android Studio, but having near no help (au contraire!) from partner and little interes on the project, all I really want is to deliver the beta and ran away from the project.

*run* away

Oookaaaay! just discovered he just deleted his displayDialog function. Now he wrote a NEW function named viewTransition whose functioning I'm about to discover...

Decided on a solution as drastic as his: I'm rewriting the code of my level from zero and without using his fancy inherited classes. Will use my own classes and control everything with just click listeners to switch images instead of his animatedAlphaDegradatingTransitionBetweenImages extends GameActivity()

Halfway up there!

Haha now that is one long class name xD

It is! Or was. Guess it was renamed transitionImage or the like.

Sounds cool, watcha buildin?

Took this Videogame Desing 101 course this last mid-term. Final project was an edutaiment app that gamificates a tool to help elementary kids with reading issues. Most things we're doing are static images, typewritter-style flavor texts and clickables to present a quiz.

We'll show this app to beta-testers today, 16hrs.

Personally, I think gamification sucks and edutaiment, if sometimes educational, rarely entertaining.

We did some funny things, though. Mostly clones of existing games: Pong, Asteroids, Marble-on-a-3D-maze thingy, A Super Mario level, a First-Person-Walker...

...and this quiz, game-like App.

We used several game engines for each game: Processing, Love, Phaser, Unity, Stencyl and... Android Studio (which is not precisely game-oriented)

Lesson learned: Android Studo is NOT for beginners.

Good thing is i'm having a first dip on Android. Guess next time it won't that hard for me to do some Android antics...

Wheew! Rough day today! At the very end, partner was very supportive, and I managed to grasp a trick or two. Beta testers destroyed the game and others kinda liked it. Went well, all in all.