I used to be intrested in converting/saving websites to my own archives. The web is rotting away and saving a local copy is the easiest way to make sure I keep my references.
This, this ain't it chief. If you're looking for local saving, use firefox extensions. MarkDownload and SinglePage are both very good for backing up single web pages.
You might also want to know a few languages were you're sure to get a job, and right now, it seems that Ruby on Rails and PHP are some really safe bets, compared to Python.
Sure, Rust is _fun_ but there's little demand for it right now in the market.
Shadow has you uses their servers to put your stuff on.
Parsec is more like TeamViewer, VNC or AnyDesk in that you uses your own hardware to both connect to and from, albeit with a latency that's low enough to play games, and color fidelity that's good enough to do graphics. It is much valuable to businesses that wants to levrage their own powerful hardware but no be limited by teleworking employee.
To be frank, I've experienced those "scroll for 3 hours through short-length content" on youtube, especially with shorts.
You just kind of... zone out. Watch, click, watch, click, heart, watch... The action is repetitive, but the content isn't. I've definetly felt like I was on a Netflix binge, there's so little friction, time just flies.
I beg to differ. I have, in a vanilla firefox UI, about 100 tabs, in a single window.
I group them (loosely) by their themes, in the bar. It's... manageable.
I find the dev tools of firefox even better. The ability to see XHR request content/header/responses directly in the Javascript console has been invaluable to me. It annoys me that chrome's console does not have this. You can only see when a request is made, but you have to hop on the network tab to see the actual content.
What I personally do when stuff is straightforward is question how and why it is straightforward to me.
Usually, I realize it is because it's following whatever is my framework's way of doing things, or it is following the usual specs of the tools I use.
In this case, I make a conscious effort to dig up a link to a tutorial on a "standard project", and link it there, an example would be:
> This project is following a Classic Java Spring Architecture (-> links to the spring tutorial), with this and this modification...
You have to imagine that people happening upon your documentation might have a totally life experience than you, they may even be a lowly intern, thrown to your project as the sole maintainer of your code, with only school-taught experience.
This, this ain't it chief. If you're looking for local saving, use firefox extensions. MarkDownload and SinglePage are both very good for backing up single web pages.