I can't wait for the days where LLM written articles are indistinguishable from real writing, so people stop complaining about this. I am giving that another 6 months. In a lot of cases its not just lazy prompt -> article, but rather text synthesis through LLMs -> article. But people will still complain /rant (bias: I run a blog with only AI written content, but a loyal audience).
Of course, I guess then this post is more about the category of apps where it doesn't matter that much. But there are still a ton of apps where all they are doing is bringing together a bunch of API keys and profit the difference.
Yes absolutely. A lot of these apps are surface level great, but the you dig deeper and its really just as easy to build the same functionality yourself. Keeping in mind that these are all decently well funded projects.
Often the "issues" aren't even bugs, its more the realization that I want some sort of functionality that they do not have; and immediately realize that if I spend a weekend on my own "base system" for that use case of SaaS; I can just attach anything to it, rather than waiting for them to release something new in 1-2 months.
Copyright is so-so. At the end of the day you can say that the complete work (not just snippets) is something copyrightable. But the most bananas thing for me is that one can patent the concept of one click purchasing. That's insane on many levels.
The automation which allowed 99% of the jobs to disappear, will be responsible for (pulling this out of my ass, to get a point across) 90-200% of the new jobs which we now can do.
The funny thing about Langchain is (and a lot of developers will attest to this), is the more "serious" your application becomes, or your app becomes production ready. The more you start to understand what Langchain is doing, and you will start to rewrite the custom classes to your own ones, and the custom logic to do your own stuff. Until at some point you realize, that you don't need a wrapper for an API, and can do everything with about 10% of the code.
Langchain is like a backwards 101 course into APIs for LLM's, where you start out trying to learn a new framework, but through debugging sessions end up understanding whats really being done.
Yes, I do post in these hiring threads as well as freelancer threads on my personal account every month. I have been working with two companies, and have invoiced them for nearly $200k in the past ~2 years for development and consulting work. One of them is a startup, the other a software shop for startups. All web-dev & api work. In both cases, they reached out to me. I have had no luck reaching out to companies in those threads.
If all you knew was Rust, then getting a job in this already harsh market would be much harder. It would be easier if you knew ML, but it does really depend on what else you bring to the table. So, what else do you know? The job market might change on a dime, make sure you don't just learn the latest hype cycle of frameworks, languages or try to optimize for hiring right now.
I am a backend engineer who have experience building microservices and data pipelines for more than a decade. I felt AI/ML is a natural expansion to my skillset as I currently work on Scala, Apache Spark, Kafka and some Golang.
Yes, then I would go the AI/ML route. I'm also mainly a backend engineer. I considered investing time into Rust as well. But employability is questionable. I'm already in the AI/ML field, so I chose to get more experience in the sales & product side of engineering.
reply