That's just basically looking up the answer. ... i will not learn anything from it.
Looking up the answer is the way to do it. You're of course supposed to pay at some attention instead of copy-pasting without using your brains. As you keep doing things, you'll develop a rough idea of how things are done.
Even if i find it (which is unlikely without asking an llm)
But i don't know how i did it, and i couldn't recreate it by myself.
You mean building the thing without any reference? Except for the most basics, you're not supposed to memorize everything by the smallest details. Imagine asking a lawyer to know the details of every single law off the top of their head.
Well yeah. You find yourself some simple project and try to build it. When you don't know how to do something, you look it up.
Like, make a command line clock, for example. Figure out how to get the current time, and then how to print it. And after that how to make it print the time once a second.
Edit: probably the most important skill in programming is breaking the problem into smaller pieces that you can then figure out. With experience, getting stuck like this becomes much less of a problem.
I don't think it's a linear progression where one ingredient is a "step." I don't really use fresh pasta, but I make the food myself instead of buying a canned sauce.
Hey cool, thanks for the recommendation, I added CT4MGM and a couple other fonts to my collection. I have already found fonts that do deranged stuff, like defining offsets outside the buffer they're supposed to be in.
Right now I'm not creating the sounds myself, but rather using a library for the purpose. I'm intending to replace it with my own implementation (or a suitable alternative, if one exists) later, if I just have the time. The biggest remaining blocker for release is doing exactly that for the midi sequencer, because the current one doesn't let me do seeking.
I have other related projects planned as well, like a soundfont compiler that builds a font from "source code" that consists of loose samples and text files that define the instruments. I promised myself to not start anything until this one is out, though.
The number shown is how many posts or comments your instance is aware of. If your number is smaller than the real one, it means that there's content that doesn't exist on your instance.
The missing content is either:
Old: The account is like 3 or 4 years older tham your instance. Old content doesn't get federated unless someone deliberately asks for it.
Posted in communities that no one at your instance has subscribed to them yet. This stuff also doesn't get auto-federated.
I was vaguely aware that some ancient architectures had weird byte widths, but I did not know about this. Pretty interesting.
This paper cannot succeed without mentioning the PDP-10 (though noting that PDP-11 has 8-bit bytes), and the fact that some DSPs have 24-bit or 32-bit words treated as "bytes." These architectures made sense in their era, where word sizes varied and the notion of a byte wasn’t standardized. Today, nearly every general-purpose and embedded system adheres to the 8-bit byte model. The question isn’t whether there are still architectures where bytes aren’t 8-bits (there are!) but whether these care about modern C++... and whether modern C++ cares about them.
The file is named Cargo.toml. Whatever dependencies you add to there are automatically downloaded by Cargo. You can manage them with cargo add and cargo remove.
cargo install is not the same thing. That installs binaries. I last installed cargo-release to automate the annoying part of managing git tags and crate version number.
Looking up the answer is the way to do it. You're of course supposed to pay at some attention instead of copy-pasting without using your brains. As you keep doing things, you'll develop a rough idea of how things are done.
You mean building the thing without any reference? Except for the most basics, you're not supposed to memorize everything by the smallest details. Imagine asking a lawyer to know the details of every single law off the top of their head.
Seriously, go build that clock.