__mharrison__

At least that's what happened when I created a Python sdk for my $500 video light.

But it is another guardrail that you are giving AI. When you have the AI use ty (and it runs almost instantaneously) after every edit, you are stacking the odds in you favor. There's no reason not to do this.

May the tokens ever flow.

Note that:

Writing code, then tests

Is not equivalent to:

Writing tests, then code

Another benefit to using Python, is if you subscribe to writing/vibing a throwaway version first, a Python version is 100x better than a spec.

(Disclaimer: I teach Python and AI for a living and am doing a tutorial at pycon this week, Beyond vibe coding. Am also using other languages as there are times when Python isn't appropriate)

This article only talks about beginners digging a hole for themselves.

Doesn't mention the speedup that experts get.

I'm my post 12 years as a corporate trainer, I've worked with lots of companies, teaching how to code, collaborate, and what makes code good. I've also used AI a lot and can use it to quickly write code better than 95% of software engineers. (Sample size one disclaimer)

I made a slicing plugin years ago that lets you create a layer that defines named rectangles. Each area under the rectangle is saved as an image.

They're hired to be responsible for some part of the product.

Introducing AI doesn't remove that responsibility.

Folks tend to focus on the code and the tools they're using (maybe I'm cynical from years in the industry). I don't think your boss wants to do your job, even if they could use AI to do it. I think your boss wants to have a headcount, and he wants the headcount to be responsible for the product.

There is a difference between:

- write code, write tests

And

- write tests, write code

Had another agentic (vibe) coding experience, which confirmed that for me. Creating an SDK for a $500 light so I can control it from my Steam Deck instead of my phone (no SDK existed before yesterday). For anyone interested, I'm teaching my vibe coding (I meant agentic) tutorial at pycon next week. The 3-hour-long version should be posted to YouTube soon thereafter.

My friend with long Covid fatigue (and no taste since late 2020) saw good improvements from nicotine patches.

(28 year emacs user)

Debugging: use a debugger, create intermediate variables using .pipe (and side effects), logging, testing, writing your code clearly (use good naming).

- 40x speed improvement

- Painless env setup

- 20 Second deploy

- 90+% test coverage

- Ability to quickly refactor

- Documentation

(The original system that I wrote with one other programmer 20 years ago took 1.5+ years to write. Modern rewrite: 2 days)

I took the plan that I used from Codex and handed it to opencode with Qwen 3.5 running locally.

It created a library very similar to Codex but took 2x longer.

I haven't tried Qwen 3.6 but I hear it's another improvement. I'm confident with my AI skills that if/when cheap/subsidized models go away, I'll be fine running locally.