☀️ 💣Nonsense haikus generated using unicode emoji description text.
BLACK SUN WITH RAYS BOMB
FAMILY: MAN, MAN, BOY TURKEY
CLOUD WITH SNOW TRACKBALL
I gave a talk at #OMRS15 on MSF’s efforts to make Project Buendia easy to customize and deploy, with a focus on nutrition programs. These are the slides (pdf, 4.5 MB). Speaker notes also available (pdf, < 1 MB).
I’ve been working on Android apps at Google for about two years. In that time I’ve worked on a diverse set of codebases - from small, tightly-contained internal tools that only target Lollipop and newer, to extremely complicated apps with large development teams, such as Google Maps, and even system-level code such as the Activity Manager for Android Auto. In that time, I’ve also seen a lot of new team members come up to speed, and found myself consistently giving the same advice to help them get there quickly. Here’s my top three tips for becoming productive whilst developing for Android.
Applicationclass as a container for application-wide resources, which can contribute to memory pressure on your users' devices, and can make code difficult to maintain. This article explains the issues in detail, and recommends One Weird Trick™ for more memory-efficient, more maintainable, app-level resources.
So today Bill Shorten, Australian opposition leader, came to work to chat about Computer Science / Engineering education, and I gave him a demo of Android Auto. Feat. me in an upside-down Google t-shirt.
I was in London for the last month working on an Ebola Crisis Response project. It’s a collaboration between MSF, Google, and a bunch of volunteers from the community.
Steph and I went to Iran with a friend who was going back to visit her family.
I wrote and gesticulated wildly in a video talk for Google I/O this year on how Android Auto works. It’s pretty high level, but it covers the key aspects of the architecture.
Information Technology - it’s an awfully un-glamourous pair of words. When people think of IT, they think of business applications that don’t really work as well you’d expect them to, database administration, and ugly-looking spreadsheet-y things on badly designed websites.
My undergraduate thesis has two main outcomes. I’m not going to bore you with the details here - if you’re really interested, you can read my thesis comic here - but I had a couple of thoughts about two different kinds of products/goals/outcomes that I’ll be working on.
A couple of months ago, I did a presentation on “re-humanising people through design” for a job interview. It’s an idea I got partially from the work of Bret Victor and a lot from the first issue of The Manual.
I finished off an app for the Windows Phone 7 Marketplace this week, it’s called Timecard. You can find a link to it here, and, aside from some slight icon colouring issues, I’m pretty happy with it! Anyway, I just figured I should write a few notes about how I put it together and some of the design decisions I made, and I’d love to hear what you think in the comments section below if you’ve got any thoughts.
In the last instalment, we took a bit of a look at troubleshooting I2C connections between Arduino microcontrollers and peripherals.
Well, I’m doing a project at Uni at the moment in a team of eight. Don’t get me started about the coordination nightmare!
When it comes to understanding my relationship with Jesus, I feel a great need to put myself into someone else’s shoes. I’m not really sure why, and I suppose lately I haven’t really been sure how.