Dmitry Lezhnev (@dimalezhnev) header
Dmitry Lezhnev (@dimalezhnev) profile picture

i make software.

Tbilisi, Georgia
Joined June 2011
Photo by Dmitry Lezhnev (@dimalezhnev)Photo by Dmitry Lezhnev (@dimalezhnev)Photo by Dmitry Lezhnev (@dimalezhnev)Photo by Dmitry Lezhnev (@dimalezhnev)Photo by Dmitry Lezhnev (@dimalezhnev)Photo by Dmitry Lezhnev (@dimalezhnev)Photo by Dmitry Lezhnev (@dimalezhnev)Photo by Dmitry Lezhnev (@dimalezhnev)Photo by Dmitry Lezhnev (@dimalezhnev)
On some random thread.
30
In fact I do have @unclebobmartin skill, use it all the time, happy as hell :)
11
I've been experimenting with no-framework app setups since many years ago (some back reference: lessthan12ms.com/frameworkle…) Eventually was gravitated towards big Laravel ecosystem. But now the old "light and little-dependencies" ideas are coming back to support AI agents.
1
28
What an agent needs is small footprint of the code, to allow small context window and better LLM reasoning. It feels right. It feels potential.
1
22
why spin up a huge PHP/Laravel setup for a project if agents will exhaust its context just by analyzing existing files. Instead light (micro) setups will drive automatic software making by optimizing for efficient context usage, less moving parts, and easier testing.
22
Automated AI can create or copy any software, or SaaS product in hours, days. Completely automated, from idea discovery to publishing, marketing, accepting payments and customers support. That is not "if", that is "when".
1
17
How the business will change if any selling product is copyable in days and for a few hundreds of bucks. WHAT is going to happen with the business models, companies and markets? I wonder if I can ask @GeoffreyHuntley for an opinion!
12
The initial gap. A SaaS dev builds a SaaS (part 6) 🧵👇 In media we only see SaaSes that succeeded. It creates the illusion that founders built something… and users appeared. [1/6]
1
26
This phase is exhausting. Slow momentum. Manual work. Little visible progress. I think this resistance is why products like this rarely exist. Habits. Stereotypes. Market inertia.[5/6]
1
17
Founders must fight existing patterns to build a better world. That takes time. To be continued.[6/6]
16
# First 50 pieces of content (A mini-series where a SaaS developer builds a SaaS / 5) We shipped our MVP, pushed a few ads, and builders immediately started signing up and uploading videos. [1/4]
1
28
We still don’t know the final shape of the product. We call it a “video portfolio” for now, but that’s not quite right. [3/4]
1
17
Two big insights so far: The platform’s value = rich features + strong builder variety Cold ads don’t work at this stage. Growth is manual, 1:1, signing people up on their phones as we talk. More soon.
14
Let’s validate the problem (part 4). A SaaS dev builds a SaaS 🧵👇 We posted in a few local groups and got our first 3 sign-ups. We contacted them right away. People liked the idea and immediately asked: “Where’s the app?”
1
26
A few days later: 5 real profiles with uploaded videos. The MVP wasn’t the bottleneck anymore. Now we needed more builders, more conversations, more feedback.
1
15
We believe the product solves two things: 1. A safe place to store & show off work videos. 2. A searchable directory of trusted builders. Next thread: what we did next 🛠️
16