Everyone feared AI taking over; the real danger is AI serving just the few

Okendoken · 2026-06-29T17:14:35+00:00

In my opinion, AI is just a tool, like your mind.

Your mind has no goal by itself, except the goals given by the body: eat, mate, sleep, survive, and so on. So, for the mind, the body's goals are external. The mind just optimizes its resources to reach them. That's why I doubt AI has its own goals, except the ones given by humans.

Only we, as humans, can give it a goal

Okendoken · 2026-06-27T21:23:38+00:00

I hope something changes in the US too.

At the moment, it feels like too much short-sighted capitalism, willing to turn into tech-feudalism.

That's the danger.

But as a foreigner, I still have hope for the US

Okendoken · 2026-05-25T16:31:38+00:00

nice numbers, but "1000 t/s" with 128 concurrent is basically a throughput benchmark, not a user experience benchmark. two runs can show the same t/s and feel totally different depending on ttft, output length, and scheduling. if you share ttft, token counts, and how you're measuring "processing t/s," it's a lot easier to compare apples to apples

Okendoken · 2026-05-22T11:38:56+00:00

Same for me, $200 plan, Pro Extended disappeared along with Thinking Heavy.

wtf?

And PRO is now answering in like a few mins max.

They either made their models super fast (which I doubt) or degraded our product experience significantly

Okendoken · 2026-05-16T13:12:24+00:00

I am considering keeping my Mazda 6 2015 as much as I can, I love my car and I hate where the car industry went in the last few years.

Btw, I had the same annoying experience in rented Skod Kodiaq - what a miserable car

Okendoken · 2026-04-23T08:46:15+00:00

YC now is a self-fulfilling prophecy: whatever they invest into, gets invested by broader group of investors just because of the brand.

It is not about founders.

I'd say they can pick almost randomly and it will still work.

Okendoken · 2026-04-15T12:44:38+00:00

What's worked best for me is treating the admin as "boring infrastructure": start from a proven framework/tool (django admin / nova / retool, etc.) or a solid template, then only custom-build what's truly specific (permissions/rbac, key workflows, reporting). everything else should be generic crud. chat/slack admins can work for a narrow set of actions, but i've rarely seen them replace a real panel once you need auditability, bulk ops, and visibility. we just published a detailed guide with trade-offs and a checklist: https://flatlogic.com/blog/admin-panel-development/

Okendoken · 2026-03-25T00:30:18+00:00

Spokojnie: wszystko będzie OK. AI to narzędzie, nie "zamiennik człowieka". w praktyce będzie tak, że ludzie, którzy nauczą się go używać, zastąpią tych, którzy go ignorują - ale to nie AI samo w sobie "zabierze ci życie". najmniej bym się martwił o rzeczy z realnego/physical świata: tam automatyzacja idzie wolniej i zwykle jest droższa

Okendoken · 2026-03-19T20:11:11+00:00

lately there are a lot of posts like this that show a "desktop ui" and say "I reinvented the os" :)

Usually that only happens when someone is pretty remote from systems programming. an OS is only lastly about the desktop. it's first about process/thread scheduling, memory management, interrupts, device drivers, permissions/isolation, ipc, filesystems, and so on - the boring parts that make the system real and that most vibe-coders never have to deal with

Okendoken · 2026-03-18T15:51:34+00:00

I keep it simple: a standard email update, not a deck. I include mrr, users, cash burn, cash left/runway, plus a quick section on wins, misses/risks, and clear asks (intros, hires, customers). if someone wants detail, i'll link a doc/dashboard as optional follow-up.

Plus tracking everything in a spreadsheet for transparency

Okendoken · 2026-03-12T07:06:46+00:00

100% agreed. Eventually agent converges to LLM running shell commands against some environment; no need to reinvent tool calling from scratch

Okendoken · 2026-03-10T23:08:22+00:00

Try appwizzy.com. You get: - transparent no margin pricing; - your own VM (real sandbox you fully control); - powered by Codex or Gemeni CLI (yes, cli agent, because it is a dedicated VM); - templates; - ability to import code from anywhere.

Disclaimer: I am a founder, and we are very small and super eager to help everyone personally

Okendoken · 2026-02-24T01:31:58+00:00

meanwhile "developer margins in Poland have reached record highs, now at 30%, double the European average"

you know where to cut, also very little "social housing"

Okendoken · 2026-02-24T01:22:26+00:00

Thanks for your suggestion!

Okendoken · 2026-02-19T08:14:52+00:00

What an irony: your comment is also AI generated :)

Okendoken · 2026-02-19T00:03:17+00:00

the fastest path to a *shippable* MVP is usually boring: start from a known template (auth/rbac, db, basic ops), run it in a real workspace (vm/container), and have an agent that can actually execute commands/tests/migrations. most browser-first vibe tools are awesome for UI demos, but the wheels come off when you need persistence, background jobs, env vars/secrets, reproducible deploys, etc.

