←
akshay oppiliappan173 posts
akshay oppiliappan avatar

akshay oppiliappan

@oppili

building @tangled_org

◷ Joined February 2026▧ 32 Photos and videos
Tangled avatar
⟳ akshay oppiliappan retweeted
Tangled@tangled_org·1h

We redesigned our activity panel →

Tangled avatar
⟳ akshay oppiliappan retweeted
Tangled@tangled_org·Nov 17

akshay oppiliappan avatar
akshay oppiliappan@oppili·Nov 16

same way cars were invented. they left a horse running over the weekend.

Theo claims LLMs were discovered when an autocomplete training run went way too long. Like someone left autocomplete on over the weekend and came back to ChatGPT. LLMs exist bc of the transformer and nobody found that by accident. What the fuck is he talking about

0:17
akshay oppiliappan avatar
akshay oppiliappan@oppili·Nov 14

nix fixes this

the biggest reason more people aren’t using cloud agents is because there’s not an obvious and simple way to migrate your local environment to the cloud feels like there should be an open source tool from one of the coding harnesses that solves this

Anirudh Oppiliappan avatar
⟳ akshay oppiliappan retweeted
Anirudh Oppiliappan@icyphox·Nov 12

We own both infra and product at Tangled, and we've been able to build out our extensive software and platform stack with an engineering team of 6, founders included. The kind of engineers we hire is important here and akin to what Thorsten is talking about. They're not *just* frontend or infra or something specific: we explicitly hire people with the widest range of skillsets. With AI, the wider your breadth, the more effective you are at building and maintaining features E2E. Almost everyone (except our designer who does still write code!) deals with frontend bits, backend services, possess a deep understanding of our distributed system, and how to provision infrastructure to run everything. These types of hires are hard to come by and I'm pretty bullish that we can effectively cap out engineering hiring to around 10–12. All of us use AI extensively, and *effectively*. Everyone's a "figure-outer" and nobody needs to be told what to do -- at least not in the typical corporate org sense. Also why we have this one specific line at tangled.org/company.

Post attachment

What's the right team size? Probably not the one you set in 2024. Think about it: your infrastructure team was 8 people back then, but now, with each person able to do so much more, faster, is 8 still the right size? Do you have more infrastructure to manage? If you have more infrastructure, then maybe. If not, you no longer need 8 people on that team. If the the ambitions of the company align with the increased productivity of teams, that's great, of course. But not every team in every company needs to scale up. If your business success isn't a function of how much infrastructure you manage (to keep using that example), then you want to keep the amount of work the infra team does fixed. And that amount requires less people now. Product teams, on the other hand, can now do a lot more and very likely should. But there the question is: does the org allow that? I was talking to @lewis_b_metcalf yesterday about some engineers really crashing out and lamenting the loss of craft. He said: "Yeah, I get it. If you're in a company where all you were hired for and all you're allowed to do is engineering, then things might suck. But here [at Amp], I can do marketing, I can think of new product ideas, I can ship them, talk to users, record videos. I can do so much more and it's the most fun I ever had." That's, I think, the crux of the matter: your engineers won't become 10x more effective if your org doesn't allow them to. If you haven't done this four times this year already, it's high time to rethink all of your org boundaries and roles. Of course AI won't have an impact on your business if your engineers are sitting there, twiddling their thumbs, waiting for someone to hand them a ticket.

akshay oppiliappan avatar
akshay oppiliappan@oppili·Nov 10

github.com/firecracker-micro… github.com/firecracker-micro… no memory ballooning, no snapshotting, no pause/resume on nitro sandboxes. sandbox companies will live to see another day.

it can not be overstated how big of a deal this is. aws.amazon.com/about-aws/wha…

Anirudh Oppiliappan avatar
⟳ akshay oppiliappan retweeted
Anirudh Oppiliappan@icyphox·Nov 5

Collaboratively clicking on the @AmpCode orb. I didn't know I needed a multiplayer canvas multiplexer. I think this is the best way to work; so awesome when you're sharing devboxes and agents can auto open windows to show you work. @oppili has figured out the most intuitive human-agent work paradigm.

0:10