tdr

16 ms·

61.
by tdr 14y ago
Timeless advice for any software engineer! The one thing to add (related to 1 and 3) is: *do not focus completely on the technology. learn what's around it also*. I once worked for a company where 1 week/month the managers would
62.
by tdr 14y ago
I would argue that the trend is that gaming is moving away from complex gameplay rather than away from desktop . What we see is less complex titles released every year both on PC and console. The reason is probably because development co
63.
by tdr 14y ago
Cool way of delivering the value. Appreciate the work! RSS feed: http://gdata.youtube.com/feeds/base/users/TheGameStartup/upl... UPDATE: I don't know why, but whenever I see other people in my situation, sharing their experience, it a gre
64.
by tdr 14y ago
Lack of gaming support was (and still is) in my opinion the main reason Linux didn't get properly accepted into the consumer sector. (every gamer had to keep Windows dual-boot ) Because of that there were problems with the drivers and snowb
65.
by tdr 14y ago
Yeah, that one of the "solutions" to the "information overload/exhaustion" problem we're solving. Thing is the "read it later" approach doesn't really solves your main problem (getting the facts fast).
66.
by tdr 14y ago
Well, web startups don't work that way. The workflow is: listens for news-highlighting requests gets each and every webpage/feed detects the main content processes the content and pinpoints the relevant sentences from e
67.
Show HN: Summarize webpages in seconds (inside the browser)(keenskim.com)
3 points by tdr 14y ago|5 comments
68.
by tdr 14y ago
I'm Tudor from Romania (see article) Being an "physically-outsider" to the US/SV environment, I must say that Ohours was and still is a great tool for getting my startup closer to the States. Although I read a lot of news, actually talking
69.
by tdr 15y ago
I agree with the point, although it's a little "all over the place". I'm taking it as a "beware sign" for knowing what's ahead; i.e. to consider the big-picture around whatever you are building (it's very easy to get sucked into some "inter
70.
by tdr 15y ago
What a great reference! Having already started a company, I can say this is true and wish this list I'd had it before. BUT, the majority of these "commandments" I already knew. The important point missing here is that until you do it on you
71.
by tdr 15y ago
Fantastic! Been looking for something like this. Could you also put the timezone (both GMT and other name) besides the city name? (as subscript & subscript, one over the orther) [ex: San Francisco (PDT/GMT-x)]
72.
by tdr 15y ago
+1 to confirm the bureaucracy around governmental/European funding: I lost 6 months on preparations for them and finally quit. If I would have continued (and be accepted) I would have lost another 3-12 months until signing the contract. Aft
73.
by tdr 15y ago
http://news.ycombinator.com/item?id=3655582 is a great post featured today. It's mainly focusing on depression but I think this is useful to any period of "tough luck" (technical issues included). The best parts are the solution(s) and in
74.
by tdr 15y ago
One of the key advantages of being a software developer is that you will end up learning business (if you work in companies). That's because developers are smart people and they are working on solving people's (business) problems. Also, bus
75.
by tdr 15y ago
This is a sad post, taking it's from an entrepreneur. You sure don't want to be in the pessimistic/negative mindset. Finding right people for customer interviews is hard If one can't find them, how can one validate the idea, tweak it and
76.
by tdr 15y ago
Following you suggestion, I found http://answers.onstartups.com/questions/329/uservoice-or-get... Thanks
77.
by tdr 15y ago
I'd like to use the best tool for the most important aspect. Also, I prefer to use a solution built by a specialist and passionate team in that specific are. The message board is great, probably that's the most important channel for feedba
78.
Ask HN: tools for Customer Feedback
9 points by tdr 15y ago|7 comments
79.
by tdr 15y ago
http://betakit.com/feed
80.
by tdr 15y ago
Also really good advice: A year into my first startup, my first major product epiphany was to never, never, ever try to build a product you couldn’t be a user for You have to have the vision, understand everything around it. Relying only
81.
Know any good list/reference of (potential) startup risks?
2 points by tdr 15y ago|1 comments