514 karma · joined January 12, 2011
Sorry, folks, but my jeans pockets are like monkey traps. If you grab anything in there you won't be able to get your hand out. They pickpockets figured that out quickly and ran off without any loot. Tight jeans saved my vacation.
Too bad that the Android app crashes on my MyTouch 4G when "Loading Challenges". Is there any way I can help in debugging this?
Now, if the tweets do not show up in my timeline it's different of course. A company can tweet every single minute on Twitter if they reply to people and start conversations since this does not show up in everybody's timeline. See Hipmunk for a company that gets this right, for example.
I am definitely seeing lots of parallels to work and other aspects of life here.
Every time this happens, someone else solved a problem for me for a fraction of the cost that would it take me to implement. I can just pick another thing from my ideas.txt file and work on that.
This happened quite a lot recently because I want to break into Android development with a friend of mine. The first three ideas we came up with have already been done. It turned out that one of the ideas is an amazingly popular apps in the Android store already. Too bad it was not us who did it. But then, now we have finally found an Android app idea nobody has executed on yet and we will start working on it today.
I took the product over as lead developer and saw no way to save it. It helped that only maybe about 10% of the features we wanted to have were implemented, so two of us managed to do the rewrite in less than six months.
The main focus of this rewrite was indeed to make sure that we would never have to rewrite the product ever again. We kept a very close eye on identifying what went wrong, what design principles can help us to avoid doing things wrong in the future, and how to design for extensibility considering that 90% of the features still have to be added.
In the end the rewrite turned out to be very successful. Until the day I left the company (three years after) no rewrite was ever necessary again. Rather, we managed to keep up the good principles laid down during the rewrite so we could just work on the code incrementally. The product was also the commercially most successful piece of software the startup sold.
The problem was not the rewriting itself but the lack of understanding how things went wrong the first time. From my experience it is absolutely mandatory to have many deeply introspective and self-critical thought sessions to figure out how you got into the mess. Only if you have clearly identified what went wrong in the past, you will be able to successfully rewrite a project and avoid the mistakes.
For some of the products we did this and rewriting was a huge success. For some others we did not and the rewrite turned out to be just as terrible as the original version. Then we rewrote it again and it was still a mess.
The funny thing is that I have never had a bad experience with US immigration. The only time I had a non-smooth experience was in Canada, before a flight from Montreal to Atlanta. An officer waved me out of line saying "I'm sorry sir but you were selected for a random security check. You can thank Mr George W. Bush for that."
The two funniest experiences I had was when entering Dubai and Sao Paulo, In Sao Paulo the immigration officer did not speak a single word of English. I do not speak any Portuguese. We quickly realized this frustrating situation and I was waved through. In Dubai I was the first person in line at the customs and not knowing what to do I just kept walking. The customs people just stood there and looked at me. I was already quite far behind the customs people, nearly out of the airport, when I realized that I just walked past the customs officers without having my bags or anything checked. So I went the whole way back just to go through customs properly.
Thank you very much for the email you sent me too.
Here is a suggestion. Maybe you can work on improving communication with your users so they know what is being changed and added to the site. I just checked out the blog for the first time like a minute ago and only once is a new feature mentioned (the #FF feature from 19 days ago). All the other entries seem to be focused on 'we are mentioned here! and we are mentioned there!'. Since I do not even read the blog, I even missed the #ff feature.
Of all the things they showed me there, Mondrian (of which Rietveld is a fork of) impressed me the most. More so than dinosaur skeletons, space ships, 3D Google Earth terminals, or free amazing meals.
I was working in a startup at the time and we did not do code review at all. After seeing the Google workflow and having their build processes explained to me in detail, I was trying to set up code review before commits at the startup too. I hoped to improve code quality with this. Unfortunately the tools we tried were terrible and so it never took off.
To this day, not getting the necessary processes in place remains one of the biggest regrets of working there. Now I work at another place where we don't do that either. Too bad.
As such I have already given up on establishing a state-sanctioned retirement fund any time soon. Instead, I live frugally and save more than 50% of my post-tax income. Some of that is invested in funds because I can easily keep those wherever I will move to in the future.
Right now I am investing some of that in managed funds but I am not very happy with this and will probably move to index funds soon. I don't have enough confidence that my actively managed funds will beat the average market.
On the one hand, this was basically our primary marketing tool. We talked about our tools, other engineers saw them and convinced their companies to buy our software. On the other hand, our engineers were constantly in contact with people from big companies (Google, MS, ...) that tried to recruit them.
Curiously, only one of our engineers ever left the company voluntarily (that was me, after four years), so apparently the boss managed to create a work environment that was so great that even constant top-dollar recruitment attempts by other companies had no effect.
But instead of working on things that could improve his chances to get a job, he just watches TV all day long. If he put in only maybe three hours of open source coding time a day, his chances to score a job should increase tremendously. If you are an unemployed software developer, it is much easier to stay on top of things than in many other professions but in the end you have to have the motivation for it.