pm

I do remember that line - Bill Bryson is gold. The other fact I remember is that Slipknot originated there.

I had this problem at high school, and it's taken me years to undo the expectation that everything should be easy. It happened to my brother too, except if something's too challenging for him, he just quits.

If you're gung-ho enough, expose yourself to the fire so you build up resistance. It's going to be rough once you start hitting walls.

I don't come to HN looking to generate new ideas. I come to be exposed to things I might potentially be interested in, and to learn from those who might know more than me. If I generate any new ideas at all, it's outside of the time I'm engaged here (when things have time to percolate and my focus isn't so narrow).

$750-$900 daily (don't do hourly). Developer/Designer. 8 years experience. Much ado about iOS, Cocoa, etc. Bit of web and Windows. Anything that needs to be done, really.

I like much of Mark Suster's writing, but I agree with you on this point wholeheartedly. Not all companies are built the same. There are lots of unhappy people pissing their life way doing shit they don't like - I don't intend on being one of them.

When has Mark Suster said that?

You said you couldn't see how the code was more relevant, which I interpreted in another context; ultimately gamers won't care as long as it's a good game. However, I don't see any value in following that line of reasoning, as it halts all further discussion.

The truth is game code often needs to be performant first, and the pursuit of that goal usually comes at the cost of maintainability and readability (and programmers' sanity), so I think further discussion is warranted.

Game code has to be performant first, readable second.

Sure, break things when you're trying out a lot of new features. I get that, and for the user-facing side of Facebook, it makes sense. It doesn't make sense (and is extremely frustrating) when you apply the same principle to your third-party APIs.

Perhaps, but when it's applied companywide, it's a bad idea.

Move Fast (and Break Things) is the unwritten motto of every mediocre dev shop out there (breaking things being an unintended side effect of moving fast). It's not controversial.

No, OP will have to focus on one thing at a time. So it's going to take longer to begin, but sometimes these things can't be helped.

It may sound obvious, but I would (besides the customer development which has already been mentioned), begin looking for a job at a place which gives you more latitude. There are some companies who get it, and some companies who don't.

I'm in no hurry, and I'm sure most people would agree that they'd rather see a database improve stability than branch out too fast to new platforms. Keep up the good work!

I'm using Realm on iOS at the moment for a reasonably large application. I originally had a C cross-platform core based on SQLite, but I found it too difficult to maintain and threw most of it out after attempting to make what should've been a minor change that ended up going on for two weeks.

Realm reduced the core size by approximately 90%, and while I've given up the cross-platform part (target platforms were iOS, OS X and Windows; obviously not focussed on Windows at this point), the code clarity and ease with which I can change data structures makes this approach so much better.

Are you guys looking at supporting Windows/C#/.NET at this stage, because while I don't develop much software for it, it does come up occasionally, and it would be good to use it throughout.

I certainly have that tendency, perhaps the external chaos is a result of my decision-making, and not out of my control as much as I think.

I get that. There are times I need to relax by being alone. Then I'm the Earth flipping magnetic poles and being alone irks the shit out of me.

It is most annoying.

I dunno, I'm supposed to be an introvert but I'm chaos incarnate. What does that make me?

Jay's a legend - worked with him on one of his indie games back in 2004. I remember this doing the rounds a while back and am glad to read again.

As much as I don't like the .NET stack myself, you should go with what you know, unless you're specifically looking to learn something new. There's enough risk in starting up as it is without burdening yourself with learning an entirely new stack.

I had this exact issue - my entire workflow revolves around GitHub (and by extension, GitHub Issues). Eventually found waffle.io and have been using it ever since, as it's quite Trello-like.

That's the part I don't get about the grandparent's post. I've never had problems with outages on App Engine. It went down during the massive outage where half of Google's services went down. Other than that it's rock solid, and features get put in slowly.

I've had the exact opposite experience, and the experience you speak of is the one I had with Microsoft Azure PaaS.

The only discontinued runtime was Python 2.5, and admittedly because of the lack of threading support it's cost went due to the way billing was changed. Upgrading to Python 2.7 was a piece of cake, and enabling thread safety returned the expense to reasonable levels.

App Engine was built for massive scaling, and anything like that is going to have tradeoffs and idiosyncracies. There's always going to be tuning and optimisations. As long as my sysadmin is kept to a minimum, I don't care. I'll leave Google to deal with outages and scaling, since they are an order of magnitude better at it than I am.

If you want exorbitant pricing with a good dose of headfuckery, deploy to Heroku.

Bad designers love the swoosh. It's a "graphic element", for when you're too lazy to think of an idea.

Honestly I think these logos are low-quality, because there is no thought put behind their creation.

4 weeks of annual leave, plus a ridiculous amount of public holidays in Australia. We'd be pretty close in standard.

Cheers, just been looking for this kind of thing, seeing as my workflow is centered around GitHub.

I'm quite sure that Context.IO does the same thing, as I've used it before (although they directly interfaced with IMAP).

I don't remember the source, but I read an article a couple of years ago that linked that statistic of plummeting death rates in Norway during WW2 to high consumption of cod liver oil, which apparently was readily available. Take that as you will.

I used to call myself a owl too. Often I would be in a haze until late afternoon, then work right up until I went to sleep. Running a business with employees meant I had to shift to mornings (though no longer), but now I'm definitely a lark. My schedule is almost reversed: I work an hour after I get up, and then chill out a couple of hours before bed.

Overall, on this schedule I feel much more rested.