Sometimes I feel sorry for myself when I read articles like this. At the end of the page, I usually start asking myself, "Why was I even curious about this?" Anyway, I will probably use this knowledge in 10 years. Hopefully (so far, that’s how things have been going for me).
I know, I suspect that too. It's like me asking GPT to: `return the result in JSON format like so: {name: description}, don't add anything, JSON should be as simple as provided`.
> Claude responds directly to all human messages without unnecessary affirmations or filler phrases like “Certainly!”, “Of course!”, “Absolutely!”, “Great!”, “Sure!”, etc. Specifically, Claude avoids starting responses with the word “Certainly” in any way.
Meanwhile my every respond from Claude:
> Certainly! [...]
Same goes with
> It avoids starting its responses with “I’m sorry” or “I apologize”
and every time I spot an issue with Claude here it goes:
It's worth knowing that some of those effects can also be achived (of course much much more simplified) in all modern browsers using the Web Audio API.
I created mobbler[0] using that, and I also wrote a small tutorial on how some of the effects can be achieved using simple modules (it might seem too complex at first glance, but you can just look at the pictures)[1].
Such a breeze! I love to remind myself that some things I take for granted require extraordinary skills that I just don't have the time or willingness to process and understand.
I think that's the reason why I love to watch Real Engineering/Practical Engineering channels on YouTube. I watch what seems like a "simple" task, such as pouring concrete, and then suddenly realize that it's actually not that easy. Or "How It's Made" - Chips? Easy, right? Well, no, lol!
pictures from internet mostly don't represent an accurate reality (in Indonesia is even more true than everywhere else). The other thing about Sulawesi is that the trasportation there is horrible and very time consuming. It's also not really touristic so better to bring your local friend with you.
I'm not that older than you, but I decided to do stuff that I want instead of doing stuff that are good for me.
> what makes you happy the most looking back?
Saving money, "retiring" at the age of 30, traveling for 2 years, entering a monastery, leaving the monastery, and then starting to think about work again for real, not just as a way to escape the system.
BTW. After 3.5 years of retirement, I finally grow up to start something myself, which is an idea that was hunting me since teen years.
my disclaimer was supposed to mean: I live here, I am interested in the current and past history of this country, I am involved, I have an Indonesian partner and Indonesian friends, but you have your right to seek the truth for yourself, which I strongly encourage you to do.
Modern history of Indonesia is also brutal, strange and very hard to grasp and accept. Just 6 months ago, a new generation choose a murderer, linked with previous coup as their new president because he was looking cute and post dancing videos on tiktok.
First of all, the 11ty documentation seems to be designed for people who already know what they are looking for. This is a typical bias from the people who create the documentation, as they are already familiar with the material.
I have a long history of improving extensive documentation for my past employers, and the first thing I always start with is a general question: Can I follow the stream of thoughts when reading the docs? Does it have a well-prepared welcoming page that can guide me to the information I need? (Sometimes you are just curious about release dates, and other times you might have forgotten the name of a plugin).
Documentation, as I understand it, should be a pleasing experience that takes you on a journey, allowing you to decide how deep you want to go.
The issue with 11ty's documentation is that every single page is overwhelming with technical details introduced right away. There is no foreplay, no gentle introduction—just straight into the details. I hate it; it makes me feel like it’s designed as a gatekeeper of knowledge (I've seen this in my previous companies too).
Designing documentation should start with simple ideas that gradually lead to more complex concepts (just like in coding, where we start with variables and functions before moving on to more complex structures like classes and logic). Simplified diagrams are also a very welcoming idea for a starter page.
To make it more 11ty-focused, their documentation is missing:
1. A welcoming page explaining what you are currently seeing and what you can expect.
2. A simple go-to project, rather than an overwhelming list of 30+ startup projects (why not just showcase a simple blog with one post?).
3. A "Set up your first project" page (I’ve chosen my first project, where should I go next?).
4. Instructions on how to extend your project (covering advanced topics like modules).
5. General organization—the whole page is cluttered with too many links, text blocks, paragraphs, and images.
6. Explanations of basic concepts (for example, it took me three days to understand why some pages have three or more syntaxes).
7. ... and more, but I just can't stand even looking at their docs