Another startup culture bash was making the rounds, this time about a common term in the startup world – “getting shit done”, and what a terrible mentality it is to have. Disclaimer – I know the author personally, as him and I were at the same 500startups batch this summer, and I also consider him a good friend. But I think he’s completely off on this one.
Last week, my co-founder, Adam, and I, traveled to Japan. The official reason was being invited to the b-dash camp conference in Osaka by our Japanese investor, Tak Miyata of Scrum Ventures, and we piggy-backed on the opportunity to visit a country we both wanted to go to for a long time.
My history with Japan
I’ve been a fan of Japanese culture and entertainment for quite some time now. I really like the Japanese themed online slots and roulette, back home I am always playing to my hearts content. Japanese society has a lot of rules and preconceived notions, but once they break through that, they have no limit on their imagination.
Continue reading Travelogue: Japan
First, a prelude – though I’ve mostly written technical articles on this blog, it’s called techfounder for a reason – it was my original intention to also talk about startups from the view-point of the technical founder. I have been involved in several ventures so far in this role ( websites like Acquirent.com), each giving me more perspective on the overall picture.
I’ve just stumbled upon a nice article titled “Why you can(‘t) recruit a technical co-founder“. The author makes some solid points about why it’s hard to recruit / find a technical co-founder for a startup, but it seemed more common sense than deep introspection.
Idea is nothing, execution is everything
If you’ve started up your own venture, you know this saying is not just a cliche. Ideas, however great, will get nowhere without execution. On the other hand, solid and above execution can get very far with even below mediocre ideas.
Continue reading Finding co-founders – Technical founder POV
Some casual surfing led me to this article from a couple of years ago, titled “How to recognize a good programmer”. It was a nice read, but as many in the comments pointed out, the criteria the author set forth most likely describe himself and are not really useful as rules-of-thumb on how to recognize a good programmer.
It got me thinking though, on what are the attributes I consider useful in fellow programmers. So what makes a good programmer?
Continue reading What makes a good programmer?
Preface: This article was written mostly half a year ago, as I was wrapping up an intense period of freelancing and sub-contracting. It is less relevant for me now, as I’m now an equal partner in a small web firm and my freelancing days are beyond me – however, I thought it might be a good read.