I asked Codex to write some unit tests for Redux today. At first glance it looked fine, and I continued on. I then went back to add a test by hand, and after looking more closely at the output there were like 50 wtf worthy things scattered in there. Sure they ran, but it was bad in all sorts of ways. And this was just writing something very basic. This has been my experience almost every time I use AI: superficially…
I've always said every line is a liability, its our job to limit liabilities. That has largely gone out the window these days.
Code is cheap. Show me the talk
191–200 of 237 posts
Re: Code is cheap. Show me the talk
#192Just because a bunch of people tell you the practice of performing the art form of producing software via handwriting code is over doesn't mean it's over. This form of hyperbole is intended to overwhelm your reason, get you to forget your own expertise, and trick you into engaging with the topic in a fearful manner (literally FOMO). Don't fall for this cheap stunt.
Re: Code is cheap. Show me the talk
#193Earlier quoted context omitted.
This is the fun part of whole AI-built things that a lot of people don’t want to accept - it really, really, really does not matter if the code “nice, maintainable and etc.”. Does it work? Is it somewhat extendable with AI? Are users generally happy and adoption rate is high? That’s it.
In this case, no, it does not work. CC is full of reported rendering issues, including some that affect me.
Re: Code is cheap. Show me the talk
#194Earlier quoted context omitted.
I've always said every line is a liability, its our job to limit liabilities. That has largely gone out the window these days.
A better formulation is "every feature is a liability". Taking it to the line of code level is too prescriptive. Occasionally writing more verbose code is preferable if it makes it easier to understand.
Re: Code is cheap. Show me the talk
#195We practically found one thought. The measure is: how well can an AI operate in/with your codebase.
I regularly find myself wondering if skeptics throwing around their empirical failure are obscuring their bad code/docs/setup.
Re: Code is cheap. Show me the talk
#196Earlier quoted context omitted.
I've always said every line is a liability, its our job to limit liabilities. That has largely gone out the window these days.
> every line is a liability, its our job to limit liabilities. Hard agree!
Re: Code is cheap. Show me the talk
#197Earlier quoted context omitted.
This is how you do things if you are new to this game. Get two other, different, LLMs to thoroughly review the code. If you don’t have an automated way to do all of this, you will struggle and eventually put yourself out of a job. If you do use this approach, you will get code that is better than what most software devs put out. And that gives you a good base to work with if you need to add polish to it.
I actually have used other LLMs to review the code, in the past (not today, but in the past). It's fine, but it doesn't tend to catch things like "this technically works but it's loading a footgun." For example, the redux test I was mentioning in my original post, the tests were reusing a single global store variable. It technically worked, the tests ran, and since these were the first tests I introduced in the code…
Re: Code is cheap. Show me the talk
#198Earlier quoted context omitted.
A better formulation is "every feature is a liability". Taking it to the line of code level is too prescriptive. Occasionally writing more verbose code is preferable if it makes it easier to understand.
This sounds wrong, features have to be the value of your code. The required maintenance and slow down to build more features (technical debt) are the liability, which is how I understood the relationship to "lines of code" anyway.
I can sort of understand it if I squint: every feature is a maintenance burden, and a risk of looking bad in front of users when you break or remove it, even if those users didn't use this feature. It's really a burden to be avoided when the point of your product is to grow its user base, not to actually be useful. Which explains why even Fischer-Price toys look more feature-ful and ergonomic than most new software products.
Re: Code is cheap. Show me the talk
#199Earlier quoted context omitted.
This is how you do things if you are new to this game. Get two other, different, LLMs to thoroughly review the code. If you don’t have an automated way to do all of this, you will struggle and eventually put yourself out of a job. If you do use this approach, you will get code that is better than what most software devs put out. And that gives you a good base to work with if you need to add polish to it.
The quality of generated code does not matter. The problem is when it breaks 2 AM and you're burning thousands of dollars every minutes. You don't own the code that you don't understand, but unfortunately that does not mean you don't own the responsibility as well. Good luck on writing the postmortem, your boss will have lots of question for you.
Re: Code is cheap. Show me the talk
#200> Code was always a means to an end. Unlike poetry or prose, end users don’t read or care about code. Yes and no. Code is not art, but software is art. What is art, then? Not something that's "beautiful", as beauty is of course mostly subjective. Not even something that works well. I think art is a thing that was made with great care. It doesn't matter if some piece of software was vibe-coded in part or in full, if i…
Tolstoy argued that art is essentially the transmission of feeling from the artist to the audience. He claimed that when an artist experiences an emotion and then, through their work, evokes that same emotion in others, that is art.