Adam Renberg Tamm
274 posts
Adam Renberg Tamm
@tgwizard
Building AI software @stilla. API connoisseur. CS aficionado. Reader of SF&F. Mostly on Threads.
Stockholm, Sweden Bergabung Temmuz 2008
2K Mengikuti273 Pengikut
Adam Renberg Tamm me-retweet
Stilla already helps thousands of organizations get work done where they already work.
Multiplayer, context layer and AI automation that works the way your team does, right where you already work. Proud to be featured by @SlackHQ.
stilla.ai
Slack@SlackHQ
Need an AI teammate that gets work done? Stilla might just be what you're looking for. 🧠 @Stilla Cofounder @siavashg shows what @stillaai does right inside Slack — picking up context from your tools and conversations, then getting to work. Just @-mention it and you're off to the races. Now on the Slack Marketplace 👉 sforce.co/4e7THFT
English
Adam Renberg Tamm me-retweet
Need an AI teammate that gets work done? Stilla might just be what you're looking for. 🧠
@Stilla Cofounder @siavashg shows what @stillaai does right inside Slack — picking up context from your tools and conversations, then getting to work. Just @-mention it and you're off to the races.
Now on the Slack Marketplace 👉 sforce.co/4e7THFT
English
Adam Renberg Tamm me-retweet
Sorry if I post this again, but: this is the best post about AI slop you are going to read in the next 2 years.
Caleb Gross@noperator
English
Why hasn’t OpenAI made a native Slack integration where me and my team can collab on Chat and Codex threads?
This feels like an easy win. What am I missing?
English
Adam Renberg Tamm me-retweet
There are two related, but distinct, problems with MTTR maximalism.
1. The distribution of recovery times could be heavy-tailed, and so the empirical mean could be far from the true mean.
2. Some failures are unrecoverable (e.g. durability loss).
Mitchell Hashimoto@mitchellh
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out. I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really). It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely. The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture. We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying. I worry.
English
Adam Renberg Tamm me-retweet
Adam Renberg Tamm me-retweet
Adam Renberg Tamm me-retweet
hi, i'm a sole proprietor/founder in Austria and i earn many many multiples of what i'd earn as an employee, despite "predatory income tax". in fact, i opt out of the many tax optimizations i could use because i like having good schools and as high a standard of living as possible for everyone.
the great thing about the EU is that you can just live under any tax regime you like in any of the 27 member states. it's all about trade offs. if poland works for you, fantastic! go build there.
and if i may add one more thing: if the CEO of a startup, especially pre-revenue, lives "barely any better than a regular employee" then the system works as intended. fact of the matter is most startups are bad. you are not special because you are trying out a shit idea and fail. but i'll happily pay taxes so you can try your shit idea, fail, and can still live.
Denis Yurchak@denisyurchak
In Austria, a CEO of a startup lives barely any better than a regular employed developer A former boss of mine (an exited founder) wanted to buy a new desk Instead of going to IKEA, she went to a site for used furniture and searched for one there, because it was much cheaper For my Eastern European mind, this is incomprehensible If you put years of your life into building a business and take on the risks, you should be rewarded accordingly You should definitely have enough money to go to a damn IKEA and buy the best possible desk there (and write it off in taxes later!) But this is not the case here The system is engineered for equality and social stability The monetary distance between employers and employees is minimal, thanks to predatory income taxes Great if you are an employee, soul-eating if you are a founder
English
Adam Renberg Tamm me-retweet
Adam Renberg Tamm me-retweet
Ghostty is leaving GitHub. I'm GitHub user 1299, joined Feb 2008. I've visited GitHub almost every single day for over 18 years. It's never been a question for me where I'd put my projects: always GitHub. I'm super sad to say this, but its time to go. mitchellh.com/writing/ghostt…
English
Adam Renberg Tamm me-retweet
We’re sorry our initial statement didn't properly address our mistake. Here's what a public project on Lovable means, and how we got to where we are today:
In the early days, people didn't know what Lovable was capable of. So we wanted to make it easy to explore what others were building, as a way to spark ideas and lower the barrier to getting started. Like scrolling GitHub or Dribbble: you browse projects to see what's possible, then go build your own.
When you create a project on GitHub, you can make it private or public. Lovable worked the same. Users had a "Public" or "Private" option right in the chatbox. A public project meant the entire project was public, both chat and code. “Just like a public project on GitHub," we thought.
Over time, we realized this was confusing. Many users thought "public" just meant others could see their published app, not the chat of an unpublished project. That's reasonable.
On the free tier, users originally couldn't create private projects. They had to upgrade to a paid plan to do so. In May 2025, we changed this: users on the free tier could choose to make their projects private. For enterprise customers, the public visibility setting was disabled altogether. And in December 2025, we switched to private by default across all tiers.
We also retroactively patched our API so public project chats couldn't be accessed, no matter what. Unfortunately, in February, while unifying permissions in our backend, we accidentally re-enabled access to chats on public projects.
This was reported through our vulnerability disclosure program (via HackerOne). Unfortunately, the reports were closed without escalation because our HackerOne partners thought that seeing public projects’ chats was the intended behaviour.
Upon learning this, we immediately reverted the change to make all public projects’ chats private again. We appreciate the researchers who uncovered this.
We understand that pointing to documentation issues alone was not enough here. We’ll do better.
Lovable@Lovable
We were made aware of concerns regarding the visibility of chat messages and code on Lovable projects with public visibility settings. To be clear: We did not suffer a data breach. Our documentation of what “public” implies was unclear, and that’s a failure on us. Specifically for public projects, chat messages used to be visible — this is now no longer possible. When it comes to code of public projects: That is intentional behavior. We have experimented with different UX for how the build history is surfaced on public projects, but the core behavior has been consistent and by design. Importantly, for enterprise customers, being able to set visibility to public for new projects has been disabled since May 25, 2025.
English
Adam Renberg Tamm me-retweet
@Latens_Verax Kladda och styra? Det är vi skattebetalare som betalar att man får vara hemma med sitt barn. Att pappor inte ens kan tänka sig att ta tre månader (med betalning!) är helt knäppt. Men är man så knäpp vill i alla fall inte jag betala hans fru för att ta hand om hans tre månader.
Svenska
Adam Renberg Tamm me-retweet
Adam Renberg Tamm me-retweet
My dear front-end developers (and anyone who’s interested in the future of interfaces):
I have crawled through depths of hell to bring you, for the foreseeable years, one of the more important foundational pieces of UI engineering (if not in implementation then certainly at least in concept):
Fast, accurate and comprehensive userland text measurement algorithm in pure TypeScript, usable for laying out entire web pages without CSS, bypassing DOM measurements and reflow
English
Adam Renberg Tamm me-retweet
So @stillaai went from a nice transcription tool at @polar_sh to a full fledged & A+ team member in a few months.
Shipping code, debugging issues and keeping us aligned on priorities.
We no longer have async standups. Stilla knows our goals for the week, shares updates and contributes towards them.
It’s fucking magical software.
English