Project Management for disorganised people

-

 

There’s a certain kind of person (I have been lucky over the years to have worked with many very talented examples) who has a very structured approach to starting a new project. They might start with something like high level goals and proceed logically from there to task decomposition, dependency analysis, and the application of a whole host of internally consistent, repeatable  techniques for considering the task from every possible angle to ensure there are no gaps. They then refresh on a regular basis to see if everything is coming along as planned.

My brain doesn’t really work that way. My process usually starts with “Huh, wouldn’t it be cool if..?”, assembling every scrap of information I can about whatever it is, jotting down insights as they occur and then staring vacantly into space 90 minutes later when the flow state ends and I try to make some sense of it all. This always leaves me feeling that there must be something that was missed, but after 15 or so years of seeing this play out in the workforce, I’ve come to the conclusion that no, it really does end up in exactly the same place as if I’d forced myself to start from first principles. The mind doesn’t really seem to care whether we use System 1 or System 2 thinking to encode and retrieve information, and once information has been assembled into a logical sequence, it may not matter when using it later whether that sequence was arrived at intuitively or in a series of top-down logical steps.

The strength of the intuitive process is that it’s fast and good for making decisions quickly. Where I think it suffers is in the follow-up; I find it actively painful to look at a list of things and ask myself, line by line, “where are we with this?” (this is why my wife project manages holidays).

All of which is to say, I’ve got some unformed ideas on where to start, what I’ll need and where the gaps are, but this isn’t going to be very pretty just yet.

What I know

·         Common features of games I’ve enjoyed (mostly RPGs, strategy games and the importance of the random sadism of the failure elements in roguelikes and soulslikes)

·         UIs that I like and those that incite rage and property damage

·         How to properly budget an individual game (in terms of upfront costs, realistic projections for indie dev sales-over-time and consequent ROI)

·         Legal and accounting aspects of setting up a business

·         General overview of IP law that’s a few years out of date and not all that helpful for software specifically

·         30+ years of concepts for games I know I would enjoy if someone else made them, with one very specific and simple concept I think will make a simple, fun project

·         Everything takes twice as long as you think it will, and then twice as long again

·         Not terrible at math maybe?

What I don’t know

·         Fundamentals of computer science, data architecture and so on

·         Will I find coding easy, hard or in-between?

·         How much art will cost and where to source good artists

·         How do you do all the fiddly bits – installer packages, sound and graphics driver support, load-and-save mechanics

·         IP considerations: details of how code is protected, implications for reusability of code for learning via courses, textbooks and examples from GitHub. Intuitively, basic stuff like how to make a save game, make a graphics driver work and code a menu screen can’t be guild secrets but it will be helpful to know how this actually works in detail fairly early on

Comments

Post a Comment

Popular posts from this blog

Week 5 - Lab (Inheritance) Done

-
The principal difficulty with programming, so far as I can determine, is holding in one's head a mental model with several layers of abstraction.  Inheritance was a fun little project. The CS50 team wrote a program to simulate the inheritance of alleles over three generations. They then ripped the guts out of a few key parts and asked us to repair them.  I'm torn over this as a teaching method. On the one hand, it does make it easier to isolate individual concepts. On the other, you're working within someone else's framework which means you need to spend time developing an intuitive understanding of it.  Anyway it's done now. On to Spelling. 
Read more

Tideman. Tideman! (pounds desk) TIDEMAN! (Cs50x 2021 weeks 2 and 3)

-
Image
If Week 1 was the learning equivalent of jumping into an ice-cold pool and trying not to drown, Weeks 2 and 3 were doing the same thing from a ground level diving board and from the high dive, respectively. Once you’re finished it’s not too bad, but the process of getting there instils a vague sense of dread followed by a terrifying ice-cold shock. Content Week 2 spent some time on the concept of arrays; integer arrays, string arrays, multi-dimensional arrays and what you could do with them, and assessed this through some basic cryptography. Specifically, a fun little program for scrabble scoring, followed by a couple of encryption puzzles. All this took a few hours start to finish and while the harder of the encryption exercises involved a bit of head scratching and a couple of frustrating re-writes of code, it didn’t require any particular mental gymnastics, and I was done with it by Tuesday.   Week 3 though, oh boy. I started watching the Week 3 lecture on Wednesday fresh-...
Read more

What if, like, I decided to give it all up and make games?

-
Since I was a child, my dearest and most beloved hobby has been playing computer games. Aged five, when I should have been reciting the times table in my head or at least pretending to pay attention in class, I was actually running through strategies for maneuvering Dizzy (a kind of sentient egg) through the strange and surreal world that the Oliver twins had built. At high school I spent endless hours glued to Civilization 2 (and when the school library got Internet access, God knows how many minutes over lunch and breaktimes downloading scenarios from the defence of Stalingrad to the Peleponnesian war). I briefly put games to one side (never away) when I was correcting for this  intensely  nerdy childhood at university, postgrad school and in the first few years of professional life. Which is a fancy way of saying I started working out, started dating, got a job, eventually got married and generally learned to masquerade as a responsible adult. By the time my wife and I had ...
Read more