I wish I was anywhere remotely as good at estimating project workload/timelines as I am programming :anotlikethis: I guess I'm learning
Conversation
Notices
-
Embed this notice
taylor (nik@misskey.bubbletea.dev)'s status on Friday, 06-Sep-2024 03:44:59 JST taylor - Sick Sun likes this.
-
Embed this notice
受不了包 (shibao@misskey.bubbletea.dev)'s status on Friday, 06-Sep-2024 22:10:57 JST 受不了包 @nik as soon as i discover something is more complex than I realized, I immediately write it all out and re-evaluate the task to break it down into as many subtasks (and subdeliverables if iteration with someone or customers is needed) and then if it's still way too big, doing design spikes/prototypes for any large tasks. if this process breaks down for other reasons then you have other problems on your hands
-
Embed this notice
taylor (nik@misskey.bubbletea.dev)'s status on Friday, 06-Sep-2024 22:10:58 JST taylor "this will take me a couple days at most, ez"
-
Embed this notice
受不了包 (shibao@misskey.bubbletea.dev)'s status on Friday, 06-Sep-2024 22:21:12 JST 受不了包 @mia@movsw.0x0.st @nik@misskey.bubbletea.dev yeah if you estimate things out really long then you can just parkinson's law to the finish
-
Embed this notice
miauz genyau (mia@movsw.0x0.st)'s status on Friday, 06-Sep-2024 22:21:14 JST miauz genyau @shibao @nik i just multiply the time estimate by some odd number between 3 and 7 depending on gut feel; roughly 8 out of 10 times i get it accurate to the minute that way :cirno_shrug: