Daniel J. Petersen’s Devblog

Documenting my struggle to make a videogame.

The Looming Indie Crash?

I just read a blog post from Cliff Harris, the man behind games like Democracy 3, Gratuitous Space Battles, and Gratuitous Tank Battles. This is going to be a response to that post.

To preface this, I respect Cliff quite a lot. I probably value what he says more than anyone else in the industry, and if there was one person that I’d want to model my career after, it’d be him.

With that being said, I think I disagree with him on this. I don’t know that a crash is incoming. People want to make games. They’re going to do it as a hobby, or part time, or they’re going to risk everything and take the chance at going full time indie. They’re going to do all this whether or not they make money. And statistically, they won’t make money, but it doesn’t matter. They’re going to continue making their games, because they love games.

Not only do they love games, but they love their games. Objectively their games are shit, but it’s hard to judge the value of your own work. You tend to either think it’s a lot better than it actually is, or you tend to think it’s a lot worse than it actually is.

I’m making a video game. I’m going to sell this game. I’m not expecting to make any money from it. I’m not expecting anyone to even care. I’ve read countless post mortems at this point detailing how they made 23 dollars their first week, if even that. But I’m still going to do it, because to me, my game is awesome.

There’s a reason why the games industry is able to pay programmers a lower salary than they would earn in other software fields. There’s a reason why they can work these guys longer hours than they’d be worked in other software fields. People love games. People want to play games. People just want to work on games, and they’ll do it whether or not it makes sense financially.

I’m not sure I understand his Unity comment. I don’t personally use Unity, but I think it’s a good business decision to do so. You’re offloading a lot of tedious work that you would otherwise have to do yourself. It’s a tried and true engine which you can rapidly prototype with. I’d even go so far to say that it’s borderline irresponsible to not use an engine like Unity or Unreal 4 if you’re not already an established dev with an engine under your belt like Cliff is.

We’re probably moving into something more akin to the music industry. There are so many unnamed and unprofitable bands out there, but it doesn’t matter. People will continue to form bands, and most of these bands won’t make it financially. Some people (most? all?) just have a deep seated desire to create.

Programming and Stenography

Before I got into programming I was interning and on track to be a professional stenographer. It’s a stenographers job to transcribe spoken word into written form, usually for courtrooms, conferences, TV captioning, or to help out the deaf community.

In order to be able to keep up with how fast people are able to talk, Stenographers type on specially designed machines like the one above. These machines allow people to reach speeds of 300+ words per minute. You have to be able to write at a staggering 225 words a minute with at least 99.9% accuracy in order to even be eligible for work. To put this into perspective, 110 words per minute is about as fast as the most people can hope to reach on a regular keyboard setup.

I think people see these stats and start imagining all the different scenarios and uses cases for being able to type at 225+ words per minute. To give an example, I and read a Hacker News thread a few days about an open source program which is best explained as Microsoft Word for stenography machines. It’ll translate the strokes from a stenography machine into English and it’ll also allow you, with the help of an attachment you’ll need to buy, to turn a regular keyboard into a stenography machine. Stenography can now reach the common man!

A lot of people seemed generally optimistic about the idea of stenography creeping into everyday life, or at least other professions. One person asked, “If Plover can effectively make Steno keyboards understandable by our OS of choice… Should we start teaching our kids this thing before they ever get hooked into qwerty?”

And the answer is no .

Stenography is in no way shape or form suitable for everyday use. The talk I linked to above was pushing the idea of using stenography for programming, which is in my opinion is an awful idea. I cannot hammer home this point home enough – no one should seriously consider it.

This is the stenography keyboard. Notice anything unusual? There are only 21 keys on there, yet there are 26 letters in the alphabet. And it’s actually more unusual than that, because there are a few letters which are on both the left and right sides.

QWERTY is pretty straight forward to learn. There’s a key for every letter in the alphabet. You press a key and it appears on your screen. Simple. And yet I still see people struggling to type above 40 Words Per Minute.

With stenography machines, the keyboard is separated into two halves. On the left half there are only 9 keys, but each letter of the alphabet can be written with those 9 keys because it’s context sensitive. The letter “t” by itself would be the letter t, but if it’s next to a “k”, it might become the letter d.

You’re not so much typing letters as much as you’re typing sounds. So the word “car”, for example would be written “kar”, or the word “talk” would be written “tauk”. You’re also not typing letters individually. The entire word is considered as a whole, and the goal is to press as many letters of a word as you possibly can at the same time. So for the word “tauk” you’d press T, A, U, and K at the same time. Sometimes you can get the entire word in one stroke, but some words you need to come back for a second, third, or god forbid forth stroke.

