Liability is the answer! If you build an auth system and it fails, it's your backside. If Okta fails, it's theirs. Enterprises buy products as much as they buy protection from problems.
I vaguely remember that from the Scion days. I wonder what that does to liability? Like if it's something that impacts the safety of the vehicle - like a roll bar? - who takes on the liability if it's a dealer option?
Wraps exist for folks who pursue it, which is always going to be a subset of those who only look at dealer / manufacturer options. Being able to get a wrapped vehicle off the line is a new option for most buyers.
What happens when your engineer realizes they can make 10x more at another company? They leave and work stops. You then hire someone else or raise your pay to get better, more reliable engineers. The analogies keep going because AI is a tool, not a replacement. If it's a tool used by a non-technical person, so be it, but it's still just a tool.
Formatters and linters fix the mistakes made by people who know what they're doing. They do nothing to teach someone how to do something for the first time in a way that supports comprehension, only regurgitation.
Help desks and canned replies - if a user complains about X, respond with Y. We used to just have humans do it, but turns out machines can do that bit, too, especially if the question is relatively simple or asked a lot or has an answer not up for debate.
I'm kind of feeling similarly, albeit I've been a Lifetime holder for a while now. So on the other side of the coin is what it would take for me to finally leave. In retrospect, Plex has probably been work $750 for the way I've used it, which I've been doing for easily 15 years now, but if I was not currently a Lifetime subscriber, I'm not sure I'd see the value. That said, I don't want to move platforms, nor do I want to have to set up the family members who steam from my server on something else.
I disagree it's a cop-out, but I agree it's hard to get good at writing prompts and takes a lot of effort. But so is programming. We're trading one skill set for another and getting a bigger return on it.
I started as a skeptic and have similarly drank the kool-aid. The reality is AI can read code faster than I can, including following code paths. It can build and keep more context than I can, and do it faster as well. And it can write code faster than I can type. So the effort to learn how to tell it what to do is worthwhile.
> If I know the answer to all these questions, wiring it together takes me LESS time than passing it to Claude Code.
That's just not true, and if it is in your case, then you're not great at writing prompts yet.
> Take the todo_items table in Postgres and build a Micronaut API based around it. The base URL should be /v1/todo_items. You can connect to Postgres with pguser:[email protected]
That's about all it takes these days. Less lines of code than your average controller.
I'm not going to argue your wants with you because they are your own. Don't buy Apple products if you don't like the way they operate as a company. I don't particularly care for appeasing the administration, either, but it's not like Cook broke the system, so I'm not going to dance on his retirement over it.
It is so easy to sit on and critique from the sidelines. Steve Jobs had a passion for product, and it showed - he pushed the teams to make things he approved of, and that was the measure. Tim Cook had a passion for growth, and as the article states, Apple's income now rival some GDPs. They're different people with different drives. In fact, Jobs told Cook not to do what he would do, but do the right thing, and to Cook that was grow the company. I'd love to see the critics do better.
That adds up over time, though, and it works in reverse. AI will always be able to read and write faster than a person can. You may be able to write the script, but in the time it would take to /literally/ write it, you're on to the next thing. And if that script is actually a feature that spans two or three or 10 files, now you're really cooking.
The devex is great and familiar to folks who have used Docker. Reading through the Lemonade documentation, it seems like a natural migration, but we're talking about two steps for getting started versus just one. So I'd need a reason to make that much change when I'm happy enough with Ollama.
I feel very torn between the “make something” or “buy a Slylight” decision, so I’m curious what makes it better in your eyes, so much so that you don’t think it’s worth attempting anymore. I’m struggling to justify a monthly fee for what I perceive is a daily calendar view with chores.