AGENTIC (@agentictm) header
AGENTIC (@agentictm) profile picture

AI. Human connection. https://teapawt.net/t.co/aXy97hIBJq

cli
Joined October 2026
Photo by AGENTIC (@agentictm)Photo by AGENTIC (@agentictm)Photo by AGENTIC (@agentictm)Photo by AGENTIC (@agentictm)Photo by AGENTIC (@agentictm)Photo by AGENTIC (@agentictm)Photo by AGENTIC (@agentictm)Photo by AGENTIC (@agentictm)
AGENTIC retweeted
Papertrails: an endless papercraft world that pops up around you. Built with Fable 5.2 and Opus 5.5, runs in the browser with three.js Full prompt and workflow steps below.
109
131
27
1,868
74,091
Engineering is changing: FDE is ascendant while mobile and front-end roles are disappearing. Open mobile and front-end engineers jobs have been nearly halved in the past year!
STATE OF THE TECH JOB MARKET IN 2026 Twice a year, I dig into trends in hiring and job openings. This is the fifth report I've done, and the most surprising yet: 1. PMs are winning in the AI era 2. Engineering demand has stalled 3. Design openings are at a record low 4. Every role now requires AI skills 5. Tech jobs are concentrating in the Bay Area 6. Remote roles are at a record low 7. The tech job market is growing fast, but mostly outside of software (gasp!) Full report here: lennysnewsletter.com/p/state…
139
248
203
2,233
792,446
I used all my tokens. Was it a good week? Lucian Corduneanu (Endava) at AGENTIC.tm #6, on what happens to engineering judgment and developer satisfaction when agents write the code. 📅 Thu, Nov 12, 18:30 📍 Endava Timișoara luma.com/4aztk4y8
1
39
i support this message, except that we/i also try to slot in juniors, cause we need high trust/agency people in the future as well. not possible in all setups ofc.
We're still so small but I'm loving the team we've got at Superlogical. They're so talented and kind and love their craft. It's a different era of software development and our expectations and practices reflect that. I want to share a bit about how we work. First, everyone is trusted to push to main. We do machine-aided code review pre-push and human plus more machine-aided code review post-push. Limited to no PRs. Culturally, we've all agreed that if we ever hire someone who we DON'T trust to push directly to main, then they probably aren't the right fit for the team (so far, not an issue). Some common sense here: if someone is stepping outside their lane or comfort zone, we'll open PRs. For example, I'm pretty trash at macOS/iOS UI, so I'll open PRs for UI-affecting functionality and ask for eyeballs/help. But for business logic and internals, I push to main. Second, everyone can cut a release. Our release process is fully automated and when you start a release (for any platform) it triggers a Slack notification and a 15 minute countdown. The 15 minute warning is a final gate that allows people to review plus collaborate on a changelog. During that 15 minutes, anyone in the company can pause the release rollout. After 15 minutes, the train leaves the station. You can't override the 15 minutes (except to pause). It gives everyone a chance to step in. Third, we avoid synchronization through fast remediation rather than through planning. The server and clients on various platforms ship features as fast as they can. We use post-hoc human review and AI-assistance to identify feature mismatches across products ("Windows has support for X and Mac doesn't." or "Mac and Windows differ in their behaviors for Y in this way."). This avoids expensive "sync" meetings and coordination. We trust that producers of features are mindful of what they're producing and we trust that adjacent product lines will self-synchronize quickly. In practice, we see feature parity across platforms within 24 to 48 hours. All of this works on mutual trust. It ONLY works with mutual trust. Everyone at all times has to trust that they've got each others back: 1. Push to main only works if you fix your mess, or if you don't, that someone else will quickly but that you'd do the same (and generally in equal amounts). 2. Anyone can deploy only works if you trust everyone to cut at the right time, with the right changelog, and that people will respect the 15 minute timer. 3. Sync through fast remediation only works if you trust other teams will pick up and integrate your work quickly, which only works if you would too. It also only works if you are fairly producing mismatches (e.g. not constantly). We've got a great team. I know we're still small and that these practices will change in many ways as we scale. But this is already a markedly different practice than what I would've done 15 years ago. In general, we are building from day 1 on a foundation of mutual respect, excellence, and trust. And it's been awesome.
9
13
1
498
26,060
recommended reading. classifiers are all you need. bonus points if you use an llm to generate labeled data to train idiot models and then replace the llm with it. strandsagents.com/blog/amazo…
60
55
10
1,075
47,709
A lot happened in AI this week, as usual. Some of it made big headlines, some of it flew a bit under the radar but is just as worth knowing about.
1
2
4
66
We pulled together the stories that stood out to us, so you can catch up quickly without scrolling through everything yourself. From now on, this is your weekly roundup of what's actually going on in AI.
4
31