Very simplified about the AI revolution happening now. We are only at its very beginning. Next, automation and integration among different AIs will increase, leading to more and more complex tasks. There are still many problems, such as - training a truly large model, and making it accessible for general use is still very expensive and very energy-consuming. It is still not very clear what to do with regulations, because it works both ways, making it significantly easier to assemble some kind of bomb at home.

SRE Simplified : Error Budget concept. The concept of Error Budget is useful for setting up alerts of different severity. This video explains in extremely simplified manner how it works.

The next issue of SRE Simplified is about Service Level Agreement. Service Level Agreement is an agreement between service supplier and a customer about what the target quality of the service is and what are the consequences if the promise is broken. But the challenge here is to eastablish monitoring and alerting. This video provides very simplified example of an SLA for the company that produces apples. Document Title

What are the SRE concepts, like Service Level Agreement and Reliability? The challenge is to explain it in simplified manner, without deep discussions on different monitoring strategies. In this first video I tried to just to scratch the surface.

WireGuard is a relatively new protocol. It claims to be greatly simplified and faster comparing to alternatives, it uses UDP as primary transport and encapsulates encrypted traffic from IP layer. Let's investigate if it's true! Some differences help to stand out of other VPN solutions: Routing as a part of Peer configuration QR code for simplified configuration using camera on mobile devices. iPhone, iPad and other things, you'll love it!

When it comes to the topic how Prometheus and Alertmanager work together and how to restrict alert notification to fire only on working hours, typicall solution is to apply workaround to avaluated alert rule expession like this and ON() (hour() < 19 and hour() > 8) and ON() (day_of_week() > 0 and day_of_week() < 6) The full example of such rule is the following - alert: DummyWorkhoursAlert expr: 1 and ON() (hour() < 19 and hour() > 8) and ON() (day_of_week() > 0 and day_of_week() < 6) for: 5m annotations: identifier: "{{ $labels.

I use org-mode extensively with org-roam for keeping my knowledge and journals together and working as my brain dump destination. This blog serves kinda the same purpose, so why not to combine these things under Emacs umbrella? Blogging from Emacs boils down to two options. TLDR; Hugo can render org file natively, but support of features is quite limited, or use org as source that rendered to markdown. The latter brings issues of content syncing from origin to end result.

In case ruby can’t find OpenSSL 3 headers, use this way. brew install ruby-install ruby-install ruby 3.1.4 -- --with-openssl-dir=$(brew --prefix openssl)

How to provision CloudFlare tunnel using Terraform CloudFlare Tunnel can be useful to use reliable alternative to ngrok when you need to expose your application running locally to the outside world. The following example exposes my application locally running on port 3000 to the Internet on the hostname https://app.prokopov.me Prerequisites Terraform CloudFlare module v4 CloudFlare API key with Account:Tunnel permissions. Locally installed CloudFlare CLI utility cloudflared https://developers.cloudflare.com/cloudflare-one/connections/connect-apps/install-and-setup/installation/ Application running locally on port 3000 How does it work?

It is in general very good idea to manage infra configuration as a code. Unfortunately, Mirkotik terrafrom support is basic, as OSS driven. Nevertheless, I appreciate author for effors. Here is an example how to use it with Hashicorp Vault. Commands export VAULT_ADDR=http://vault_address:8200 export VAULT_TOKEN=<token> terraform init terraform plan Example main.tf provider "vault" {} data "vault_generic_secret" "main" { path = "common/mikrotik/nexus-home" } provider "mikrotik" { host = data.vault_generic_secret.main.data["address"] # Or set MIKROTIK_HOST environment variable username = data.