SmartNIC by Ciro Santilli 37 Updated 2025-07-16
A network interface controller that does more than just the base OSI model protocols, notably in a programmable way.
Video 1.
Hyperscalers Lead The Way To The Future With SmartNICs by The Next Platform (2019)
Source.
Associated article: www.nextplatform.com/2019/10/31/hypercalers-lead-the-way-to-the-future-with-smartnics/ mentions that:
Google is widely believed to be working on its own design.
Cisco by Ciro Santilli 37 Updated 2025-07-16
Video 1.
Nerds 2.0.1 excerpt about Cisco (1998)
Source.
Nothing phenomenally new on the early days to add on top of Video "Nerds 2.0.1 excerpt about Cisco (1998)", but a few new good points:
Sandy Lerner by Ciro Santilli 37 Updated 2025-07-16
This chick is hardcore.
Server (computing) by Ciro Santilli 37 Updated 2025-07-16
Video 1.
Unpacking 200 servers by Play with Junk (2021)
Source.
Video 2.
Visiting Hetzner in Falkenstein by der8auer (2022)
Source.
As per stackoverflow.com/a/52351480/895245 our standard test setup is:
while true; do
  resp=$"$(date): hello\n"
  len="$(printf '%s' "$resp" | wc -c)"
  printf "HTTP/1.1 200 OK\r\nContent-Length: $len\r\n\r\n${resp}\n" | nc -Nl 8000
done
  • there can be more than one node per server.
  • there can be more than one CPU per node
E.g.:
Blade server by Ciro Santilli 37 Updated 2025-07-16
Figure 1. Source. Good image from Wikimedia Commons. In this one we can see how the blades are put vertically, and you get several of them per horizontal rack space, instead of a tipical single rack server going all the way horizontally.
Video 1.
HP Blade Server by Brian Kirsch (2013)
Source.
In the video we can see that it contains RAM, disk storage, we are told about two CPUs, and networking interfaces, so it is a complete computer on its own. He also explains that unlike typical rack servers, each blade unit does not have its own coolers and power supply related hardware, which goes instead on the chassis.
Computer science by Ciro Santilli 37 Updated 2025-07-16
A branch of mathematics that attempts to prove stuff about computers.
Unfortunately, all software engineers already know the answer to the useful theorems though (except perhaps notably for cryptography), e.g. all programmers obviously know that iehter P != NP or that this is unprovable or some other "for all practical purposes practice P != NP", even though they don't have proof.
And 99% of their time, software engineers are not dealing with mathematically formulatable problems anyways, which is sad.
The only useful "computer science" subset every programmer ever needs to know is:
Funnily, due to the formalization of mathematics, mathematics can be seen as a branch of computer science, just like computer science can be seen as a branch of Mathematics!

Pinned article: Introduction to the OurBigBook Project

Welcome to the OurBigBook Project! Our goal is to create the perfect publishing platform for STEM subjects, and get university-level students to write the best free STEM tutorials ever.
Everyone is welcome to create an account and play with the site: ourbigbook.com/go/register. We belive that students themselves can write amazing tutorials, but teachers are welcome too. You can write about anything you want, it doesn't have to be STEM or even educational. Silly test content is very welcome and you won't be penalized in any way. Just keep it legal!
We have two killer features:
  1. topics: topics group articles by different users with the same title, e.g. here is the topic for the "Fundamental Theorem of Calculus" ourbigbook.com/go/topic/fundamental-theorem-of-calculus
    Articles of different users are sorted by upvote within each article page. This feature is a bit like:
    • a Wikipedia where each user can have their own version of each article
    • a Q&A website like Stack Overflow, where multiple people can give their views on a given topic, and the best ones are sorted by upvote. Except you don't need to wait for someone to ask first, and any topic goes, no matter how narrow or broad
    This feature makes it possible for readers to find better explanations of any topic created by other writers. And it allows writers to create an explanation in a place that readers might actually find it.
    Figure 1.
    Screenshot of the "Derivative" topic page
    . View it live at: ourbigbook.com/go/topic/derivative
  2. local editing: you can store all your personal knowledge base content locally in a plaintext markup format that can be edited locally and published either:
    This way you can be sure that even if OurBigBook.com were to go down one day (which we have no plans to do as it is quite cheap to host!), your content will still be perfectly readable as a static site.
    Figure 2.
    You can publish local OurBigBook lightweight markup files to either https://OurBigBook.com or as a static website
    .
    Figure 3.
    Visual Studio Code extension installation
    .
    Figure 4.
    Visual Studio Code extension tree navigation
    .
    Figure 5.
    Web editor
    . You can also edit articles on the Web editor without installing anything locally.
    Video 3.
    Edit locally and publish demo
    . Source. This shows editing OurBigBook Markup and publishing it using the Visual Studio Code extension.
    Video 4.
    OurBigBook Visual Studio Code extension editing and navigation demo
    . Source.
  3. https://raw.githubusercontent.com/ourbigbook/ourbigbook-media/master/feature/x/hilbert-space-arrow.png
  4. Infinitely deep tables of contents:
    Figure 6.
    Dynamic article tree with infinitely deep table of contents
    .
    Descendant pages can also show up as toplevel e.g.: ourbigbook.com/cirosantilli/chordate-subclade
All our software is open source and hosted at: github.com/ourbigbook/ourbigbook
Further documentation can be found at: docs.ourbigbook.com
Feel free to reach our to us for any help or suggestions: docs.ourbigbook.com/#contact