HNHacker News
TopNewBestAskShowJobs

weaponizedgames

11 karma · joined April 6, 2010

submissionscomments
weaponizedgames··on New Startup Now Pulling In Over $100k in Monthly Revenues
Kumph, congrats, but what's your plan for when Apple clones your features and look-n-feel to be included inside their own App Store app?
weaponizedgames··on Steve Jobs "never had any designs. He has not designed a single project"
Nonsense. When you are "betting" on every platform in the market, it's not betting. Try going to the track and betting on every horse in a race. You'll lose money.
weaponizedgames··on Ask HN: How does marriage affect the creation of a (successful) startup?
One problem to consider if you are working on your startup from home is the danger of constant interruptions. It can be hard on your family, especially your wife, to "not be allowed" to interrupt you. You have to remember that your family interrupts you because they care about you and they want you involved in their lives, but at the same time you have to find a way to tactfully get them to stay away from your office during your workday.

Sitting almost perfectly still in front of a computer and concentrating for hours and hours at a stretch is not a natural act. Humans are wired to get involved with the social activities going on around them. Depending on the difficulty of what you are working on, a few family interruptions per day or a too-high noise level from elsewhere in the house can destroy the quality of your work for the entire day.

Interruptions are also a big problem in a traditional office environment, but there you have much less invested in your efficiency. If management isn't willing to pay for private offices where the staff can concentrate properly -- then they get what they pay for and its not really the programmer's job to question it. At least everybody in a shared office area is in the same boat and everybody suffers from the same distractions.

In a startup, however, interruptions can ruin you and must be dealt with.

weaponizedgames··on Every Comment is an Admission of Failure. Write self-documenting code instead.
From your link, Knuth himself says:

"The practitioner of literate programming can be regarded as an essayist, whose main concern is with exposition and excellence of style. Such an author, with thesaurus in hand, chooses the names of variables carefully and explains what each variable means."

I agree with Knuth. All my blog post is saying is that, given that a program is little more than a bunch of words (symbol names), we might as well make those words be the documentation instead of cluttering up the screen with more words that we call comments.

weaponizedgames··on Every Comment is an Admission of Failure. Write self-documenting code instead.
I'd be interested in a quote or link from Knuth if you have it. Or a page number, I'll look it up.