Leading software teams and AI agents @tryhackme · co-memer @supermeme_ai

Amsterdam
Joined January 2020
really impressed by how easy it is to build an agent with @flueai built turbodiff.dev today in a few hours (between other life stuff) it’s a PR review agent that triggers automatically for each new PR and it adds a PR description and inline code comments
trying out @flueai today the goal - create (yet another) PR review agent to help distinguish signal from noise in large PRs with larger PRs its helpful to have an agent pre-screen the changes and highlight the import parts so I can pay extra attention to it will report back
2
3
1
19
6,751
evergreen
the 2 most important problems in the AI era is infrastructure and security all businesses will face these problems in some form or another in the next 5 years if you solve one of these (or both) you'll be set for success
65
there’s decades where nothing happens; and there’s weeks where decades happen we’re only halfway through one of those weeks
So basically, today PHP got two critical bugs that let anyone run code on your server without even logging in, which is bad, and then the details leaked before the patch was even out, which is worse, and it works on WordPress and MediaWiki and Magento and Joomla and Laravel, and Censys says like 1.5 million servers are running a version with no fix, so the NSA was like "take your system offline," and the FBI was like "take your system offline," and CISA and the UK and CERT-EU were all like "take your system offline," and then the Prime Minister of Japan, the actual Prime Minister, posted at 5:55 in the morning telling 48.8 million people to take their system offline, so everyone took their system offline, like the Dutch cybersecurity agency took its own website offline, and the Dutch parliament went offline, and the Port of Rotterdam went offline, and Finland and France and Denmark started pulling government sites, and Wikipedia went down, and Archive.org went down, and Asana and GOG and Something Awful went down, and the University of Vienna's webmail went down for some reason, and that's just PHP. Because GitLab also dropped a CVSS 10.0, which is the highest score they give out, for a bug that's been there since 2014, so that's every self-hosted GitLab for twelve years, and then LiteLLM 1.107.0 got hijacked and shipped a credential stealer and a remote access trojan in every single wheel and the Docker images, including latest, and you didn't even have to import it, just installing it was enough, and it's the second time this year, and then Railway paused every deployment on the entire platform because someone got into the environment variables, so now everyone has to rotate every secret they've ever stored there, and TiDB Cloud said someone was walking around inside with stolen credentials for basically a month and an extortion group says they took 10.6 terabytes, and Zeabur got breached for the second time in two months and is just shutting down, like the whole company, and Node.js patched remote code execution and a TLS bypass, and CISA says Plex is being actively exploited, and someone took over 300 Tor exit relays to steal SSH passwords, and SafePay ransomware has hit over 600 critical infrastructure orgs, and India's biggest bank filed a data loss incident, and Japan has been in an official state of emergency in cyberspace since October 9, which honestly explains the 5:55 AM post. Oh, and eMudhra, a certificate authority that's issued over 60 million certificates, whose entire job is proving websites are who they say they are, was supposed to be using private keys that are random numbers over a hundred digits long, and one of them was 4. Just 4. And the others were like 66 and 237. Anyway, it's Wednesday.
64
Nico Botha retweeted
Here is a full list of what you can do NOW for PHP2Shell (CVE-2026-109618 / CVE-2026-109619) as a temporary mitigation. (generated and validated by LLM) 1️⃣ Do this first. In php.ini or the FPM pool, set: session.upload_progress.enabled = 0 Reload PHP-FPM, then update PHP right after the release (21 Oct, 14:00 UTC). 2️⃣ Edge block until you patch. It blocks the PHPSESSID cookie and query (also lowercase and URL-encoded), and all multipart/form-data requests. ⚠️ File uploads stop working until you remove it. ☁️ Cloudflare (WAF custom rule, action Block): (lower(url_decode(http.cookie)) contains "phpsessid") or (lower(url_decode(http.request.uri.query)) contains "phpsessid") or (any(lower(http.request.headers["content-type"][*])[*] contains "multipart/form-data")) 🟩 nginx (http {} context): map "$http_cookie|$args|$content_type" $block_php2shell { default 0; "~*(?:p|%[57]0)(?:h|%[46]8)(?:p|%[57]0)(?:s|%[57]3)(?:e|%[46]5)(?:s|%[57]3)(?:s|%[57]3)(?:i|%[46]9)(?:d|%[46]4)" 1; "~*multipart/form-data" 1; } In each server {} block: if ($block_php2shell) { return 403; } 🔒 Caddy: @php2shell expression `{header.Cookie}.matches("(?i)(?:p|%[57]0)(?:h|%[46]8)(?:p|%[57]0)(?:s|%[57]3)(?:e|%[46]5)(?:s|%[57]3)(?:s|%[57]3)(?:i|%[46]9)(?:d|%[46]4)") || {query}.matches("(?i)(?:p|%[57]0)(?:h|%[46]8)(?:p|%[57]0)(?:s|%[57]3)(?:e|%[46]5)(?:s|%[57]3)(?:s|%[57]3)(?:i|%[46]9)(?:d|%[46]4)") || {header.Content-Type}.matches("(?i)multipart/form-data")` respond @php2shell 403 🚦 Traefik v3 (Coolify: Server > Proxy > Dynamic Configurations). Add this to the https router and also to a copy for the http entrypoint: http: routers: block-php2shell: rule: "HeaderRegexp(`Cookie`, `(?i)(?:p|%[57]0)(?:h|%[46]8)(?:p|%[57]0)(?:s|%[57]3)(?:e|%[46]5)(?:s|%[57]3)(?:s|%[57]3)(?:i|%[46]9)(?:d|%[46]4)`) || QueryRegexp(`PHPSESSID`, `.*`) || HeaderRegexp(`Content-Type`, `(?i)multipart/form-data`)" priority: 100000 entryPoints: [https] middlewares: [deny-all] service: noop@internal tls: {} middlewares: deny-all: ipAllowList: sourceRange: ["255.255.255.255/32"] ✅ Test: curl -s -o /dev/null -w '%{http_code}\n' -H 'Cookie: PHPSESSID=x' https://your-app → 403 curl -s -o /dev/null -w '%{http_code}\n' -F a=b https://your-app → 403 The edge block does not protect direct origin access. Disable upload_progress and patch PHP.
24
89
14
622
104,122
Facts! the problem is you only realize this when you’re already in way too deep 😂
or just vibe coding in general man
1
1
157
This is what love for the craft looks like A million builders with infinite tokens cant recreate this experience and storytelling
For years, maybe a decade, I've wanted to build a writing tool that just did a few things I couldn't find anywhere else. A system that mimicked how I think when I write. A system that provided clear affordances, features, and places to do the things I wanted to do. A way to play with my writing as I'm writing it. A way to settle into just the right way to say something. It never made sense to make it a 37signals product because it's not commercially viable, nor would it be worth pulling people off their other work to hack on this. Plus, it would have taken months the old way. So this weekend I just made it myself, with Claude's help. It's called Write_On and the short video walks you through it. Essentially it's "alternative control" at the word, sentence, and paragraph level, plus a way to dim stuff back, and stash stuff near by. Not version control, but alternative control. You'll see what I mean when you watch the video below. So here it is. Write_On.
1
194
much needed sane take on the timeline beware of all the hype - not everything is automatically applicable everywhere
It’s NOT a hot take that we will be reviewing less code soon But today you shouldn’t follow loud voices who have been full sending some of the worst code we’ve ever seen Stick with Ruby or any language for that matter if your team is executing Use AI to elevate your weaknesses
1
1
312
This is one of few topics I disagree with DHH on LLMs are very good executors but can’t think by itself. You as the builder/engineer/coder have to give direction and structure for things like architecture If you dont, and just let the LLM yolo all the 100s of micro decisions that goes into building a product, you’ll end up having to rewrite your app every 6 months because it will become unmaintainable This is not a “i love coding” thing, I’m way past the handwriting code phase and I use LLMs for everything And it may be a skill issue for me, but I dont see how letting an LLM write code that you can’t at least read (instead of something like Rust or any other language for that matter) will end up creating better software
Rust is a good prompt compilation target for the moment, but so is C++. And soon assembler. Then microcode. Myopic to think we're going to stop the agentic drill bit until it reaches computing bedrock.
1
1
113
Great write up by Sanjeev Despite not having met each other in person, this project “just worked” from the start and it’s been an amazing experience to work together Building something is definitely more fun when doing it with great people and it can open doors beyond your imagination And another fun fact - there’s also been 4 new kids born between the 3 of us in the past ~4 years
No AI, no backspace reflections on my ~4 year journey with @supermeme_ai we made over $200k lifetime revenue. based on where you're looking from, this could be a lot or this could be nothing. But the money is lower down the ROI list for me Context - supermeme is an ai meme generator built by three co-founders (@ramsri_goutham @nwbotha and me) out of a whatsapp group. it's a side project for all 3 of us and we don't spend more than a few hours on it every month In no particular order, here are the things i've personally gained or learnt from it 1. personal brand memes was (and hopefully is) my social media identity. I built a following by sharing corporate tamil memes and creating parody sketches. building supermeme made that even more real, the fact it was revenue generating attracted a lot of podcast and speaking opportunities. it also gave me the confidence to start my own youtube channel in tamil where i talk about building microsaas products 2. product dev exposure for me i'm not a developer. beyond to-do lists apps for online courses, i've never shipped code. supermeme was the first place where i could actually dev see work happening in real time. tech conversations between ramsri and nico used to scare me but i'm glad i got exposed to all that. eventually, with claude code and codex help, i actually started shipping things to a real live product app that was being used by thousands of people 3. building a product (vs being a product manager) i was already a pm by the time we started building supermeme. but as a pm, you hardly feel like you're making decisions that matter - its either forced upon you or been shot down by senior engineers/designers. but with supermeme, i was responsible for many decisions we took. it was also not a one way street, many times i had to work hard to convince ramsri and nico (they don't blindly accept ideas) 4. the 'founder' tag the tech world has hierarchies, even if we deny it. you only know about certain whatsapp groups and meetups if you carry a founder tag on linkedin. i was never too comfortable flaunting the founder tag because i was either freelancing or in a full time job but i saw that people who've done less waving their founder status all over the place, so felt better about how i was using it 5. getting attached to an idea and getting detached i was guilty of being too attached to product ideas. even in freshworks, i would passionately (in hindsight, emotionally) campaign for an idea going all out. i was not a pm or dev, so i would be angry and pms and devs for not seeing my idea. with supermeme, i had a lot more control but it still wasn't easy to get things built. i would still get frustrated when my ideas aren't accepted - but over the years, i started getting emotionally detached from an idea or product. i started being objective and i don't know if that helped the product but it certainly helped my mental health 6. software building myths broken after running supermeme with 3 people, no project management tools, minimal budget - i started seeing software development for what it is - rather, what it's not: a complex meeting driven year long activities. i have a fair sense of how quickly things can be done so i can spot the inefficiencies of a product/dev org from outside even if they can't 7. my unshakeable belief on seo seo drives majority of our revenue. if i was more data driven, i could tell you how many clicks we attract but i know it's a lot. as the sole gtm person, i didn't understand SEO at the beginning but we still attracted the right traffic. it taught me that if you just build the right things and use customer language on your website, you'll attract the right audience. seo starts there, not in keyword research - those come later. later, with more nuanced understanding of seo - i was able to a do a lot more, still doing. our goal is to be the default meme generator of the internet - we can do that just with seo. 8. competitor obsession is real but not very useful we would get competitors, some using the exact same language that we did. some would show up higher than our search results. all of this used to upset me. i would try to take counter action but it was fueled by emotions. over the years, i realized that it doesn't matter. there's enough room for everyone and our lives don't depend on this alone, it's okay. anyone can do what they want, we just have to do our thing 9. there's no one way to build or scale saas supermeme isn't a 'successful' saas by global saas standards. our revenue staggers, degrows. we don't convert at a high percentae. sure, if we had played a few cards differently - we could've either made a lot of money or be wildly more successful but we didn't. it was deliberate. i lucked out by having two co-founders who shared the same vision. we knew that we wanted to keep supermeme as a side project while we go on with our lives. we could've raised funds, we didn't. we could've sold it off, we didn't. we're okay with keeping it and keeping it at this scale. 10. team matters i am grateful for both nico and ramsri, beyond their amazing engineering skills - they're just good people. no drama. high trust. willing to put in the intellectual rigor when needed. this has made the entire experience stress free. i can't say that about other teams i've been part of, i've always walked away more exhausted even if we've built something good 11. an idea doesn't have to take up your whole life traditional startup wisdom is that you have to go 'all in'. supermeme's early days were like that for me. i was properly all in - it was my identity. slowly, it wasn't anymore. that's okay. I got interested in other things, strated a family, a new job, picked up hobbies and supermeme's relevancy in my life reduced. that's okay. i can't imagine doing this as a vc-funded founder. this made me realize that i can still run this without it being an obsession, maybe in the future that obsession will come back and we'll do more. for now, i have the privilege of being a bootstrapped founder who can afford to take time off the project besides this, there are so many other micro learnings and regret, but these are the broad themes. the experience was humbling in many places, we've gotten abused over email, weren't able to afford tools and products that we needed and got harsh feedback. i'm just proud and happy that we're afloat as a business, we pay our taxes. we take a decent sum out of it every month and it feels good that it's coming from something that 3 of us built from scratch. of course, lot more to do and we'll do it. at our own pace, at our own liking, in our own ways. but for now, i just wanna acknowledge how far we've come.
122
something about the the lack of hype about the latest model releases tells me that most people don’t have that many tough problems to solve Models are good enough, speed is the real problem to solve at this point
1
115
ANTHROPIC BUILDS BIOLOGY LAB TO PUSH AI INTO DRUG DEVELOPMENT Anthropic has quietly established a Bay Area wet lab, moving its life-sciences ambitions beyond computer simulations and into physical biological experiments. The company wants Claude to direct laboratory robots with limited human intervention, potentially accelerating research into rare and traditionally “undruggable” diseases. Anthropic says it will focus on preclinical research rather than clinical trials, avoiding direct competition with pharmaceutical companies.
1
3
291
the most important issue on github is finally getting addressed
We're adding support for AGENTS.md to Claude Code. Starting today in version 2.1.277, if there is no CLAUDE.md in a folder, Claude will check for and use AGENTS.md. You can toggle this behavior in /config.
1
160
Read the code or dont use PRs or dont run one agent or many in parallel dont believe all the opinions you see about AI Everybody is still figuring it out use whatever makes you productive and helps you ship good software the rest is just noise
1
86
Haven’t been this excited to try a new model in a loooong time
3
175
These Planetscale blog posts are like mini engineering courses Super information dense and interesting recommended read
Today we introduce TIN: a powerful and reliable full-text search extension for Postgres. TIN works with complicated WHERE clauses, replication, backups, and maintains correct transaction visibility. It's also mind-blowingly fast.
1
1
19
686
Hard agree, I much prefer the p(abundance) outlook
The p(doom) discussion gets all the headlines, but the p(abundance) scenery is far more like and deserves much more engagement.
106
I’m a visual learner. So i asked astra to help me understand the @EffectTS_ codebase with a video walkthrough The result is pretty cool
1
1
121
checked out effect.institute from @kitlangton yesterday and now I started rewriting an api in effect and all the hype makes sense effect brings some much needed structure to a typescript codebase. highly recommend checking it out
1
3
262
the main selling point of serverless is that you never have to worry about scaling "it will just scale" regardless of whether you understand scaling or not but in the AI era it's more important than ever to understand scale and the complexity it brings serverless is not necessarily bad but it's not something that will magically solve all your scaling issues
2
85