HackerLangs
TopNewTrendsCommentsPastAskShowJobs

robertnowell

no profile record

Submissions

Show HN: Agentic simulator for marketing email A/B testing

inbox-wars.com
2 points·by robertnowell·2 miesiące temu·0 comments

2-d dungeon visualization of 51 real OpenClaw AI engineering tasks [video]

youtube.com
1 points·by robertnowell·3 miesiące temu·1 comments

comments

robertnowell
·26 dni temu·discuss
the main concern here is what is needed to create and sustain that growth rate.

here are three potential issues:

1. there is a short term incentive for lying -- tricking people can get you a long way (e.g. delve)

2. there's a genuine long term incentive for selling products that have short term benefit but long term harm (e.g. gambling, cigarettes, etc).

3. there is a durable incentive to sell products that genuinely benefit for your customers but cause net harm to society -- this last one is a hard problem of capitalism, and imo it's the gov'ts job to make sure that such companies are not allowed to win.
robertnowell
·28 dni temu·discuss
if they are selling to a business, the biz will pay if it solves their problem. if the solution doesn't solve their problem, or something else solves their problem that is easier / cheaper / better, the business will not pay.
robertnowell
·28 dni temu·discuss
their number one priority is solving their problem so they can realize their organization's mission, and that's how it should be.

if the translation is good enough to solve their problem, then it doesn't need to be any better.
robertnowell
·28 dni temu·discuss
the version of this skillset that stays employed is "now I translate 10000x more than i could before by managing a fleet of agents. by encoding my experienced taste and judgement into robust evals, I've helped my ai translators be far better than chatgpt on its own, and much more cost effective compared to manual human translation"
robertnowell
·28 dni temu·discuss
head in the sand
robertnowell
·28 dni temu·discuss
if it was valuable, people would pay for it
robertnowell
·28 dni temu·discuss
unfortunately this person will soon be unemployed.

not because their skills are no longer relevant, but because they are taking a principled stance defending now irrelevant skills.
robertnowell
·28 dni temu·discuss
unfortunately this person will soon be unemployed.
robertnowell
·w zeszłym miesiącu·discuss
this is like telling a student driver they have to push their car by hand instead of putting their foot on the pedal.
robertnowell
·2 miesiące temu·discuss
fair point, but it is not a tesla-style “giant iPad”

primary inputs while driving are buttons and knobs
robertnowell
·2 miesiące temu·discuss
you are correct, I amend my claim.

the interiors are nice, but overall imo the car is a design failure.
robertnowell
·2 miesiące temu·discuss
imo the exterior looks like a cartoon BYD and should be killed with fire.

however while folks are negative on Ive for the car shape, he only designed the interiors not the car body, and the interiors are kinda lovely car interior design:

-no touchscreen (dangerous while driving) -clicky, intuitive tactile switches and buttons -thoughtful use of color (display base color changes based on driving mode)

I mean even just looking at those air conditioning vents (rotate vent to open/close) is classive Ive: intuitive but sophisticated.

I hope more manufacturers copy these new/old patterns on the interiors.
robertnowell
·2 miesiące temu·discuss
> Every software developer knows that you can’t make projects go faster just by typing faster. If that were the case we would all be taking typing lessons.

^ this statement is false. typing infinitely fast would make software development much faster.

typing infinitely fast would not make shipping useful products and features instantaneous, because there is product, technical, and organizational uncertainty that requires iteration and "cross functional collaboration" to figure out.

but ai can make each iteration step a lot faster.
robertnowell
·3 miesiące temu·discuss
interesting visualization of 51 real engineering tasks completed by openclaw ai engineers during March 2026

I was having a hard time explaining how my OpenClaw ai engineering orchestrator runs a structured engineering process by dispatching tasks to OpenAI Codex or Claude Code

...so i rendered it into a video game.

watch a team of Claude-powered ai employees compete against team OpenAI on real Kopi AI engineering tasks.

you are seeing a visualization of 51 actual tasks executed on by a team of openclaw AI engineers during March 2026

these engineers all follow the same structured process.

a task is created by me from slack, and the ai starts a structured process to execute on the task

each desk represents a sub-task dispatched to this employee's coding agent -- either claude code or openai codex

in this way we have two competing teams of ai engineers -- openai vs claude -- you can see each team's score on the left

every employee plans, builds, audits, fixes, tests, and if thye are succesful, creates a PR.

Sometimes they have to audit and fix in a loop several times before they get approval.

if their PR is successfully merged, they get a quick moment to enjoy the plants on the top floor, and then it's back to work.

Sophie is one of our star employees, but not everyone is doing so well.

Sometimes tasks don't get merged, and they fail.

this openclaw engineering system is called b0b, and it's open source on github