Have ever though of running your own ISP? Sound crazy but turn out quite do-able. Graham writes about technical part, cost analysis. Very cool even if we don’t do it. On the DevOps side, what problem we run into when scale to thousands servers? And more goodies, what Slack does to speed up Webpack. And writing an emulator. Hard core stuff. Sound fund. Have a good week everyone.
Wow, sound crazy but it’s actually very practical. This guide is focused on the very earliest stages of starting a WISP - determining feasibility up through connecting the first few customers. You may not start a real ISP, but knowing the process and the infrastructure is useful knowledge.
If you aren’t happy with JavaScript and are looking into switch to Elm, this is a great guide. Elm is pure functional, immutable, much faster, less concept to learn. It’s developed with emphasis on usability, performance, and robustness
Let learn Go by building an emulatior. How awesome that sound? Whole code is on Github, and suprisingly it isn’t that complex.
Carrier pigeons transport letters in plain sight. Any activity on the internet comes down to sending and receiving messages to and from a server. How come we can secure them? This is another attempt to explain HTTPS in simpler term.
Those who already ran Java application inside Docker have probably came across the problem of the JVM incorrectly detecting the available memory when running inside of the container. The JVM rather sees the available memory of the machine instead of the memory available only to the Docker container.
OpenAI scales their K8S cluster and share solution for problem that they run into in large scale deployment
Could you imagine just because you remove a function foo
, which has nothing to do with function bar
, yet suddenly bar
performan goes donw 10%. Let’s see why.
A simple hardware project to collect CO₂ with a device found for ~116USD on Amazon. A Go binary to run on a Raspberry PI, read data from the device via USB.
In Issue #31, we learn about ten thing the author wish he known about bash. Now, he follows up with, yes, ten more things
A series to understand how React work internally by diving into its code and understand its core concept by walking through code.
webpack is a brilliant tool for bundling frontend assets. But when project becomes large, it becomes slow. Slack teams improve this with measuring to identify bottle neck, parallelize, reduce the workload.
Keeping up with JavaScript frameworks can be a challenge. There are a lot of them, and seemingly another one every month. How do you know which ones might be right for your project?
Similar to the author, I like Elixir and cryptocurrencies so enjoy this quite a bit. let’s build a small crypto price checker. Then we will refactor it using FP concepts such as currying, function composing and pointfree functions
Yet another meltdown/spectre explanation from author of Envoy proxy
Rails made lots of huge change recently: webpack intergration, drop jQuery…What is strategy we can use to incrementail update Rails safely and effectively?
Kontena team describes how they do event sourcing with RabbitMQ tie all together among: APIs in Ruby, front-end in TypeScript and datastorage with Redis, MongoDB, PostgreSQL
This post will walk through an introductory example of creating an additive model for financial time-series data using Python and the Prophet forecasting package developed by Facebook.
Akita shares his personal note on running Rails on GKE, which can also apply to any Kubernetes cluster.
The pickle module implements serialization protocol, which provides an ability to save and later load Python objects using special binary format. It can also store references to functions and classes, as well as the state of class instances.
BetterDev Link
Every Monday