I Was Worried Networking Would Be Complicated Phew

Content What working on a git repo by yourself feels like:

Content LEFT EXIT 12 Spendina 400 to upgrade my hardware Installing Linux on mV 10 yo PC and calling it a day Me, a non programmer

Content Developers when they find a nice piece of code on GitHub Our code Devs

Content 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 include stdio.h include stdbool.h int main(int argc, char argv) printf("Which is greater, C or C? nAnswer: "); int c 1; bool cIsGreater ( c; if (cIsGreater) printf("C); else printf("C); return 0; PROBLEMS OUTPUT TERMINAL Which is greater, C or C? Answer: C DEBUG CONSOLE

Content - ballbase 72 points 1 day ago What does sacrifice child mean in this context? permalink source embed save save-RES report give award reply hide child comments -J Schnickatavick 234 points 1 day ago (last edited 1 day ago) I don't know the term "sacrifice", but generally killing a child means that a parent process needs to terminate a secondary (child) process that it started. I would assume based on context that a sacrifice is just ending a child process to save memory? Regardless, threading has some of the most messed up terminology for seemingly no reason. It's the only place where "killing orphans" or "zombie children" are normal terms permalink source embed save save-Res parent report give award reply hide child comments - TechCubeTetrabyte us 61 points 1 day ago Zombie children? Like, unaccounted for by the OS? permalink source embed save save-RES parent report give award reply hide child comments - Schnickatavick 128 points 1 day ago - It's a child process that finished its task and closed, but the parent process hasn't acknowledged it yet. It leaves it in this awkward state where it's terminated (dead) but it still has to hang around in memory (like a zombie) until the parent process can receive the child's "return" values, which let's the OS wipe it from memory, which is called reaping. Which is another messed up term, the OS is literally a "reaper" for dead processes? Who named this stuff? permalink source embed save saveRES parent report give award reply hide child comments - TerrorBite 55 points 1 day ago - The child itself has already died or been killed at that point; what isn't released yet is the child's entry in the PID table, as the return code (which the parent needs to read) needs to be stored somewhere. So the only thing the zombie process is taking up at that point, is a PID number and a few kB at most of metadata in the kernel. You can't kill a zombie process, because it's already dead. The only way to get rid of it is to kill the lazy parent; the zombie will then be re-parented to init, which will clean it up immediately. Dermalink source embed unsave parent report give award reply hide child comments - Schnickatavick 69 points 1 day ago The only way to get rid of it is to kill the lazy parent The child itself has already died or been killed the zombie will then be re-parented See! What's with this phrasing?! But yeah, that's exactly right Dermalink source embed unsave parent report oive award rediv nice child comments

Content Looking to hire a Jr Data Scientist: - 15 years Python - 30 years SQL - 20 years AWS - 15 years Spark - 15 years Terraform - Core contributor to assembly code base - Team player - Should have some sort of martial arts experience, whether Ninja, Jujitsu, or Karate. All 3 is preferred. - Knows SQL, NoSQL, NewSQL and all future flavors of SQL - Project Management experience - Strong experience with Keras, TensorFlow, Sklearn, XGBoost and preferably has written their own ML library from scratch. - Should have published at least 2 top level academic papers preferably focused around a Convolutional Recurrent Back-propagating Neural Network - Open source contributor at least 5 projects. - Experience leading teams of 10,000 people or more - Managed CICD pipeline for an application with at least 2 billion daily users - Should have at least 1 PhD, 5 is preferred. Yes, we have ping pong tables and an open floor plan and lots of salty snacks in the breakroom. Organic Kombucha on tap. The interviews will consist of a 5 day process of whiteboarding algorithms from scratch followed by writing your own compiler and a coding exam will be taken at random from the 20 most popular programming languages.