Now I have to figure out how to combine the two, and of course whatever further optimizations I can figure out along the hard way. My first idea is implementing a more pure C++ of capturing the gnuplot html5 canvas output instead of just emitting the system call to stdout. With the html code saved in the data structure proper parsing/adjustments could be made before output. I should also want charts with the month ago and year ago yield curves superimposed as is often done traditional newspaper yield curve charts.
Too bad my multithreaded BST and BST/AVL tests were more than a month ago.
Is there any chance of having something similar to this, such as a monthly showcase for people to gather and post their projects? It might be cool if random people could also put up prizes, but I didn’t do this for a reward. I realized that I’m always doing things by myself and keeping it to myself, so I figured it could benefit myself and the community to share.
In any event, I finally got the fluid for my transmission replacement project and got the car back on the road. I updated the blog with the last few details.
So, here’s where i got to so far. I haven’t spent much time on it lately due to other commitments but fuck it - figured i’d upload the state so far.
I’m trying to simplify a lot down to the level that is relevant for home (probably home-lab)/small networks so some of it may not be “100% complete” in terms of the technical stuff (but it should at least not be misleading) and I’m aware of that.
But at a minimum i think a (very) basic primer on network layers is also required to understand diagnostic terminology when chatting networks with others. Hence the current content before i even got to subnets.
It’s also not fully fleshed out, this is a text export from what i plan to make an epub or something. So the formatting is all fucked up compared to what would be in the epub (i’m using iBooks author to write it at the moment).
But feedback regarding the scope, brevity vs. complexity, etc. welcome. This stuff is pretty difficult to summarise without losing so much detail as to be irrelevant. I did want to include a very, very brief overview of the layers as they’re somewhat crucial to understanding how the network stack works and “layer 1” or “layer 2” etc. is frequently used to describe problems by others you may have to liaise with when working with others to diagnose a problem (especially in the workplace).
As mentioned in the doc - my aim isn’t for this to be used for certification or whatever. But more as a basic troubleshooting cheat sheet for those not specifically trained as a network admin.