If things can go wrong, they will, as my accidental merge and commit just proved.
To save me from having to Google again, here’s a direct link to the solution:
http://stackoverflow.com/questions/1338728/how-to-delete-a-git-commit
If things can go wrong, they will, as my accidental merge and commit just proved.
To save me from having to Google again, here’s a direct link to the solution:
http://stackoverflow.com/questions/1338728/how-to-delete-a-git-commit
http://www.fourhourworkweek.com/blog/2009/05/19/vanity-metrics-vs-actionable-metrics/
http://venturehacks.com/articles/lean-startup
http://successfulsoftware.net/2009/04/23/the-truth-about-conversion-ratios-for-software/
http://gigaom.com/collaboration/5-ways-to-keep-your-rockstar-employees-happy/
Decent ideas but still misses some very important points such as:
Here’s the instructions: http://my.opera.com/community/blog/2008/04/03/opera-mini-on-your-pc
Here’s where to download Opera Mini JAD+JAR: http://www.opera.com/mobile/download/versions/
Today was finally time to look into implementing the mobile version of one of our web apps. I had an idea of what the best practices are for supporting mobile and desktop web users. The theory is quite simple and I had accepted that I’d have to implement it in code.
Luckily, I somehow discovered the existence of Spring Mobile. It’s documentation at http://static.springsource.org/spring-mobile/docs/1.0.x/reference/html/device.html explains the best practices for mobile web very well. I use Spring, so naturally I went on to integrate Spring Mobile into my project.
At some point in the app, there needs to be a switch that decides whether to serve a simple JSP for mobile or a more complicated counterpart for desktop web. I decided that having the switch in Spring’s ViewResolver would present the least amount of work – the M and C parts in MVC would remain completely untouched. The biggest challenge is the fact that the web request is not available to ViewResolvers.
A bit of Googling unearthed this gem: http://stackoverflow.com/questions/1868732/spring-mvc-resolving-the-view-based-on-user-agent
Build automation (continuous integration) for mobile apps isn’t as mature as the “enterprise” world but it’s slowly getting there.
Recently we’ve had a need to automate the build of a reasonably complex BlackBerry app (with preprocessors, optional modules etc) because manual work had been error-prone and painful. We thought that implementing build automation for a BlackBerry app was going to be hard but it turned out easier than expected.
Below are the key pointers:
Collection of links and reading materials posted/shared by JFDI Asia
JFDI Asia (http://jfdi.asia) is an incubator programme in Singapore. Their first batch is being coached right now and every now JFDI Asia shares some useful tips for the benefit of other startups who didn’t get in. Unfortunately it’s all over the places.
This blog post collects links shared by JFDI Asia that I find most useful.
http://rtfm.jfdi.asia/100-days-of-reading/
http://www.entrepreneur.com/article/219666