If you want a really great learning aid, search for "Island of Yap Blockchain" and read any of the million articles about it.
234 karma · joined February 14, 2018
If you want a really great learning aid, search for "Island of Yap Blockchain" and read any of the million articles about it.
You need to add the EI.cfg and PID.cfg [0] files to the installer medium before booting it. Once you have those files present with the correct syntax, it will install the version you want, but I can't imagine a non-tech person being able to figure this out on his own.
[0] https://learn.microsoft.com/en-us/windows-hardware/manufactu...
I pay for the All Products Pack purely out of convenience - If I wanted to spend a ton of time tweaking my IDE, I'd go back to Emacs!
I know not everybody uses Linux (or loves systemd as much as I do) but it's a great solution if you already use systemd.
[0] https://www.redhat.com/sysadmin/introduction-path-units
[1] https://www.freedesktop.org/software/systemd/man/systemd.pat...
I remember a whole bunch of light bulb moments when I showed other developers the "big picture". It's an awesome technique when you're forced to work on spaghetti!
That being said, I hadn't heard of rclone - thanks for mentioning it, it looks amazing. I'll definitely be trying this out for my use cases...
[1] http://www.gnu.org/software/parallel/man.html#example-parall...
It's obviously not going to teach you the ins and outs of modern C development, but it's the best introduction to the language out there IMHO.
With my old log merging program, you had to supply a regex with groups for the different timezone components and optionally a UTC offset. That worked really well but was a pain to set up. Typically I was using it to look at the same format of files all the time though, so in practice it wasn't that bad.
I'm not really a C/C++ person but maybe I'll try and hack on lnav a bit and see if I can figure out how to add timezone support.
Specifically how they are untarring each container layer and creating a chroot jail to run commands inside is fairly self-contained and interesting.
Creating tools to produce realistic test data and also using fuzzing tools can be just as good and sometimes even better than using actual production data.
There are definitely cases where the official docs (or RFCs) are practically incomprehensible to a newcomer, but I usually will try and come back to them quickly after getting a foothold using a blog post or YouTube video.
I find that even with the best technical writeups, there are often things applicable to MY use case that may not have been relevant to the author. The official docs (or sometimes the source) is the best place to find out about those.
You also have the terminal, so you're free to `cd`, `find`, `locate`, etc...
For example, if I take a couple of Canadian Maple Leaf coins to any local "We Buy Gold" shop, I'll get very close to spot price in cash with no questions asked. The fact that they clearly came from the Canadian mint tells the dealer that they can trust they are indeed made of 99.99 pure gold.
If I come to the same dealer with a bar of gold I melted and poured myself, they may need to send it out to a lab for analysis to determine the purity, actual weight, if I'm ripping them off, etc.
Both are excellent reads, but I'd definitely agree IaaSL is far more approachable and a better use of your time.