Learning by Trial And Error

Reading Time: 4 minutes

Every day or two I see people post about how the Fediverse should be simplified to welcome new people. It's a shame. Signing up for a fediverse server is easy. It's the same process as for every site. The biggest difference is that you're signing up for a privately owned, crowd sourced community instance. The instances vary slightly from mastodon to firefish to ClassicPress to WordPress but at their core they are the same. It's just the community that changes, but even that can be the same if you migrate from one instance to another.

Experimenting

A core aspect of the World Wide Web is that it is a platform where people can experiment with ideas, community tools and more. If you need a manual then you are stuck on websites like Twitter and Facebook, rather than exploring what the World Wide Web has to offer. You're stuck in a silo.

It worries me that people want to simplify the Fediverse, to write guide books and tutorials. If you spend an hour or two experimenting you'll understand how things work with ease. I don't think we need manuals for everything in life, especially not social networks on the fediverse.

The Case for Manuals and Tutorials

There are moments when manuals and tutorials are important. That's when you're trying to use something that is not as intuitive as you had hoped. WordPress is plug and play and requires no manual. It works like every other CMS works, so it's easy to pick up. Hugo is easy to pick up, but you might need to RTFM for one or two functionalities.

The moment you really need a manual or instructions is when you're experimenting with Angular, Laravel, 11ty, Jekyll and other platforms. It's when you don't know what the options are that you need a manual. With the Fediverse all the answers are easy to find. You just need to spend a few minutes looking for them. I suspect that chatGPT, Bard and Bing AI can help you when you have questions.

With Hugo I was able to create pages and get a table of contents with relative ease. With 11ty I got a little stuck so I felt the need for a tutorial. I know what I want to do, and I know how I expect it to work, but it's not like other solutions. that's why I decided that for 11ty I would use a learning resource, or more, to experiment with, and learn how to use the tool. I am not against manuals and instructions. I like to read the fantastic manuals, when I get stuck. I even like to ask AI for help in some cases, because I can ask a tailored question and get a tailored answer.

The Case Against Manuals

The more time I spend on Mastodon and the Fediverse, the more it feels like a waste of time. I love the concept, and the freedom we have on the website. What I don't like is that people want to write manuals and instructions to make the same mistakes as people made, on mastodon, and if that is the case, then I have no reason to stick around. Every day people discuss how to use hashtags, bully people into writing alt text for imagess and encourage thousands or tens of thousands of people to follow individual accounts. If that is what people want then there is little reason for using Mastodon, rather than Twitter. Twitter has the community of friends amassed from 2006 to 2023. The Fediverse is a network of strangers.

I Want the Community to Teach Itself

I want communities to learn by participating, rather than reading. I don't want people to read a manual about how to use the fediverse, I want them to learn by trial and error, and by what feels good, rather than by doing what is expected. The more time I spend on the fediverse, seeing people speak about better onboarding, the more it feels kitsch, and the more I want to close the tabs.

Experimenting with Eleventy

Since I was getting stuck with eleventy I decided to follow Learn Eleventy From Scratch. As I said, it's not that I am opposed to learning from guides, manuals, or documentation. I like to learn from these sources, when trial and error doesn't yield the results that I am looking for, or where trial and error takes more time than is reasonable to figure out.

What I want to do is simple. I want to have one directory for posts, and so far that works quite easily, but I also want another folder that acts as an archive. That is where I am getting stuck, and that is where a manual can streamline my learning process. It's when I see that I have gaps in understanding that I use manuals to fill them.

And Finally

In my experience the people who write manuals on how to use social media websites are utilitarian, rather than humanists. They encourage people to develop a utilitarian approach to social media and that's what I fear, and object to.

When you look for books about blogging none of them are about the philosophical or intellectual process. They are all about monetisation, which is fantastic, if you want to be a spammer, but awful if you want to be a humanist. I blog to explore ideas, concepts, and speak of cycling, walking and climbing experiences. If I followed the guide books my blog would be aimed at making a fortune, rather than developing and elaborating ideas.

I will always try something new, without RTFMing (Reading the fantastic Manual), before getting stuck and following a tutorial. What has changed is that now I am learning through manuals, instructions and more, rather than online tutorials. I am learning independently. I am a step further along now.