@yevhen Я на тому тижні в продакшен коді знайшов, що у нас дві автономні паралельні системи логіну ). Просто на якийсь момент 4 місяці тому Агент форканув систему лоігіну, і далі ми 4 місяці автоматично робили фікси і туди і туди. Агент каже що не хотів робити брейкінг чеіндж.
I still amused how extensible @badlogicgames pi coding agent is. Built extension for tool approvals to make pi more appealing for non-techies and DevOps people. Post: https://t.co/QatM6hFTd1
Package: https://t.co/QRUb169hRq
Hey @openclaw (@openclaw / Clawdbot) people! 🦀
I've run meticulous AI security review (Codex 5.2 High) on Clawdbot's codebase (latest 2026.1.24 release) across 5 surface attack vectors, and it found 37 potential vulnerabilities related to misconfiguration (incl top 10 reported yesterday).
You can run it instantly with uv or with single-liner shell command (or just from source). Includes detailed checklist report with mitigation recommendations.
Check link in reply comment
AI is causing a new dev pattern: I heard this yesterday: I show my stakeholders a demo, we generate 10-12 exciting ideas, and by end of next day, 80% are already in production. Then I let them know: 'It's live — what do you think?"
People who fret about AI replacing dev jobs are missing the point. When you can create value 10x or even 100x more quickly, you get more headcount, not less.
Another example: I paired with someone two days ago who made a circa-2005 Google Analytics clone in less than 30 minutes. (One JavaScript snippet, sending events to Google Cloud Run, PubSub, and BigQuery.). It will eventually ingest 20MM events/month, way above the 1MM Google Analytics limit. (We wrote the reporting engine in Python Streamlit today.)
The longest part of the process? Getting permission to create PubSub subscribers. Not coding.
These types of obstacles are what @steve_yegge and I called "barbed wire" in our Vibe Coding book. But I never saw as vividly as how critical it is to have someone from infosec or admin rights on the team — all your wildest dreams are blocked by waiting to get access rights.
Another heartbreaking form of barbed wire? People stuck in protracted sprint planning processes, endless backlog grooming meetings about what features should work on next and which need to be pushed into next quarter...
The new bottlenecks are organizational, not technical — let's go fix them!