I think it is time to re-read A Group Is Its Own Worst Enemy: http://www.shirky.com/writings/herecomeseverybody/group_enemy.html
»the group is real. It will exhibit emergent effects. It can't be ignored, and it can't be programmed«
»The constitution is always partly formal and partly informal. …The informal part is the sense of "how we do it around here." And no matter how is substantiated in code or written in charter, whatever, there will always be an informal part as well. «
“Dread of Heinleinism - Charlie’s Diary” http://www.antipope.org/charlie/blog-static/2018/08/dread-of-heinleinism.html
it does post to websub, yes.
@natecull @kevinmarks I think it's interesting to call it a 'bug' - Lovelace had no way to run her program, and thus no way to test and no way to iterate. It may be more accurate to call it a typo - she was writing Note G out by hand, after Babbage (or the printer) lost the original version that she'd sent over to him. It's easy to imagine that the printer was also unable to properly comprehend what he was typesetting and thus could easily have introduced the error.
I wrote about the theory of Mastodon versus Twitter early last year; I think it's still mostly right http://www.kevinmarks.com/mastodontheory.html
“Today, I constantly remind myself before publishing any article that I am publishing this on *my* blog (which means that I can publish anything I want), and that it doesn’t matter if people read it or not.”
By Sara Soueidan
Do you remember when the last programming language arrived, in 1981, and it was literally called The Last One, and every program ended in a line saying 'TERMINATE' and how we all laughed
and then came the nuclear fires of Judgement Day
•Do early design work in small, invested groups
•Design in the open, but away from the bright lights of the big stage
•Iterate furiously early on because once it’s in the web, it’s forever
•Prioritise interop over perfect specs;
https://infrequently.org/2018/06/effective-standards-work-part-2-threading-the-needle/ #indieweb #microformats
Standards are documentation, not legislation. They explain how to make your code do the same thing as mine. Sadly, we write them in an imperative voice, and don't explain how we chose them. Alex has more to say: https://infrequently.org/2018/06/effective-standards-work-part-1-the-lay-of-the-land/ #indieweb #microformats
When designing a user interface, imagine some old woman using it, say Margaret Hamilton, and she's clicking your app's buttons and saying to you, as old people do,
"Young whippersnapper, when I was your age, I sent 24 people to the ACTUAL MOON with my software in 4K of RAM and here I am clicking your button and it takes ten seconds to load a 50 megabyte video ad and then it crashes
I'm not even ANGRY with you, I'm just disappointed."
Why don’t we call them post-partums? The project is not dead, to be buried; it is born, to be supported.
Tell us: What are your tips for conducting a positive post mortem at the end of a project? How do you talk through the weak points without assigning blame? Responses go in the magazine.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!