Because it’s all phonetics based, you run into conflicts like “sell” and “cell”, so you still need a way to write a c, but that’s the gist of it.

Worth mentioning is that there are only 4 vowel keys on the machine. A, O, E, and U are the vowels that are on there, and if you press one of those keys individually, you’d write a short vowel of that key. If you wanted to write a short I, you’d press E and U together. You would write long vowel sounds by combining different vowels together. So for example, if you wanted to write a long e sound, you’d write aoe, long U sound would be aou, long a sound would be ai (or aeu depending on how you look at it), long o is oe, and long i is all the vowels together at once.

You can see that combining letters together to represent more complex strings is a big part of stenography. The real secret behind it is that they take this concept to the extreme. People use what they call briefs, which is combining commonly said words together into unique key strokes. “T S” combined together might form “it is” for example. And because speed is the only thing people really care about, the concept is taken to an insane degree. People try to abbreviate everything. Entire sentences written in one stroke.

What does all of this mean? For starters, it can be hard to read what you’ve actually written. The word dime, for example, you’d see raw as “TKAOEUPL”. TK for D, AOEU for long I, and PL for M.

It means that everyone is writing in their own language unique to them as an individual. Sure, you might learn the same theory as another person, but that theory gets warped and manipulated into an abomination of its former self thanks to the necessity of using briefs to achieve the desired speed.

It means that you have to go through a painstaking process of defining your own dictionary so that the machine can translate your strokes into english. This will take years. I was at it for two years, and while I was able to write at around 240-50 words per minute, I still had a daunting number of briefs and phrases that I was adding to the dictionary on a daily basis.

It means that speed is the only thing that people care about. At high speeds people are advised to just write something down, -anything- down in the heat of the moment, because you can decipher it later on. Which of course means having to actually go through what you’ve written and make sure everything is properly translated into english, because you’re going to make mistakes when you’re writing that fast. A misstroke might be obvious, or it might be a mistroke which forms another word or phrase. You won’t be looking for just an underlined red word, you’ll be checking every word written to make sure it’s the word or phrase you meant to type, decoding everything you’ve written based on the context it was written in. Sure, you’ll write write at 225 words per minute, but the aftermath is time consuming. Definitely more so than writing at 110 words per minute and not making any mistakes, which is something I’m confidently able to do with a regular QWERTY setup.

It means stripping syllables off of words in order to get the word written in fewer keystrokes, which of course adds to it being harder to translate later.

To expand on the last two thoughts, your writing will be vague. You can type exactly what you want to appear on screen with a QWERTY keyboard, and there will be no ambiguity about it. You can certainly type the exact thing you want on a stenographic keyboard, curly brackets with proper spacing and all if programming, but you’ll need to be unreasonably good to do so.

It means that it’s a complex system which is time consuming to learn. They tell you it’ll take two years to learn, but I’ve met people that were at the school for 4+ years and unable to advance. It doesn’t appear to be something which everyone is able to grasp.

It means changing your very way of thinking. I think anyone who reaches the state of being able to write at 225 words per minute has to have their way of thinking shift slightly. Stenography is now engrained in my brain, and every word, every single phrase you can possibly utter is permanently associated with a hand motion. It does not add any value, and it does not go away.

I’m quite frankly not even sure why people want to program at 225 words per minute. The bottleneck in programming, for me at least, is how fast I can think, how fast I can design and structure the code, and how fast I can solve problems. How fast I can type has never been a bottleneck. Stenography requires a certain portion of your brain power, so your thinking is going to be bogged down by adding that layer of abstraction between you and your writing.

Given that, I wouldn’t be surprised if stenography actually hindered programming. I think it’s very telling that the person leading the Plover project has had a hard time learning how to program. That extra layer of abstraction is distracting from the actual goal, writing code.

I’ve heard the idea that stenography might be good in terms of preventing arthritis or repetitive stress injuries, but I think that varies depending on the person. My hands have not been the same since I took up stenography. There are professional stenographers that I’ve spoken to who complain of horrible hand pain. I personally don’t have any problem typing all day on a regular keyboard, but a day of stenography takes a toll on my hands.

I think at the end of the day, the Plover guys are trying to solve the wrong problem. Stenography is a dying field. I don’t wish anyone to lose their livelihood, but realistically speaking, the job should not exist once text to speech technology advances far enough. I’m not claiming that the field will be replaced by it, but I also don’t love the idea of people having to learn such an inane and archaic system.

