Over the last few months I’ve been sleeping quite less than recommended, and this is the reason…
We’ve revamped most of the app to make it cuter, neater and more usable. So, next time you need to catch a bus in Bilbao, don’t hesitate and download BilbaoBus.
The Clean Coder
By Robert C. Martin
The Clean Coder is a kind of sequel to the famous Clean Code published in 2008. This sequel is a 200-pages-self-help book for programmers that’s sprinkled with biographical material. By and large, the mantra is: read this book and you’ll learn how to be a true professional programmer. To achieve that goal, the author shows a kind of ethic code for “true” developers in a world of sloppy programmers. The most remarkable aspect of the book is that is rather focused on psychology than in practical or technical stuff. Therefore, there are whole chapters dedicated to topics such as: when/how to say No to pushy managers, coding mental-state, etc.
I do support the idea of acting always as a professional no matter if you’re an entrepeneur, an employee working for a large company or a freelancer. One should have always in mind that every mistake we make has consequences and there’s no free lunch. However, I find the approach of this book is a little unreal, the programmer is presented as a kind of medieval knight or so.
To sum up, there are highs and lows in this book. While I enjoyed some chapters like “how to say no” or “how to estimate”, others are pretty much useless, like “Coding”, “Mentoring, Apprenticeship, and Craftsmanship” or the one about teams and projects which, to my surprise, is 4 pages long (!?). The reading is agile and even enjoyable but don’t expect to much and it won’t disappoint you. Usually I’m not very keen on this sort of books, but every now and then, I read one because we all have something to learn or get better at.
This is recent interview with Robert C. Martin:
The website Gamasutra frequently publishes articles where game creators talk about the development process of a game. These papers are called Postmortem because they are written once the game’s been finished/released and that’s precisely what it makes them so so valuable. They are no just about “how brilliant we are”, on the contrary, Postmortems usually focus on mistakes and lessons learned.
Although most of them may be considered a must-read, I’ve found particularly interesting the one about Riptide GP where the guys of Vector Unit describe the process of porting a 360 xBox game (Hydro Thunder Hurricane) to the Tegra 2 platform. Hot topics such as funding, monetization and piracy are also addressed in the write-up . Definitely a good read!
Postmortem: Vector Unit’s Riptide GP
Published August 31, 2011
Android , Archer Master , Business , Java , Quoders , Technology
Tags: Android, Archer Master, Java, MAT, Memory Leaks, Quoders
Recently while I was working on the next version of Archer Master, I’ve had to roll up my sleeves and find a memory leak. By and large, a memory leak in one’s application is frequently a synonym for having painful time, no matter which language you’re coding in. I have experience in finding leaks in the non-managed languages such as C/C++ but this was my very first time with a managed language (Java). In my case, the leak was caused by a lost strong-reference to a LinearLayout used to hold advertising, so each time a level was played, the entire activity remained in memory and wasn’t collected. As a result, after playing several levels (the number depended upon the particular device), a OOM exception raised and the game crashed.
It’d have been virtually impossible to find the leak without a tool like MAT. Moreover, a good understanding of the different types of references (strong, weak, soft…) and the concept of Dominator Tree also help.
When I’ve got a little more time I’ll write about the whole process I went thru (if anyone is really interested please let me know)… but meanwhile, this is an invaluable resource if you find yourself in a similar situation and don’t know how to start:
Good luck with your leaks!
I’ve published the weekly Archer Master report on Quoders website. The following chart shows downloads per day:
It’s been a long time since my last post and this time there’s a good reason for it I’ve been working hard to release the first version of Archer Master, an archery game for Android. Archer Master is free, so give it a try!
Moreover, I’ve co-founded a new development studio named Quoders.
Hopefully, this is the beginning of something great…
Due to the fact that I’m currently engadged in an Android project, seemed to me worthwhile to take a look at how other people are making money out there. I’ve found quite useful this presentation that shows a real business case of a mobile application for IPhone. So, no matter what your target market is, there’s always a lesson to learn when it comes to mobile app business.
It’s been six weeks waiting for the Nexus One and finally it’s here. The N1 runs smoothly and fast a Cyanogen ROM. Even though I’m using the same 3G connection (vodafone ES), now browsing the web is a delightful experience compared with HTC Magic. The battery lasts almost a couple of days with a normal use (email, web, rss, etc).
The parcel didn’t include any sort of manual except a couple of sheets with tips and tricks.
Here you can see more pictures.
It’s been announced the second part of the course “Developing Android Apps with Java” by O’Reilly. It will start in May 18th and it’s going to consist of six sessions in which a Twitter client app for Android will be developed. Interested? You can register for free at the course home page. No excuses to learn Android Programming
I wrote a review of the first part of the course in this post.
Published April 12, 2010
Android , Books , Technology
Tags: Android, Book, Hello, Review
By Ed Burnette
Regarding books, one of the things I appreciate the most is an honest relationship between title and contents. Unfortunately it’s quite common to find books out there promising things they don’t fullfill.
“Hello, Android” meets perfectly the commitment of its title. Don’t buy it expecting a reference manual of Android because it’ just an introduction to this platform, and I must admit that it does the work gracefully. It’s quick and brief so it tells you the essential and gives you resources for further research such as the sample projects that can be free downloaded from the book website. A nice aspect to highlight is the hands-on approach, throughout the book concepts are illustrated with lots of code. Furthermore a Sudoku game is parcially developed during a couple of chapters.
So I basically recommend this book for beginners mainly for two reasons:
- Starts from the Scratch: Nothing is assumed so it’s a good point to start out as Android developer.
- Brevity: I don’t have time for an eight-hundred-pages book to start to develop. I’ll deal with the ins and outs as I go, not before.
Of course, like any book about Android, Java (or C++, C#, etc) basic understanding is recommended.