@agami
It's not really practical to do that level of detail, and I don't think it should be done.
For one thing, the blog would be the most boring ever. Imagine it being like this:
"Today I made no progress. Tracking a bug."
"Still tracking a bug."
"another day. where is it?"
"Found a missing equals sign. Hurrah!"
"Still doesn't work. D'oh!"
"Ripped out huge chunk of code. Too much like spaghetti."
"Bug gone. Now had to write data structures for input handler."
"Wrote input handler"
"Found bug and squashed it"
It'd be a proper yawn-fest, so nobody would read it anyway.
Also:
You should publish your ideas and weird mistakes to the
public because it is the 21st century and that's how things are done
now.
I don't know of anybody who blogs to this level, and even if someone does, it doesn't mean the rest of us have to.
Nearly all Amiga work is done part time now. You don't want to see lots of blogs saying "Nothing got done today", but that is exactly what you would see.
Also, I don't see why a developer "should" do anything. The developer is not employed by a user, nor is he behooven to him on any way. If Toni Willen does it then great, that's nice, but that's just his personal choice.
Put simply, a developer can do whatever he wants in the manner he wants, it is not for the user to decide what he must and must not do. Trying to force rules and regimes on people who are basically just doing it for a hobby and love of the platform more than anything else is just going to push what developers we have left away.