The Destruction of My PC, and the Coming Code Bootcamp Destruction?

About two weeks ago my desktop (video card?) decided that it was done with life. I was jamming away working on It Always Ends In Nuclear War when I was greeted with a bluescreen of death. I started my computer back up and the resolution was keyed in at 800 x 600 with a scattering of red pixels on the display. I decided that the PC was haunted and that it was time to go all out and get a new PC. I just finished building it yesterday, and I’m pretty excited.

  • ASUS Z97-A ATX DDR3 2600 LGA 1150 Motherboards Z97-A
  • EVGA GeForce GTX 780Ti 3GB GDDR5 384-Bit Dual-Link DVI-I DVI-D HDMI DP SLI Graphics Card 03G-P4-2888-KR
  • Ballistix Sport 8GB DDR3-1600 (PC3-12800) CL9 Desktop Memory Module
  • Ballistix Sport 8GB DDR3-1600 (PC3-12800) CL9 Desktop Memory Module
  • Core i7-4790 3.6 GHz 1150 Boxed Processor
  • Hyper 212 EVO Universal CPU Cooler
  • GXII 750 Watt ATX Power Supply
  • MX100 512GB SATA III 6.0Gb/s 2.5” Internal Solid State Drive CT512MX100SS

I’m pretty damn happy with it. Its destroyed every game I’ve thrown at it, and it compiles It Always Ends In Nuclear War soooooooooooooooo damn fast. I couldn’t really work on the game until I had my desktop in order, but now I can get back to work full speed ahead.

In other news, the author of Learn Python The Hard Way and Learn Ruby The Hard Way is going to be posting a series of articles criticizing coding schools. I attended Dev Bootcamp in early 2014, so this is particularly interesting to me. For what it’s worth, I’m glad I attended Dev Bootcamp. Mostly because it was a cool experience, but I also think I learned some valuable things from it, both programming wise and about life in general. That being said, I don’t particularly think coding schools are a great investment if you’re new to programming, and I wouldn’t say that I learned to program from Dev Bootcamp. Don’t get me wrong, it definitely helped, especially on the web dev front, but I’ll be very interested to see what Zed Shaw has to say.

New Website?

I’ve been thinking tonight about what my future plans are in terms of this blog. I enjoy posting on it, and want to do so more often, but perhaps more than that, I also want to add some features to this website (and in extension, It Always End’s In Nuclear War’s future website) that I think would be pretty awesome to have.

Unfortunately, they’re features that aren’t really suited to Wordpress. Wordpress is awesome and I have no complaints with it, but I do think it’d be a challenge to accomplish what I want to do with Wordpress.

I also find myself wanting to brush up on my Ruby skills, which are getting rusty at this point. I’m therefore thinking that I’m going to spend some time redoing the website, probably building it out with Ruby on Rails and switching over to Digital Oceans (sorry Bluehost!)… Or not. I’m not committed to this idea yet, it really depends on how much work it turns out to be. I suspect it’ll be very doable, but that might just be me being naive.

I mainly want to have the website closely linked with It Always Ends In Nuclear War. For example, I’ve been keeping a I’ve ever taken of the game, but it’s hosted on Dropbox, which isn’t really ideal. Those screenshots should be hosted on this website. I also think it’d be cool to continue documenting the game in this manner, even after I release it. I’m thinking aloud here, but It Always Ends In Nuclear War should have a screenshot button built in, which will automatically save the image to your PC, but also automatically upload it to this website for everyone to see. And we could go further than that. People in the Civilization Community post playthroughs of their games on community forums, and they’re actually a really fascinating thing to read. They go through painstaking detail to take screenshots as they progress through their game, and keep notes so that they remember what their thought process was during that point in the game. The game could provide a nice and official avenue to pursue something along those lines and have it posted here. Along that same manner of thought, there could be a centralized place to share saved games. You could tie in the documentation of the progress feature with the save game sharing, so that each picture is accompanied with a saved game.

I literally came up with that idea out of the blue while writing this. I’m not saying I’m going to do that, but I think there are a lot of really cool unexplored possibilities, and I want to have my options open in case I decide to pursue them. First thing first, transferring this blog off of Wordpress…

It Always Ends in Nuclear War Update 6

It Always Ends In Nuclear War is a game I’m making which aims to simulate human history, allowing you to guide a people from the dawn of civilization into modern times. You can find the previous post about it here , or to view a gallery of almost every screenshot I’ve taken during development (currently 715 screenshots!).

