For example if you search "Nothing Can Stop Google. DuckDuckGo Is Trying Anyways site:medium.com", and set a custom date range to sometime last year. You'll see results which state this blog post was posted in 2018-October-31 for example, or which every date you prefer because I assume they just fuzzily fit the post date -into- that range. You can make google tell you this blog post is 2+ years old.

The Google.com I found useful in the early 00's even had document qualifiers so I could search for strings, but filter to just PDF's, or HTML, or JPG's. Now I have to pay for these features via a Google App-Engine private search instance. It just feels like having somebody spit in your face. When features were free, but they quietly became pay-to-play without zero warning.

[1] https://bynd.com/news-ideas/google-advanced-search-comprehen...

Support is not free. If you want software updates, security patches, bug fixes, or somebody to call when shit hits the fan you pay Red Hat.

If not CentOS/Fedora use the same source codes

The resources I'm linking are supplementary to the above, and you'll likely encounter them in the wild. But they'll help you build a base of knowledge, and give you terminology to search for, and work with.

- What Every Programmer should know about memory: https://people.freebsd.org/~lstewart/articles/cpumemory.pdf

- Cache Obviousness: https://www.youtube.com/watch?v=bY8f4DSkQ6M (the suggestions, and terminology are important)

- Parallelism: (This is a good primer, there are a lot of complementary posts linked on the site) https://preshing.com/20120612/an-introduction-to-lock-free-p... https://preshing.com/20120913/acquire-and-release-semantics/

- If you plan on working with linux these is an excellent reference: http://man7.org/linux/man-pages/dir_section_2.html remember there is no magic in Linux, everything eventually has to go through a system call. So if you learn the systemcalls, you can can learn how things work :)

- Fog's optimization resources are awesome: https://www.agner.org/optimize/

- MIT courseware: https://www.youtube.com/watch?v=ytpJdnlu9ug&list=PLUl4u3cNGP... https://www.youtube.com/watch?v=HtSuA80QTyo&list=PLUl4u3cNGP...

- This cheat sheet is worth committing to memory: http://www.bigocheatsheet.com/ the reference links are also great for building up knowledge

- I highly recommend CMU DB open course ware: (intro) https://www.youtube.com/watch?v=vyVGm_2iFwU&list=PLSE8ODhjZX... (advanced) https://www.youtube.com/watch?v=poEfLYH9W2M&list=PLSE8ODhjZX...

This should give you a good primer on Concurrency, and DB's. For networking likely a basic TLA+ certification class will be 99% review, but for the things it isn't will offer great insight.

C89 only requires that static values be initialized.

A modern C standard (section: 6.7.8(10)) requires static values be initialized, but what the value is initialized too be _technically_ indeterminate.

There is the guide line given that integers must be zero, and pointers be NULL. But if a static storage class isn't consisting of purely integers, pointers, or (fixed sized) structures, arrays, and unions who's elements can recursively reduced to integers or pointers. Then the standard says the initialized value is indeterminate.

While relatively straightforward, there is a few gotcha's.

I taught myself to touch type at about ~80WPM with my thumbs, and how I have this bad of habit of typing a full google search query, and just staring my phone for 90seconds until all the text magically fills in and my phone shakes with haptic feed back that should've occurred nearly 2 minutes ago.

It is such a cheap experience I had to turn haptic feedback off because its not even remotely synced to touch inputs.

This was mostly added during NT6.0 era, which occured ~12 years ago. VISTA was the first OS using NT6.0 and VISTA was VERY much not in vogue ~12 years ago. In fact it was avoided like a plague as of 2008 (unless you were using 64bit, and had >=4GiB of RAM)

So many were using Windows-XP 32bit, or the NT5.2 kernel. Even those with >=4GiB of RAM were on Windows-XP 64bit, as VISTA had a ton of driver problems.

NT6.0 didn't catch until Windows7 and NT6.1

It is nice to have disk IO be the limiting factor on decompression even when you are using NVMe drives.

[1] https://github.com/valarauca/car

for those you who don't remember Xenix was Microsoft's UNIX that it marketted prior to releasing DOS. Originally the idea was Xenix was the multi-user OS, DOS was the single user.

    get their office suite to LibreOffice

That being said ownership is rather hard, but liberal usage of `.clone()` can get you pretty far.

Generally speaking it is exceptionally rare for a star to point directly at us. This is to an acurracy of millionth's of a degree, as the straight line travel across interstellar space is massive. So getting hit with a GRB is like winning the interstallar lottery.

Secondly, if you cannot control it, or influence it. Worrying about it is just fantasizing. Humans tend to assume overly dramatic events are more likely then they actually are.

    I think if more people took the time to understand
    them and practice writing them (when appropriate),
    they wouldn't have such a stigma.

When people move away from this model there are a lot opportunities to practice regexes. I've noticed this my own workflow when working Java-centric languages (who's IDE's often have poor regex integration).

2. Assets are bundled via the zip like mechanism, and individual "zone maps" are separated by hard loading screens. If you travel from 1 continent to another in WoW you get a had loading screen as assets are unloaded, and reloaded.

3. Which continent you log into is the only one you _need_ data for, so as you log in the client can prioritize certain assets higher then others.

4. Blizzard/Activision have a lot of experience with this. In 2008 blizzard had 10mil + players downloading 4GiB+ patches within 24hours so they've had a while to tune and make adjustments as this is part of their core customer experience.

5. Large publishers don't general optimize for this, because the people who whine about it largely already gave you their money and aren't likely to refund/return (in some avenues it is impossible).

Used an existing box fan. I had to buy duct tape ($3) and the filter I used one rated for 0.1micron pollen and viruses cost me $17 (rounding up after tax). I cut up a plastic safeway bag to make the seal around it. Seeing as most smoke particles is around 2.5-.5 micron I figured it'd be okay.

I threw this together at about 7am on Saturday after I woke up coughing my lungs out at 6am (I live in the bay area). Just a quick trip down the the Homeless Despot to get the parts and throw it together.

All things consider it works great. The air in my apartment is easy to breath, but if I leave without a respirator (even today) I cough uncontrollably.

---

As of Tuesday evening it has been running for 4 days straight (no overheating). And has started to become noticeably brown. Needless to say I'm thankful for it.

The maker has some data that compares it to Fentanyl [1]. Their numbering states that is closer to 100x, and crosses the blood brain barrier in around 6 minutes.

[1] http://www.acelrx.com/technology/publications/arx-04/MHSRS%2... here

Or at least I've encountered this in my career.

Division of tasks, and specialization naturally trend to hierarchical organization for the same reason divide and conquer algorithms are so efficient. Separation of concerns is powerful.

There is much different of 5-6 shoemakers picking the same person to handle their finances so they can focus on making shoes. But, how many shoe makers can offload their finances until you have a bank?

The fundamental limit of clock speed is power draw. As clocks increase the wattage ~ frequency relation goes from

     frequency = Constant * Power Draw

     frequency = Power Draw * Power Draw