One secret to becoming a great software engineer: read code
This is why betterdev have the
code to read section. Even skimming through code you can see different way prgrammer approach problem, organize project.
Then you can focus on specific function that you curious about. You do not have to read whole system. Eg, you want to see how people are doing microservice authentication. Then you
want to see how exactly the code that validate authentication data or password hashing.
Virtual Filesystems in Linux
Why we need them and how they work. They are the magic abstraction that makes the “everything is a file” philosophy of Linux possible.
Best practices for optimising video streams on the web
When it comes to video, we just use Youtube similar services and call it a day. They hide all the detail and remove fun challenge.
Setting up video streaming is fairly straightforward today, and no longer requires any specialised hardware – any HTTP server can serve streaming content.
Blazingly fast parsing, part 2: lazy parsing
V8 is fast because many talented developer pour years into it. We all can learn from it.
We rolled out Envoy at Geckoboard
Gecokoboard shares how envoy helps them to stop worrying about our gRPC traffic. This gives you some hintsight if you are looking into Envoy.
Code to read
An Emacs-like text editor written in Ruby
An almost complete tetris in ClojureScript
Reddit clone in Rust
a large-scale CRDT set implementation for timestamped event
Want to see how JS fix
quickly mock out end points, setup delays
Prevents you from committing secrets and credentials into git repositories
Istio and App Mesh progressive delivery Kubernetes operator
automates and exposes complex infrastructure tasks to other teams and service
An easy to use and powerful chaos engineering experiment toolkit
That's it for this round, have a great day! If you like this newsletter, please tell the world, or
tweet about this