Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
-eth18448yA game complete with engine written in golang? Looks like your backlog it's a bit too generic! But I'll give this a try.
Orgmode, not the game engine -
@-eth Its a gamejam complete with Godot Engine that I want to re-implement with SDL2 just for fun. (agree on generic backlog) (have some tips?)
-
-eth18448y@CSaratakij first of all, good luck. It's an heck of a journey, pretty sure you will learn a lot!
As for the backlog, usually I make some generic containers , as per your items, and then explode each container in deliverables, I.e. what I presume what can be accomplished in a single sprint (as in agile) -
-eth18448y@CSaratakij
Ok, so you went really down on granularity, and that's fine, it give you a better idea about how much work do you still need to accomplish. You moved the concept from very compact statements to real User Stories; this is a skill you might get use for, since it is used in companies, but try not to forget that user story is a concept that closes the gap between your technical language and the stakeholders/clients "marketing" language: you do not _need_ to use this formulation for personal project, but you will _have to_ when confronting your clients with the requirements/specifications for your code.
I wonder why you just reduced the backlog from several to just 2 items, but I believe it's just an example? -
@-eth Yep, actually in this example, I have 3 story. But I just fold it by press 'Tab' . I still new to this concept though. So, Story is really about a story from user perspective like? (cuz, I just write 'As a Game Developer' at the first Story and it kind of strange)
-
-eth18448y@CSaratakij indeed, the way user stories are depicted is always from customer perspective. Usually this approach works for dealing with client. All the "behind the curtain" tech stuff can be pinpointed in the backlog in a more...precise and technical manner (and not to be shown to stakeholders)
-
@-eth Thank you so much. Now Im gonna try Org mode for one project to see if it can replace GUI board in one man team xD
Org mode as kanban board for personal projects is quite usable.
(trying to find if this gonna works)
undefined
vim-orgmode orgmode