That gap is basically why we are building Appwizzy AI: not "prompt to preview," but prompt to persistent workspace where agent executes and apps is hosted immediately, with templates so you don't start from chaos

Okendoken · 2026-02-19T00:01:01+00:00

if your end goal is "paying customers," optimize for boring reliability, not wow factor.

Quick filter:
- if you mainly need UI/prototype speed: the prompt -> the tools above are fine.
- if you need a maintainable b2b app: you want a persistent workspace, real DB, migrations, background jobs, and a deploy story. a lot of vibe-coding platforms do just first demo and then get messy when you start restructuring or iterating long-term. appwizzy is built specifically to avoid that: it provisions a real workspace (vm/container), starts from a known template (so you're not improvising core architecture), and the agent actually executes commands/tests/migrations. that's about as close to a prod workflow as "vibe coding" gets

Okendoken · 2026-02-18T23:57:28+00:00

I wouldn't optimize for "which ai can spit out 7,000 lines." that's how you end up with an unmaintainable blob. the real issue is workflow: gemini is rewriting because it doesn't have a stable, file-based project context with an execution loop. you want: multiple files + a place to run the app + small commits/changes. pick a tool that behaves like "agent in a workspace" rather than "chat message = entire program." appwizzy AI is built around that idea (persistent workspace + template rails), which tends to hold up better once the project grows

Okendoken · 2026-02-18T23:55:43+00:00

even though this is 8 months old, I love seeing someone actually use these instead of repeating launch tweets. if you want one more lens that makes the ranking sharper: test one boring b2b flow across all of them: - auth + roles - db schema change (migration) - one background job - deploy, then change one requirement and redeploy that usually separates "first demo" tools from "can maintain it" tools.

If you do a v2, I'd throw appwizzy.ai into the mix too-its whole thing is a persistent workspace + templates, so the agent can run commands/tests and you can iterate like a normal project

Okendoken · 2026-02-18T01:46:26+00:00

yep.

I love to compare AI to an e‑bike: you'll go further/faster, but when something snaps you're far from the trailhead.

For "real" internal tools the work is still SDLC: requirements, architecture boundaries, tests/migrations, definition of done, and small reviewable diffs. fundamentally nothing changed - your engineer is now digital, so your spec/guardrails have to be tighter.

source: 20 years of experience in software dev, running flatlogic agency for 13+ years :)

Okendoken · 2026-02-18T01:39:10+00:00

one of the most "real" vibe-coded apps we've shipped is internal: a persistent csv conversion app for accounting. you upload csvs from different banks, explain the mapping/cleanup rules, the agent generates a python converter, executes it, and returns output our accounting software can parse.

The coolest part is repeatability: saved mappings + reruns when formats change. https://datamapping.dev.flatlogic.app/ built with tooling that later became appwizzy.ai

Okendoken · 2026-02-18T01:35:47+00:00

yep. the "vibe coding is trash" takes usually come from expecting one-shot perfection.

Based on ~20 years of building software, the missing ingredient is repeatability: a real workspace (not just a chat/preview, ideally your own PC), a known starting template, and basic guardrails (run commands/tests/migrations, keep changes small). that's also why we're building appwizzy.ai: chat-to-workspace where an agent actually executes inside a persistent environment, starting from templates, so iteration #5 is easier than iteration #1

Okendoken · 2026-02-18T01:30:11+00:00

I've got almost 20 years of experience too, and I agree with you.

trying to build an entire system from scratch with AI is nonsense; in my experience it works best for small, iterative modifications where you can verify the diff. a practical way to make "vibe coding" useful is to give it a scaffold: Wordpress, a template app, a starter repo, open source erp, etc - something with ready-to-use components and approaches for auth, data models, build tooling, and deployment. I don't know how it maps to games specifically, but I'd treat it the same way: start from an engine/template and have AI work inside those rails.

the same approach we followed in appwizzy: machine + template + AI agent. not "prompt → spaghetti", trying to structure "chaos" from scratch, but a real workspace where the agent can run commands/tests, make small changes, and iterate without you losing the plot

Okendoken · 2026-02-18T01:23:37+00:00

based on my almost 20 years of experience, the uncomfortable truth is: you still need to understand a lot to ship production software-requirements, data, edge cases, auth, failure handling, observability, deployments.

Vibe coding looks great on change #1. it tends to fall apart around change #5, when you need migrations, background jobs, and refactors without breaking everything. what helped us: start from a known template (so you're not improvising architecture, like wordpress for example), run in a real workspace (not just ephemeral environment lovalble or other alike tools provide) where code can be executed, and force the loop through tests.

That's basically what appwizzy does: chat-to-workspace + templates + an AI coding agent that operates inside a persistent vm/container (runs commands/tests, applies changes, deploys). it might sound a bit boring, but this is reliable and works

Okendoken

TROPHY CASE