[DiscordArchive] The argument emulator developers always use against scripting is performance, but performance is not
[DiscordArchive] The argument emulator developers always use against scripting is performance, but performance is not
Original source
i think there can be a balance somewhere, and it probably depends on how you prefer to work. I can get a lot more done if i'm more liberal with how many tangents I end up in rather than considering whether every single thing I'm doing should've been cut off and implemented independently
rektbyfaith
11-15-2021, 10:54 AM #31Archived author: <o> • Posted: 2021-11-15T10:54:57.036000+00:00
Original source
i think there can be a balance somewhere, and it probably depends on how you prefer to work. I can get a lot more done if i'm more liberal with how many tangents I end up in rather than considering whether every single thing I'm doing should've been cut off and implemented independently
Original source
since starting on tswow I _have_ tried to improve still documenting all the changes I make, but then i'd still prefer to just note them down in a single larger commit message
rektbyfaith
11-15-2021, 10:55 AM #32Archived author: <o> • Posted: 2021-11-15T10:55:55.819000+00:00
Original source
since starting on tswow I _have_ tried to improve still documenting all the changes I make, but then i'd still prefer to just note them down in a single larger commit message
Original source
Yeah everyone works differently. I definitely get more done and faster if i'm being super liberal with things and just plodding on but find myself missing obvious bits or encouraging scope creep.
Which is why before embarking on my current project I basically sat down and wrote up 500ish issues in categories to work from. Over the top planning undoubtedly but has kept things on track.
rektbyfaith
11-15-2021, 10:57 AM #33Archived author: Deleted User • Posted: 2021-11-15T10:57:11.463000+00:00
Original source
Yeah everyone works differently. I definitely get more done and faster if i'm being super liberal with things and just plodding on but find myself missing obvious bits or encouraging scope creep.
Which is why before embarking on my current project I basically sat down and wrote up 500ish issues in categories to work from. Over the top planning undoubtedly but has kept things on track.
Original source
My experience is that if you try to plan in too much detail too far ahead then that planning ends up being a waste of time because you need to adapt/change to new things being found or learnt from. Hence agile methodology
rektbyfaith
11-15-2021, 10:59 AM #34Archived author: stoneharry • Posted: 2021-11-15T10:59:17.594000+00:00
Original source
My experience is that if you try to plan in too much detail too far ahead then that planning ends up being a waste of time because you need to adapt/change to new things being found or learnt from. Hence agile methodology
Original source
Things will have to pivot more agile once I have people actually playing for sure but right now while it's entirely closed dev and testing its working okay.
rektbyfaith
11-15-2021, 11:00 AM #35Archived author: Deleted User • Posted: 2021-11-15T11:00:47.866000+00:00
Original source
Things will have to pivot more agile once I have people actually playing for sure but right now while it's entirely closed dev and testing its working okay.
1 Guest(s)
1 Guest(s)