Author Topic: Writing a retrospective  (Read 6038 times)

Krice

  • (Banned)
  • Rogueliker
  • ***
  • Posts: 2316
  • Karma: +0/-2
    • View Profile
    • Email
Writing a retrospective
« on: March 07, 2014, 01:32:15 PM »
I had an idea to write a retrospective from Kaduria, years 1996-2004 or the phase 1 as I call it. I really don't recommend it to anyone. Not only I spent three hours writing it, but after that I had some kind of recall where I was thinking who I am, and after that I've been depressed remembering the things I could have done other way. Mainly in context of getting sex.

jere

  • 7DRL Reviewer
  • Rogueliker
  • *
  • Posts: 233
  • Karma: +0/-0
    • View Profile
    • Email
Re: Writing a retrospective
« Reply #1 on: March 07, 2014, 06:30:09 PM »
 :(
Golden Krone Hotel -- available on Steam Early Access now

chooseusername

  • Rogueliker
  • ***
  • Posts: 329
  • Karma: +0/-0
    • View Profile
    • Email
Re: Writing a retrospective
« Reply #2 on: March 07, 2014, 08:51:31 PM »
How depressing.  The only kind of retrospective I want to read, is a developer's journal.

December 12th, 2010
... Lots of detail about thoughts on game design ..
December 13th, 2010
... etc

Krice

  • (Banned)
  • Rogueliker
  • ***
  • Posts: 2316
  • Karma: +0/-2
    • View Profile
    • Email
Re: Writing a retrospective
« Reply #3 on: March 07, 2014, 09:40:45 PM »
It's not all depressing. Anyway I realized I can't write even the first part before the game itself is ready.

Vanguard

  • Rogueliker
  • ***
  • Posts: 1112
  • Karma: +0/-0
    • View Profile
Re: Writing a retrospective
« Reply #4 on: March 09, 2014, 07:06:29 AM »
How is that coming along anyway?

Krice

  • (Banned)
  • Rogueliker
  • ***
  • Posts: 2316
  • Karma: +0/-2
    • View Profile
    • Email
Re: Writing a retrospective
« Reply #5 on: March 09, 2014, 12:23:14 PM »
It's fine I guess. The big change in my working has been that I can now define problems easier than before and also the order in which features are done is better which I hope means less rewriting and more stable code.