Not only that, even if you would like to pay, the best model providers could decide any day that they want to save on cost, so they nerf the responses. Then you shipping on time is at the mercy of these companies.
If you spend months shipping slop, because “models will get better and tomorrow’s models can fix me today’s slop”, what happens when they not only do not get better, but actually get worse, and you are left with a bunch of slop you don’t understand and your problem solving muscles gotten weak?
IMO this is the only way model providers can survive in the long run, bank on their users overreliance on them resulting in diminishing capabilities. This gives them leverage to increase prices without any pushback
Good point indeed! I've been feeling Claude Code has gotten worse for a while now, read many articles on it, overall probably due to cost saving. But if you set your things up to depend on it, that becomes a huge issue.
This is part of it for sure. It is also true that many open source business depended on it not being worth the trouble to figure out the hosting setup, ops etc, and the code. Typical open source businesses also make a practice of running a few features back on the public repo.
Now I can take an open source repo and just add the missing features, fix the bugs, deploy in a few hours. The value of integration and bug-fixing when the code is available is now a single capable dev for a few hours, instead of an internal team. The calculus is completely different.
Well, unfortunately people always tend to only spend time on verifying that the feature they wanted works, testing the happy path. Even many superficial bosses / code reviewers / QA tester will check this...
Checking if your code also gets executed elsewhere a bazillion times, checking failure cases, etc... That's a luxury that you feel you can't afford when you are in "ship fast, break things" mode.
> That's a luxury that you feel you can't afford when you are in "ship fast, break things" mode.
I've been there, countless of times, never have I shipped software I didn't feel at least slightly confident about though. And the only way to get confident about anything, is to try it out. But both of those things must have been lacking here and then I don't understand what the developer was really doing at all during this.
I’m on mobile, I’d much rather see some visual demo, ideally video, explaining your product in 60 seconds or less than try to tap around in the live demo.
It's not only about preventing accidents (but I do believe it prevents some to attempt answering your question).
It's also about signaling to someone that they might be doing something wrong or they might not be paying attention. For pedestrians it takes significantly less time and distance to stop, for cars, trams, and bicycles, it takes longer.
It happens all the time that pedestrians don't know the customs of a country, they don't recognize bike lines... in that case the cyclists do not need to pump the breaks anytime a clueless tourist gets in front of them... they can ring the bell, signaling:
"yo, it's not how we do it here, please watch out, I'm coming full speed and you are in the wrong, so please look up from your phone and stop right there".
I also had the luck to meet some people thinking they can be on their phone while cycling, drifting into my lane, etc... In that case, a bell is also adequate
"hey, please stop writing a text message while you are on your bike blazing through the city, you are driving as if you were drunk, pay attention please and stop multitasking (you moron)"
If nothing works to change their behavior, of course I'll try my best and hit the brakes safely, but I'd prefer they learned how to move around in the city safely.
My experiences on a motorcycle tell me that if you feel the need to honk you should be focusing on braking and evasive maneuvers instead.
The choice between between teaching some midwit the law and going home in one piece seems crystal clear to me.
In a couple of years of riding I think the horn would have very slightly helped maybe... once or twice. If the other guy would have heard it at all which is doubtful.
As someone who cycles daily, the bell is less aggressive than a car horn and it's a useful signaling tool about every other day. I need to signal that I'm approaching from behind pedestrians, especially if they are walking without any safe gaps for me to pass them through.
For some rare once-in-a-lifetime friendships, you are not disposable, and if anything were to happen to you, you would be missed. I can count those on one hand.
For most casual acquaintances (that some people incorrectly label as friends), it's certainly true.
On the family's side: only parents, siblings, children, maybe some aunt or grandparent. Second distant cousin you saw 3 times in life?
You may feel this way, but it feels a lot different when you learn that one of your acquaintances has died.
I enjoyed a brief intellectual conversation with a professor at the end of a semester. When I returned the next academic year, I stopped by his office for a quick chat, but his name was no longer on the door. The department administrator told me "Oh, he's no longer with us."
My heart sunk. I didn't know him well, he may not have remembered my name, but I wanted to thank him, and now he was gone. Cut down in his prime? He was just an acquaintance to me, he was not my friend. But I still felt that shock and grief deeply.
I asked the administrator how he'd died, and she quickly clarified: he was still alive! He had just been a guest lecturer visiting for one semester from a Scandinavian university and had now returned home. This has taught me not to delay expressing my gratitude for the acquaintances in my life.
There's a been a few similar instances in my life that have led me take up the personal practice of "Always say hi or wave to friend when the chance comes around, because there may not be a next time". It came about because I tend to see a lot of close friends and looser acquaintances on a day to day basis physically in the world, and there used to be more times than not where I wouldn't bother crossing the street or stopping for a minute to chat. Later I realized this costs me almost nothing, and even for less-close relationships, I'd prefer to have put in the tiny amount of effort to walk up and show them they're worth even that much before they overdosed or moved away or committed suicide. It's not always opportune, but what else is life for?
Granted, in retrospect, there's not really ever a sufficient amount of interaction you could have had, but if I see someone inside a cafe that I'm walking past, it's worth popping in and at least saying hi or waving from outside.
There still is value with the casual acquaintances. Just because a person is replaceable doesn't mean they are not valuable when present. My neighbor who I barely talk to has helped me out when I am in a bind. Even if a new neighbor moves in and replaces him, the original neighbor was valuable and gave me a sense of security, peace, and community while he was present.
I'd rather have my family and 1-2 close friends, and literally no one else, instead of 100 close friends that will vanish as soon as I am not able to bring anything to the table anymore, which will inevitably happen for everyone.
That’s not the point. The point is that the number is small. They are not making a judgment on the value of such relationships but rather that that number is and will always be small that in the grand scheme of things it’s insignificant, it only matters in a person’s immediate sphere.
People on this thread seriously need to stop reacting so emotionally to things. Damn. Grow up people.
The number is small in comparison to the whole humanity, yes, but this is not at all what it's about in this post. Did you read the article?
Instead, it actually is literally about each individual's immediate sphere, which, as you correctly point out, is where it matters. Having 5 true friends in a world with 100 people or in a world with 1 billion people doesn't change anything.
Even there the "problem" was left-pad being used by one or two projects used in "everything".
So the problem isn't that everyone is picking up small deps, but that _some_ people who write libs that are very popular are picking up small deps and causing this to happen.
This is different because it doesn't really say that all JS developers are looking to include left-pad. But I _do_ think that lots of library authors are too excited to make these kinds of dep trees
If you spend months shipping slop, because “models will get better and tomorrow’s models can fix me today’s slop”, what happens when they not only do not get better, but actually get worse, and you are left with a bunch of slop you don’t understand and your problem solving muscles gotten weak?
reply