@hauju.bsky.social
Quit the safe route. Now building my own stuff. β http://seggwat.com (feedback SaaS) β http://oxidt.com (Dev blog) Indie hacker π§βπ» Β· Rust enthusiast π¦
"We didn't change anything"
checks deployment
image tag: latest
You did. You just don't know what.
AI-assisted coding is the digital photography moment for software development.
Companies that skip it won't just be slowerβthey'll be outpaced by teams shipping 10x faster.
The gap is widening. Every. Single. Day.
Genuine question for devs using AI assistants:
How often does Claude decide your auth system is "unnecessary complexity" and just... removes it?
Asking for a friend.
Configure in Profile Settings β seggwat.com
29.01.2026 10:58 β π 0 π 0 π¬ 0 π 0
Hot take: most product teams collect feedback in Slack threads, spreadsheets, or not at all β then wonder why they ship the wrong features.
We're building a tool to fix that. No guessing what you need β you tell us.
What's the #1 feature that would make you actually switch? π
Yeah, agent-browser works faster for me π
29.01.2026 10:48 β π 1 π 0 π¬ 0 π 0
Writing e2e tests with agent-browser in Claude Code is surprisingly smooth.
Describe what you want to test in plain language β AI navigates, clicks, fills forms, and validates.
No more brittle selectors. Tests that read like requirements.
Love devcontainers much, but use also often docker compose .
25.01.2026 16:06 β π 0 π 0 π¬ 0 π 0
Building my own affiliate platform vs paying for an existing solution... The dev in me wants to build, but is it worth it?
What's your take?
#BuildInPublic
Curious builders, what's your local dev setup?
π³ Docker Compose
π¦ Devcontainers
βοΈ PaaS from day one
π οΈ Bare metal chaos
Drop your stack belowβbonus points for why you switched π
#DevOps #BuildInPublic
The calculus changed.
AI handles the complexity. You get the benefits.
Maybe it's time to reconsider which languages we ask AI to write.
#RustLang
π° Better economics
β’ Superior performance = fewer compute hours
β’ No GC pauses = predictable latency
β’ Consistent resource usage = easier capacity planning
When scaling, efficiency compounds.
π Memory safety without garbage collection
Rust eliminates entire categories of bugsβbuffer overflows, use-after-free, data races.
No runtime overhead. No safety trade-offs.
AI just made Rust's biggest criticism irrelevant.
The knock on Rust? Steep learning curve. Ownership. Borrowing. Lifetimes.
But if AI writes the code, that doesn't matter anymore.
What's left are pure advantages π§΅
Am I the only one who creates new accounts because I forgot which email I used last time? π
Currently using email auth for my SaaS. Thinking of switching to passkeys.
What do you prefer?
45 days live. 0 customers.
The honest #buildinpublic update for
@seggwat.bsky.social:
β
Product works
β
Docs written
β
Widgets ready
β Distribution figured out
Building is the easy part. Finding customers is the real game.
Back to it.
#BuildingInPublic
How it works:
- Claude Code's native skills system loads at startup
- This skill writes new skills when it finds extractable knowledge
- Descriptions optimized for future retrieval
Check it out: github.com/blader/claud...
When Claude discovers something non-obvious during debugging, it saves that knowledge as a new skill.
Next time a similar problem comes up, the skill loads automatically.
Persistent learning across sessions.
Every AI coding session starts from scratch.
You spend an hour debugging some obscure error. Claude figures it out. Session ends.
Next time you hit the same issue? Start over.
This Claude Code skill changes that π§΅
Is your AI agent still crawling your .env? π¬
You should be using an password manager like #infisical
Secure secrets management > plaintext env files
Hey builders, how do you collect user feedback for your products?
#BuildInPublic
@zed.dev + devcontainers = π β
Your environment variables now follow you into containerized development. Setup once, code anywhere.
Are you using it yet?
"Can you show me what you mean?"
Screenshot annotation in SeggWat:
πΈ Capture β βοΈ Annotate β π€ Submit
No more back-and-forth. Just clear, visual feedback.
seggwat.com
#UserFeedback
The future is here: AI just cleaned my desktop.
Life is great.
For me Leptos and Dioxus works fine βοΈ
15.01.2026 07:19 β π 1 π 0 π¬ 0 π 0@zed.dev just added devcontainer support.
Why should you care?
β New dev productive in minutes, not days
β Same environment on every machine
β Save space for AI coding
β CI/CD runs the same container
β Version controlled setup
"It works on my machine" β "It works on everyone's machine"
That's the power of devcontainers.
One JSON file. Identical environments. Zero setup headaches.
New guide on getting started π
The solo dev winter day:
7AM: Coffee
8AM: Code
13PM: Realize I haven't moved in 5 hours
2PM: Exercise
5PM: Sauna
Repeat tomorrow.
Who else? π
I wrote a full guide with workflows and commands.
oxidt.com/use-git-work...
What's your setup for working with AI assistants?
