This feels like a fever dream. As a developer everything changes every week. A new model, a new tool, a new sdk, paradigm we have to learn. I'm getting tired of all that shit.
As a JS developer for over 10 years who has seen multiple hype waves, here is my advice: You don't need to ride the first wave. You can wait until technology matures and see if it has staying power.
For example, React and TypeScript were hard to set up initially. I deferred learning them for years until the tooling improved and they were clearly here to stay. Likewise, I'm glad I didn't dive into tech like LangChain and CoffeeScript, which came and went.
when did that happen for you with React? 10 years ago was 2015 right around the time it started getting popular if I remember correctly (I wasn't a professional yet back then) so I am curious what was the point at which you decided the tooling improved. As a still junior dev I would love to know how to see determine things like that
It's still around, but the hype has faded. Users discovered numerous issues with the project and began abandoning it. I remember one month when everyone was all, "LangChain is the future," and another month when the sentiment became: "LangChain is terrible."
It is but I feel it's main value prop as a developer friendly abstraction layer has been very well solved for by the actual model providers themselves, while LangChain itself have become more bloated, clunky, and to under-opinionated.
The big hype wave has finished now (we still have the "how dare you criticise our technology bros" roaming around though), the tooling is maturing now. It's almost time for me to actually get my feet wet with it :)
With what exactly? They are desperately trying to create a "marketplace" and become gatekeepers on the backs of developers and businesses alike. There's no innovation here.
Knowing OAI's history, only big whales could survive being copied by the platform's owner—case in point: Amazon Basics. They're so big that most of the time, SMBs can't escape them and don't have a choice but to cave to Amazon's demands. Is your product successful? Great, I'll copy you, add the "Amazon basics" label, and start bombarding users with my "product".
Amazon basics is a private label just like Costco and the Kirkland Brand. Same thing with Walmart, Target, Trader Joes, etc. And if these SMBs don't have to deal with Amazon, they will have to deal with a dozen copycats from China for anything that becomes a hit.
For me the most annoying thing is APIs arbitrarily changing all the time. Completely change the entire Tailwind, ESLint, AWS SDK, etc APIs every 6 months? Why not! Heaven forbid you don't touch a project for a few months, blink and all your code is outdated.
nothing really changed much here though. re llms nothing really has changed either, its mostly just scaling. there is really not much to learn as a consumer and app builder.
Like "Abort, Retry, Fail"? And same as there, what's the difference between the first and the third? Is there a way of accepting a new sdk every week without specializing?
I don't understand, how can you acquiesce to a situation whereby "As a developer everything changes every week"? Not even the most "on the bleeding edge" JS developers can switch frameworks every week, and the pace is continuously accelerating. As I see it, the only way to stay sane and productive is to specialize to a sub-area where you can stick to a technology for at (the very) least 3 months.
