597 karma · joined August 28, 2021
Businesses, especially tech ones, are not altruistic. The idea that tech companies are out to make anyone's life better is a joke and a sentiment that should have died decades ago. The evidence is of predatory business practices and leveraging the worst aspects of our brain chemistry to keep us hooked on apps that make us less happy, keep us stupid and less informed, and buying more.
Even more confusing are the people who are welcoming AI with open arms as just another skill to learn, _surely_ they'll be the ones who come out on top, right? It has all the stink of the countless Americans believing they too will become billionaires and everyone else are just suckers as they are all one healthcare problem away from bankruptcy.
We don't learn.
I am with you entirely and would not have taken that route today, but it is really easy to see why people go that route.
The goal posts are being moved, yet again, as the reality of generative AI's usefulness starts to narrow. I think most "anti-AI" devs wanted the technology to be supplemental in the first place, in the hands of responsible engineers. The hype riders are the ones who are saying our job is over.
> reducing the cost
The evidence is the contrary. The tools are become more expensive by the month it seems.
As a more emotions based response to your post: I find it pretty gross that we are ready to accept that this tech should be used in art whatsoever. I think saying this is a barrier-to-entry-lowering tech is a misnomer, because even those who use computers still need to understand the program, mechanics must understand the function and implications of a torque wrench; there is no effort or skill involved with generating slop, you always get a result. Additionally, the first part of your post was to argue that we should be using these tools to do narrow scoped tooling and one-off script, and then you moved to generating videos and music, which shows that you aren't even aware of the "scope" involved in those efforts.
Good luck convincing people to not just take the money.
I know plenty of engineers being forced to use these tools whether they want to or not. A lot of which are okay with using AI liberally, but don't particularly like generative AI and see it as pretty irresponsible (which feels more true by the week and it is clear from first hand experience). I don't know, there is a huge gradient of users, but I would argue that in previous revolutionary technologies, we didn't have to force people to use a good tool. I didn't have to be forced to use Google search or Google Maps, tech that is now ubiquitous with western society. It seems really suspect that suits have to enforce the use of something that is supposed to change the way we work and be a force multiplier.
I would like a source for that statement. Additionally, I want to know by who? Because it certainly isn't end users. Inflating token usage doesn't make it any more economically viable if your user base, b2b or not, hasn't increased with it. On the contrary, that is a worse scenario for providers.
I am still baffled about engineer's or developer's use of AI. I see fail and fail on anything other than some novelty one-shotted tool, and even then folks are bending over backwards to find the value because that solution is always a shallow representation of what it needs to be.
My projects are humming away, hand made. They have bugs, but when they show up, I more often than not know exactly what to do. My counterparts have AI refactoring wild amount of code for issue that can be solved with a few lines of adjustment.
TL;DR I feel like I live in a different reality than those who write these blog
You're missing a very fundamental point here, and this is usually something I find with long time C programmers. C is a great, but old language, with decades of overhead on context, tooling, and lib understanding that make getting in to writing C substantially more difficult than say, Rust. We are still humans, and Rust isn't entirely trying to solve C from a fundamental paradigm of handling memory from a technical point of view, but more from a programmer one. Your comment about solving memory bugs is predicated on perfect human usage of C to not write the bug in the first place, which is precisely one of the many problems Rust is looking to solve.
Another observation is developer experience. Again, have you written _any_ Rust? I would argue that the reason Rust is such a joy to use is that the compile time errors are amazing, the way docs are handled are amazing, and so on. I know the eco system for something like Typescript is worlds better, but have you ever tried to _really_ understand what shenanigans are going on behind the scenes on some random hook from say, React? Their docs are so dismal and sparse and make assumptions on what they think you should know. Rust? You go to the doc gen, read what they think you should know as an overview, and if it isn't enough, I can click on "source" to dive deeper. What more could I possibly want?
Perhaps I'm just triggered. The discussion on Rust always seems to be fad or hype driven and almost always have very little to do with how it is to actually use it. If I have to read about compile times, again, I'm going to scream. Of all the languages I've used, it is one of the best in terms of a mature project needing new features or refactors. This is mentioned in some articles, but mostly we hear about "velocity" from some one dimensional perspective, usually someone from the web space, where it is arguable if the person should even bother trying to use Rust in the first place.
Apologies for the rant, but at this point I think Rust as a buzz word for article engagement has become tiring because it seems clear to me that these people aren't _actually_ interested in Rust at all. Who gives a shit what someone on Reddit thinks of your use of clone??