Creeping slowly toward playability…

I’ll Be Damned if I Can’t Do That

I moved into a new apartment a few weeks ago, and I haven’t yet bothered to get a computer desk. Truth be told, I’m not sure if I’m going to even bother getting one. My current setup has me situated on the couch, with my desktop monitor on a small table in front of me. This is a pretty good setup, but it’s not very practical to use a mouse with. I mainly use my PC for programming nowadays, and there’s not too much of a need for a mouse, so I decided to get a keyboard which had a trackpad attached to it.

It’s not what I’d call a good keyboard, but it’s pretty good for my use case. Problem is, I use the F5-F7 keys as hotkeys for programming, and this keyboard has media keys in their place. You can press the F keys, but you’ll have to press and hold the FN key first, which is annoying to say the least. I hopped onto Logitech’s website and downloaded their software which lets you control how the keyboard works. I didn’t see an option to disable the media keys, or switch the FN toggle. After a bit of googling I found a forum post by a Logitech help staff saying that you can’t do what I want to do.

That can’t be true now can it? I think the coolest thing about programming is being able to make the computer do whatever you want. I’m happy to report I have my Fkeys back by writing a short script which will convert a media key into it’s prospective F key upon press. It took 3 minutes.

It Always Ends in Nuclear War Update 5

It Always Ends In Nuclear War is a game I’m making which aims to simulate human history, allowing you to guide a people from the dawn of civilization into modern times. You can find the previous post about it here , or to view a gallery of almost every screenshot I’ve taken during development (currently 682 screenshots!).

I recently moved into a new apartment, which took up a bit of my free time, but I’m all settled now and back to working on this game in my spare time. I’ve started a system in which I assign myself weekly tasks, and it seems to be a good mechanism to keep myself motivated and on track. These are pretty specific tasks that I think I can reasonably accomplish in a given week (ie: This week one of my tasks was to finish a basic version of a dialog box gui widget).

I’m going to be experimenting with a milestone system, too, which I think will also help out with keeping me motivated and on track. The current thinking is that at the beginning of every month, I’ll create an overview of features which I’d like to be completed at the end of the month, and I’ll designate this with a version number. This month I’m hoping to have a very basic version of the game playable, which I’m going to be designating alpha 0.1. Here’s the list of features for this month.

The past week or two I’ve been working on creating some simple GUI widgets, and a general structure for which to manage the game’s gui system. The widgets are going to be pretty ugly for a while, because I don’t particularly care about that at the moment, but code wise I think the system I came up with makes a lot of sense, and will be easy enough to work with.

I think that’s about all for now.

It Always Ends in Nuclear War Update 4

I’ve made a very rough and hastily put together of what It Always Ends In Nuclear War is going to be. It’s just a general overview with all nitty gritty details stripped away.

It Always Ends in Nuclear War Update 3

It Always Ends In Nuclear War is a game I’m making which aims to simulate human history through the ages, allowing you to guide a people from the dawn of civilization into modern times. You can find the last post about it , or to view a gallery of almost every screenshot I’ve taken during development (currently 615 screenshots!).

The gamedev community at large has this thing called Screenshot Saturday. I participated in it this week with these two screens.

In other news, the game was mentioned on Rock Paper Shotgun . How fucking cool is that? It honestly made my day, and I’m still coming down from it.

In actual development news, I’d say that I’ve been working on tile type generation (ie: adding deserts / ice / forests to the world instead of it consisting of just ocean and grassland) the past few weeks. It was like two solid weeks of failure, followed by something I was semi happy with (the screens in the last update), followed again with something that I’m happy enough with for now but need to eventually improve (the above screens).

I’m now working on finishing up the game design. It’s been a huge struggle to come up with a design that I’m happy with. I feel like I’m capable of programming whatever design I come up with, but coming up with the actual design has seemed hopeless at times. To give some perspective, at one point I decided to move onto a new project because I couldn’t come up with anything I liked. And that’s with a design document filled with about 4,000 lines of ideas.

Which makes it all the more satisfying that I think I’ve finally come up with something which will be interesting and worthwhile. I’ve had a general idea of what I wanted to do for a few months now, but it’s been an abstract idea in my mind until tonight. The design still needs a bit of polish before I post about how it’ll play. I’m hoping next update I’ll get into it, most likely with some screens of a super early prototype being played. I can’t guarantee that anyone else will enjoy what the game will be, but I think it’s cool and that’s good enough for me.