Menil Vukovic (@MenilVukovic) header
Menil Vukovic (@MenilVukovic) profile picture

Software Engineer turned CEO | The Terminal Thursday Newsletter (your favorite OSS newsletter)

Remote
Joined July 2012
Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)Photo by Menil Vukovic (@MenilVukovic)
Logic doesn't tell you what is true, but it can expose nonsense and dodgy thinking. "The Limits of Logic" at iai.tv/assets/videos/linked/…
9
5
Redis for jobs. Elasticsearch for search. A vector DB for embeddings. Kafka for events. Before you add the next box to the diagram, check what the Postgres you already run can do. 3 tools from TTT #014 🧵👇
1
24
Also on The Radar in Issue #014: 🧩 Extensions: pg_cron, PGMQ, ParadeDB, PostGIS 🛠️ Migrations and ops: pgroll, pgBackRest, PgHero, pgcli ⚙️ Platform: River, Graphile Worker, Neon, PgBouncer
1
11
Postgres first, exit criteria second. Kafka still wins as a log many consumers can replay, Elasticsearch as a search cluster, and a vector DB once one machine isn't enough. Full issue 👇 theterminalthursday.com/arch…
12
FFMPEG had one of the most valid crash outs in infosec history IMO. There's a huge elephant in the room when it comes to the fact that cybersecurity is extremely unbalanced. You have like 1,000 people pointing at problems for every 1 person fixing them. Vulnerability research is extremely important, but it's become somewhat of a marketing stunt. First with fuzzers, and now with LLMs. It's a lot of "look what my new toy can do" rather than earnest attempts at actually fixing security problem. What Google did to open source developers was especially egregious. They're a $3.6 trillion dollar company, who spent billions upon billions of dollars building a bot that points at problems really really fast, then they just dumped them all on a bunch of unpaid open source project maintainers to fix. Then because of Google's 90 day disclosure policy, the maintainers have 90 days to fix the issues. After 90 days, Google goes public with the issues, making their project look bad if the vulnerability is yet to be fixed, and also potentially harming users if it gets exploited. The 90 day policy was intended to give developers a reasonable amount of time to fix issues, while also applying some pressure with the threat of disclosure. Otherwise, you do get a bunch of goober ass vendors that will just ignore all security issues reported to them, then act completely surprised when their software gets hacked. But when you're a small team, non-profit, or a solo developer, and you have a trillion dollar company's AI just blasting you with infinite problems to fix (each coming with a 90 countdown & a threat), that becomes extremely untenable. They're essentially inadvertently blackmailing developers into becoming unpaid interns. Then on top of that, Google profits unimaginable amounts of money from the use of open source code. They use FFMPEG's code extensively across several highly-profitable products, meanwhile FFMPEG's developers work for free. There's no reason Google couldn't have donated money, engineers, AI tokens, or something towards fixing the problems. They can more than afford it. I don't think Google has any malicious intent at all, it's just that the whole incentive structure behind vulnerability research is completely whack. All the glory goes to people who find issues, not those who fix them, so there's not a whole lot of interest in helping with fixes. Some vulnerability researchers will submit fixes with their reports, but most don't. Honestly, in 2026 cybersecurity basically just feels like the equivalent of 50,000 people following the housecleaner around yelling "you missed a spot". Abysmally little effort has gone into anything outside of pointing out vulnerabilities.
FFMPEG was right all along and people gave them too much shit for it
132
767
52
7,619
373,731
Every request leaves logs, spans and metrics behind, so telemetry grows with traffic, not headcount. OpenTelemetry made the data portable. These 3 open-source backends let you run the storage yourself. TTT #013 🧵👇
1
45
Also on The Radar in Issue #013: 📊 Metrics and dashboards: Prometheus, Grafana, Perses, Netdata 📜 Logs, traces and pipelines: Loki, Jaeger, Vector, OpenTelemetry Collector 🚨 Uptime and alerting: Uptime Kuma, Gatus, Healthchecks, Keep
1
47
Instrument with OpenTelemetry, put a Collector in front, and the backend becomes a replaceable part. Running it yourself isn't free, so count the on-call hours too. Full issue 👇 theterminalthursday.com/arch…
23
Most of us use five git commands and treat the rest like a live wire. But rewriting history isn't as scary as it looks, and a new batch of tools makes rebasing, splitting and fixing up commits fast. 3 tools from TTT #012 🧵👇
1
22
Also on The Radar in Issue #012: 🪚 History surgery: git-absorb, git-filter-repo, git-branchless, git-town 🖥️ Git in your terminal: tig, gitui, diff-so-fancy, gh-dash 🤝 Hooks and releases: pre-commit, lefthook, git-cliff, gh
1
7
Rewrite history before you share it, not after. Git's reflog keeps old branch positions for at least 30 days by default, so a bad rebase is recoverable. Full issue 👇 theterminalthursday.com/arch…
12
Menil Vukovic retweeted
There must exists an app with PHP, deployed on Railway, with calls to cURL, with other services written in node that use Brotli compression running on a couple day old Linux, with their code self managed on GitLab They are having a hell of a week
182
326
39
8,103
167,886