Alex Rotar

Alex Rotar

Build in public. Scaling data workflows.

About

Just a dev trying to make complex data actually usable. Building ChangePoints OS: 50+ Case Studies for ESG Leads. Refined WeeklyMark: Local-first Python parsing for Obsidian users. I believe the future of B2B is data-dense and local-first. Here to support other makers and ship products that solve real boredom. Next Milestone: 500+ ESG consultants using the Vault.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Forums

I dogfooded my own code intelligence tool and found 4 bugs I'd shipped

Building Sverklo (launching tomorrow on PH), I ran a structured dogfood protocol used the tool on its own codebase to find real bugs before users did.                                                                                  

                                                                                                                                                                                                                                            

  Found 4 integration-level bugs that unit tests missed:                                                                                                                                                                                                                                                                                                                                                                                  

  1. Impact analysis silently dropped repeat call sites the worst possible failure for a refactor-safety

  2. Reference search returned 48 substring matches, drowning the 5 real

  3. Lookup returned "No results" on valid queries instead of explaining why    

  4. Parser off-by-one skipped every function after the first in multi-function                                                                                                                                                                                                                                             

  5. All fixed, regression-tested, and documented in a full unedited session log

Is traditional Technical SEO dead, or just evolving into "Agentic UX"?

I've been researching how autonomous agents (Claude, Google Jarvis) traverse websites, and I'm noticing a massive gap. Sites that score 100 on Google Lighthouse are literally crashing AI agents because of DOM bloat and missing ARIA semantics.

We just launched a tool today to physically measure this "Agentic Friction," but I'm curious what the community thinks: Should front-end devs be designing for human UI, or should they be stripping down their DOMs so AI agents can actually read and cite them? Where is the balance?

I built a Telegram bot because I keep forgetting everything

You know that moment when you think "I need to remember this" but opening a reminder app, tapping through date pickers, and saving it takes longer than the thought itself?

Yeah. I built something for that mostly because I keep forgetting everything myself. I even forgot to use the reminder apps I already had.

Just open Telegram and type:

- "remind me tomorrow at 9 go to shop"

View more