Înapoi la articole →

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 46
  1. Every team that merges more than a handful of pull requests a day eventually hits the same failure: two pull requests are both green, both get merged, and the main branch goes red.

  2. Go has a garbage collector, so people assume they can’t leak memory.

  3. I have carried the same dotfiles from machine to machine for years.

  4. Google’s Open Knowledge Format sounded relevant to me immediately.

  5. This setup was inspired by Andrej Karpathy’s LLM Wiki, but my version is deliberately local and boring: Logseq journals as the inbox, source files as the archive, and compact pages as the durable layer.

  6. Most developers use AI models, but few extend them.

  7. In less than two years, coding agents went from novelty to daily driver.

  8. Under the Hood of AI

    A reader-friendly write-up of my WebExpo Prague 2026 talk.

  9. Most developers use AI models, but few extend them.

  10. In this talk, I’ll walk you through the common evolution of Terraform projects - from simple beginnings to complex, sprawling infrastructure definitions that become increasingly difficult to manage.

  11. Modern Go services generate telemetry (metrics, logs, traces) with instrumentation embedded directly in code.

  12. Tools table overview

    Last updated: March 2026 — Pricing and status verified against vendor websites.

  13. If you want to build text-based user interfaces in Go, Bubble Tea is a good option.

  14. The fun, functional, and stateful way to build terminal apps.

  15. On-Call Documentation

    Writing documentation effectively can be achieved by following a framework such as Diátaxis.

  16. Terraform by HashiCorp has become a leading tool for defining and provisioning infrastructure as code.

  17. On OpenTelemetry website, you can read the definition what is OpenTelemetry: OpenTelemetry is a collection of APIs, SDKs, and tools.

  18. OpenTelemetry as best way how to instrument your CICD pipeline.

  19. Disclaimer: I work for Pure Storage, which provides and sells flash storage for enterprise customers.

  20. Many articles have been written about this problem, but I keep seeing this problem coming back over and over again.

  21. Dagger is a programmable CI/CD engine that runs your pipelines in containers.

  22. Pipelines as Code

    “Pipelines as code” is not exactly a new concept, I heard about it a few years ago with the launch of Tecton.

  23. What is fuzzing?

  24. First, there is no such thing as a perfect dashboard.

  25. Thanks to Daria Grudzien for correction and comments.

  26. I know Grafana for a long time, but in my previous career, we used different tools as Datadog or other older tools.

  27. Github introduce new feature for repository that have special name as your nickname on Github.

  28. Compliance as Code

    I went through classical audits, where you fill tens of excel sheets and then consult with internal audit what and how to improve etc.

  29. JAMStack in 2019

  30. TinyGo

  31. Roster

    The roster is a term used for on-call planning, which describes a group of people who are part of a single on-call rotation.

  32. High Alert ratio

    One of the most challenging problems of on-call design is controlling the number of times engineers are paged during the night.

  33. Primary vs secondary

    When you have a primary and secondary on-call, several design decisions shape how effective the arrangement is.

  34. Daily vs Weekly

    My example uses weekly shifts, though that doesn’t mean I prefer them over daily shifts.

  35. In my example, I calculate how many non-working hours people spend on-call.

  36. Escalations & Metrics

    The primary and secondary layers are for resolving and managing incidents.

  37. Weekly oncall

    For an overview of on-call, I recommend reading Chapter 14 on On-call 1.

  38. OnCall Market

    An on-call market is a structured, team-managed process for swapping shifts.

  39. Reporting

    Over the years, I have found the following reports most valuable for On-Call owners to prepare: Number of incidents per week per team — useful for a regular weekly review.

  40. Incident process tooling

    You do not need an expensive incident platform to start.

  41. Daily Oncall Routine

    For daily on-call support, I recommend a few things.

  42. Postmortems

    Postmortems are how you make sure the same incident does not happen again.

  43. Summary

    Designing on-call is a tough process with constantly changing conditions.

  44. Running golang test on CircleCI is easy but if you need DIND (docker in docker) that is made by setup_remote_docker is all easy and you have something like this: version: 2 jobs: build: docker: - image: circleci/golang:1.13 environment: TEST_RESULTS:…

  45. New start in 2020

    I clean up old posts and restart this with a new look.