186 karma · joined March 26, 2013
And yes, we will run DOOM on this hardware at some point, but projects such as these take a long time to create! After all, we are only 3 people working on this in our free time. Have patience until then :)
A reporter interviews an old highlander at his home:
- What's your secret? How did you manage to live for so long? - For all my life I've followed three simple rules: no alcohol, no tobacco and no women!
Suddenly they hear some noise behind the wall in the other room.
- What's that? - asks the reporter. - Oh, that's my elder brother. He's drunk again and is beating his wives for hiding his cigarettes.
I was also considering Slate, but have found this rather annoying bug https://github.com/ianstormtaylor/slate/issues/4833, which is surprising as it doesn't look like some rare edge case, and breaks something that seems to be like basic functionality for an editor. Had to re-consider.
I couldn't wrap my head around git for a while when I started. Some time later I decided to write a procedure for our branching flow at work. I wanted it to cover all the common cases like: checking out a branch, squashing and rebasing, undoing things, amending commits, etc. All of which I knew was possible with Git, but I didn't feel comfortable with most of those operations and had to go to Google almost every time. So in order to put that all down in simple steps with some short explanatory comments I, obviously, was supposed to very clearly understand all of those cases myself to be ready to answer some questions and moreover to be sure that each step is a correct way to do git and it wouldn't cause any permanent damage to anybody's repo. To get that understanding I created a few nested directories with some really small text files in them and used those to actually run and inspect consequences of various git commands which took me, maybe, about two hours maximum. I've never had a single problem with git ever since.