Post AQ6FZ68TPfuM4eLIrA by freakboy3742@cloudisland.nz
 (DIR) More posts by freakboy3742@cloudisland.nz
 (DIR) Post #AQ6FZ68TPfuM4eLIrA by freakboy3742@cloudisland.nz
       2022-11-28T23:29:48Z
       
       0 likes, 0 repeats
       
       If you're an OSS project maintainer (or, honestly, a project maintainer of any kind), this DjangoCon US talk is worth your time: https://www.youtube.com/watch?v=GLkRK2rJGB0 The advice about Twitter hasn't aged well (in just 6 weeks...) but the blogging alternative is still good :-)
       
 (DIR) Post #AQ6FZ6YLrSblMuRyC0 by simon@fedi.simonwillison.net
       2022-11-29T01:16:50Z
       
       0 likes, 0 repeats
       
       @freakboy3742 I have an extensively annotated version of it up on my blog now too: https://simonwillison.net/2022/Nov/26/productivity/
       
 (DIR) Post #AQ6FZ6xsKZ1ae4OLya by kushal@toots.dgplug.org
       2022-11-29T08:30:07Z
       
       0 likes, 0 repeats
       
       @simon @freakboy3742 Q: When you start a new project, do you start developing each feature from the beginning only after creating the issue for that feature? Asking because I mostly find doing so at the very beginning is difficult than after first 1 week or so.
       
 (DIR) Post #AQ6FZ7aA2DeKYoIveS by jeff@federated.fun
       2022-11-29T15:20:01.193108Z
       
       0 likes, 0 repeats
       
       @kushal @simon @freakboy3742 the development workflow is actually very dependant on the actual software itself. e.g. the workflow ctor (if started today) would need to be much different vs an nodejs webapp.
       
 (DIR) Post #AQ6H9ggr573NpDR40O by jeff@federated.fun
       2022-11-29T15:37:53.510857Z
       
       0 likes, 0 repeats
       
       @kushal @freakboy3742 @simon this is primarily due to software each having different needs, but also roles and priorities, some things you cant compromise on but others can be put on back burner