Old Stack Journal
59 posts

Old Stack Journal
@oldstackjournal
AI tools, web workflows, build notes, and simple-stack thinking for people building real things on the web.
Sumali Mayıs 2026
234 Sinusundan21 Mga Tagasunod

@abembridgeai @T_Zahil OSS models? Like locally hosted you mean? Don’t you need mega hardware to run local stuff?
English

@T_Zahil Not a bad tool to throw in the arsenal when subscription subsidies dry and you realize OSS models can handle almost all tasks at 95% cheaper prices. But for now I agree, codex/claude code is 98% of my workload
English

@khushiirl Yeah when the product is already good especially. Of course all products could be better though. Clever question:)
English

𝕏 gets way better when your feed is full of builders.
People shipping projects. People solving problems. People obsessed with tech.
Looking to connect with more people into: AI, SaaS, coding, startups, web dev, engineering & tech.
Let’s connect 🎉, I’m building Fahemeni a learning workspace ✅📚 building in public helped me connect with so wonderful people 🧑💻
English

reddit.com/r/codex/s/Wh4Z…
Is this tomorrow’s announcement?? Fingers crossed 🤞
English
Old Stack Journal nag-retweet
Old Stack Journal nag-retweet
Old Stack Journal nag-retweet

"Anyone can access state of the art AI models. It's the combination of enterprise data, coupled with state of the art AI, that allows customers to build unique, differentiated experiences."
@AWS's @rahulpathak and @levie on why the enterprises pulling ahead are not winning on model quality. They are winning on data.
Watch here. x.com/i/broadcasts/1…
English

@khushiirl Haven’t told anyone yet but… YOLO texttodeck.com
English

Most web projects are still pages, forms, users, records, uploads, emails, reports, and cron jobs. For that, LAMP is still a very sensible fit. Old Stack Journal: oldstackjournal.com/web-tech/lamp-…

English

@sflorimm Codex for the win. Way better for building what I build.
English

Not every side project needs a modern JavaScript stack.
For a lot of solo builder tools, PHP + MySQL + Apache + cron is still enough.
If the app is forms, tables, scheduled updates, and one useful answer, keep it simple: oldstackjournal.com/workflows/not-…

English










