🟠 Write code first and sort it later / never or 🟢 Make a plan then start writing code I started with 🟠 and now regret I didn´t do 🟢. Which one are you? #gamedev #indiegamedev #solodev - ThreadSky

openindie.bsky.social • 90 days ago

🟠 Write code first and sort it later / never

or

🟢 Make a plan then start writing code

I started with 🟠 and now regret I didn´t do 🟢.

Which one are you?

#gamedev #indiegamedev #solodev

Comments

arkethos.bsky.social•90 days ago

Making a plan, even a basic one, gives you guidance on the direction needed. Pseudocode (common language of “need player input here when X happens”) is super helpful. Just talking it out on paper can help avoid potential problems. Using sticky notes for components/systems is also useful.

zeliotl.bsky.social•89 days ago

im very much 🟠 where i write the code bit by bit until ive reached the baseline of what i want, then i gradually add onto parts while sorting things out. i guess maybe its a bit different for me since i do shaders mostly and those are a bit hard to plan ahead for imo

brainfartstudio.bsky.social•90 days ago

Both.

I plan future out future projects while working on current projects. (Lunch breaks or something.)

Once I jump into development, it goes quickly. But I do make a point to go back and refactor at the end of every branches dev cycle.

It’s just what I’ve found works for me.

bergberggames.bsky.social•90 days ago

I’m 🟠 but you have to keep reminding yourself that temporary is temporary, and don’t hesitate to kill your darlings. But sometimes I fail to do that too 😅

openindie.bsky.social•90 days ago

Also looking for good info material how to 🟢 in a good way. 😁

gray-forge.bsky.social•90 days ago

I've definitely the green points but still some of the red. Or maybe reverse... Kinda both? I have no clue actually. I'm red/green colorblind. :D

sextantstudios.bsky.social•90 days ago

I come from "traditional" software engineering (I have way too many CS degrees 😅) so I'm trained in always writing the PRD first (= product requirement doc). Or, when it comes to gaming, the design doc goes first. Plan can diverge later, but always start from the doc.

perroboc.com•90 days ago

In my experience, game code is a set of systems. Iteration is important, and isolated testing too.

What I do is write code first in an isolated project to test the concept, and then move to a planned out system.

Cleaning comes periodically and it’s a PITA. Documentation comments too.

eliotw.bsky.social•90 days ago

🟤 Change syntax style mid-project but put off refactoring for months

Comments

Posting Rules

Reply