The only way to estimate work is to make up a number and then log everything that prevents that from happening to put forward a case when the “why?” question comes up when the deadline hits. Then prepare for being told you are making up excuses and being negative and not flexible to all the challenges that you just listed and that you need to manage time better and potentially think about outsourcing some work to people who lie better than you.
I think most people are interested in helping the fediverse grow and fragmentation here is a good thing. Also subscriber count doesn’t always mean activity and engagement.
Recreating scientific studies that have been funded by large corporations is very difficult and disproving or countering any findings are less common because to apply the scientific method properly is beyond skill and know how, it’s down to money.
A programmer does not primarily write code; rather, he primarily writes to another programmer about his problem solution. The understanding of this fact is a final step in his maturation as a technician.
I always saw commenting code as writing to my future self initially, but now in a team that’s evolved to writing to my future self and referencing the comments when explaining it to people that ignore them.
Thanks for the downvotes lemmings, only asking a valid question