"Create a list of things to do, in the order you intend to address them, and make that list public. And then follow-through on working through that list. And then, give a 5-minute monthly updates on your progress.")"
I wanted to address this statement by Josh.
Sorry, Josh, but thats not exactly how business-to-consumer products work. The "list of things" change based on user feedback, and then so does the priorities. I have worked as software developer in quite a few companies, and can assure you that there are some issues that never gets fixed, it is usually because the project is understaffed, or because the roi is not significant to warrant that change.
Regarding refusal help from Internet stranger, I understand your stance, but I also understand dominion's stance. The efforts and time to bring someone up to date with the codebase, and then vetting their commits, is a job in itself. I have had interns and juniors reported to me, and there were some days when i was doing nothing but doing code review. Considering stef is doing most of the coding by himself, i dont think it is a good use of his time.
I wanted to address this statement by Josh.
Sorry, Josh, but thats not exactly how business-to-consumer products work. The "list of things" change based on user feedback, and then so does the priorities. I have worked as software developer in quite a few companies, and can assure you that there are some issues that never gets fixed, it is usually because the project is understaffed, or because the roi is not significant to warrant that change.
Regarding refusal help from Internet stranger, I understand your stance, but I also understand dominion's stance. The efforts and time to bring someone up to date with the codebase, and then vetting their commits, is a job in itself. I have had interns and juniors reported to me, and there were some days when i was doing nothing but doing code review. Considering stef is doing most of the coding by himself, i dont think it is a good use of his time.