It definitely is and I wouldn't take this approach mid-way for a project with multiple users and contributors. But it works for my little projects that desperately need me to be the user more than the developer. An example would be a REST API with a few endpoints where the database operations are handled directly in the route handlers uniquely for that specific task.
Yes, the better solution is probably not on the programming layer :D I was still interested in a specific term to this approach to look up to what extent somebody can drive this.
I don't really have a perception of people that like to listen to metal, because that's a huge amount of different people. This definitely did change. I'm not sure, if it was due to my younger age or the strength of genre stereotypes at the end of the 2000s, but at that time I didn't even realize how much of the music I listened to was metal. I associated metal more with the stereotyped metal heads than the actual music.
If we're talking about programming language guides in particular, following a guided introduction to a new language was helpful to me, when I was introduced to new concepts and perspectives. And Rust is the best example in my case. Personally I probably would've struggled more and longer in practice without learning about ownership, lifetimes and borrowing in theory first, because it's an essential part of almost anything, even strings, and yet it's not too difficult to understand in theory.
But at the end of the day, you can start rawdogging it and use the Rust book or any other guide, when you're facing a roadblock. If you do so, please share your experience.
It is a problem worth solving. Terrorism is a problem that needs solving and killing all people on earth is a solution. The next question is whether or not it is an appropriate solution to the problem.
If we're talking about people who simply make video content about software development, then the biggest impact I see is a bigger reach for any tool that needs to be seen in action or simply sounds too strange on paper. In recent years HTMX was probably affected the most.
I see that a lot of people boil it down to tutorials, but there is so much more content about software development.
It has a Linux-based OS that you can SSH. You can install community-maintained stuff with Toltec. The Awesome Remarkable is a great overview.
However for 3rd-Party software and more general features, even with the openness, it doesn't come close to Onyx. In general, the remarkable is more focused on distraction-free e-reader and note-taking capabilities. And honestly even being part of this target audience, if it wasn't for the affordable replacement offer, I probably would've rather looked into other e-ink devices.
It took a bath in ice tea for a few hours and it suffered even more when I stupidly connected it to the PC before I saw the wet folio and bag. I probably would've looked into other alternatives, too, if I didn't receive a replacement offer for ~130€. I love it, but it does have many faults, that for some people may be unacceptable for the price. But that seems to be the current state of e-ink tech in general.
I bought the Remarkable 2 about two years ago, but since I had to get a replacement, I guess it counts. I love the e-paper's magical feeling in general. Remarkable in particular amazes me with the openness e.g. giving me SSH access to the Linux-based system. I wish they'd focus on customization, tinkering and stability, but unfortunately that doesn't seem to be the case.
I don't ignore, re-gift or discard any gifts, at least not immediately. But it's extremely rare to satisfy me with a gift. It only happens when they know exactly what I'd have purchased myself in near future or if the person behind the gift means so much to me. Other than that, I prefer to not receive any gifts at all.
I use mostly Rust. I meant "extending" in terms of features.