If it is, and it works well, then to me this is far more meaningful than the fact that AI wrote 130K lines of code.
4,496 karma · joined April 1, 2015
If it is, and it works well, then to me this is far more meaningful than the fact that AI wrote 130K lines of code.
- you are using AI as an E2E testing tool and it's a requirement to not just test the API but also the workings of the UI
- you are using some third party tool and want to automate its usage
This has been tried so many times already. It works nice for functions that only do some arithmetic. But in any real life system that pushes data around over the network or to databases, most things will happen inside effects which leaves the compiler clueless as to whether the function implementation does what it's supposed to do or not.
Don't get me wrong, I'm a big fan of using the compiler to improve productivity and I also believe strong typing leverages LLM power. But this kind of function specification is a dead end IMO.
> The trap is that get_user_by_name ends up loading shared libraries from the new root filesystem to resolve the username. An attacker who can plant a file in the chroot gets to run code as uid 0.
To me such a get_user_by_name function is like a booby trap, an accident that is waiting to happen. You need to have user data, you have this get_user_by_name function, and then it goes and starts loading shared libraries. This smells like mixing of concerns to me. I'd say, either split getting the user data and loading any shared libraries in two separate functions, or somehow make it clear in the function name what it is doing.
Well this is true, but that doesn't mean that there isn't any other way to acquire this knowledge. Until now, this way of gaining deeper understanding was simply the most practical one, since you needed to write lots of code when starting out as a software engineer.
But it's just as well possible to gain knowledge about useful abstractions and clean code by using AI to do the work. You'll find out after a while which codebases get you stuck and which code abstractions leverage your AI because it needs fewer tokens to read and extend your codebase.
- a very large codebase
- a codebase which is not modularized into cohesive parts
- niche languages or frameworks
- overly 'clever' code
What I like about it: it's one of those games that are easy to learn but difficult to master. Modern analyzing tools can detect your errors and weaknesses, providing you with eternal possibilities to improve.
But also, I like the excitement of the live tournaments, which like poker, have money prizes and an entry fee. They are all over the world and I especially like visiting tournaments in places which I otherwise wouldn't visit. Plus after a while you'll make friends in the tournament circuit, so it becomes a social thing as well.
> Worst outcome is the US attacks Cuba ..
As you probably know POTUS was announcing already that Cuba would be next.
Yes that would be a typical US solution. Let's liberate the Cuban people! By flattening them.
For instance, isn't it complicated to have their output be in perfect sync with the frequency that comes in via the electricity net? Because to me it seems that if they won't, you will have lower benefits or even a net minus after plugging it in.
In practice I try to combine the best of both worlds. I write some code by myself and rely on my LLM for parts that are not too big and where I expect it to do a pretty good job.
Good luck doing that in any company that does something meaningful. I can't believe anybody can seriously be ok with such a workflow, except maybe for your little pet project at home.
The environment where the over-engineer tends to be promoted is one where the engineering department is (too) far separated from where the end users are. Think of very large organizations with walled departments, or organizations where there simply is not enough to do so engineers start to build stuff to fight non existing issues.
Your either don't understand or don't want to understand what people are commenting about here. Of course nobody thinks that only money has value. If only money had value, why would anybody exchange money for, say, a bread?
What many people are wondering about, is whether the value of the money paid by tax payers to artists, equals the value of what they give to the tax payers in return. Because if it would be equal, then one might wonder why they apparently are not able to sell their art for the same amount of money.