Bata @zygotich

Mobile product engineer Joined December 2025

Tweets

5
Followers

3
Following

126
Likes

13

Ábel Énekes @enekes_abel

6 days ago

Love this! I wrote & drew something very similar back in May: agent guidance on top, executable checks in the middle, review and monitoring at the bottom, all protecting the requirements. Back then ppl called it AI slop - kinda discouraged me from writing. Seeing you land in the same place gives me some peace, and maybe the push to start again :)

6 3 130 28K 149

View Details

lauren @poteto

6 days ago

how do you trust your agents' work more? copy this post/link and give it to your @bot or agent! 1. codebase improvements: this is just good software engineering - better architecture, stronger types and invariants, clear boundaries. agents love to copy what exists and take the shortest path, so make the easy thing the right thing. categorically eliminate problems through code and you won't need to think about it again. 2. static analysis: lint rules, tests, CI, verification (eg TLA+). very token efficient ways to catch issues ahead of time. 3. prose: comments, rules, AGENTS.md, skills - anything that can't be enforced and requires agent judgment. use it minimally, but do use /create-verification-skill. 4. human review: the hardest to scale. at the rate agents land code, it's pretty much impossible to thoroughly review every PR, so spend that effort on the highest leverage point, designing an environment where agents do the right thing by default. this forms an inverse pyramid: you want most of your effort at the top, least at the bottom. codebase improvements are deterministic, making it more token efficient, and lets you sleep more soundly at night. install github.com/cursor/plugins… and create a new Project: 1. look through my slack/chat messages and code review comments where i've given feedback on PRs, code, architecture 2. use /recall on my past transcripts to learn how i steer agents 3. /poteto-mode use /correct and /architect on past commits to find the most common pitfalls agents fall into, then propose a plan to rearchitect the code i own so it's more agent friendly. answer open questions with prototyping rather than defer to me, and back the plan with real data. 4. before you begin, use /sharpen + /in-your-own-words and confirm this prompt with me

601 511 7K 727K 13K

View Details

Quincy Larson @ossia

6 days ago

This is the most popular freeCodeCamp course we've published all month. And we published 2 FREE banger books this week, too. Hit 'em.

Quincy Larson @ossia

6 days ago

x.com/i/article/2111…

4 166 1K 54K 1K

5 59 478 17K 418

View Details

Cindy Sridharan @copyconstruct

6 days ago

@dcarter_js Might need to scrub some work specific stuff, but about 95% of it is just good general software engineering principles I’ve collected from the best sources I know (if I do say so myself). I’ll try to make it public over the weekend.

50 8 1K 32K 716

View Details

Jaewoong Eum @github_skydoves

6 months ago

Published a new open-source project, Compose Performance Skills. ⚡️ This is a curated library of Agent Skills focused on Jetpack Compose performance. Every skill is grounded in primary sources. github.com/skydoves/compo…