> The AI ecosystem will continue to be Python-first, and that’s fine! The actual interaction with models is just HTTP requests with JSON payloads, though.
Wow, all this time I thought transformer neural networks required expertise and specialized hardware to design, train, build, and operate. Apparently all you need to do is make an HTTP request. We've been wasting our time! /s
If your idea of "building AI" is calling someone else's web service, you might want to consider scaling back those grandiose claims on your resume. You're building a basic app that makes API calls, stop fooling yourself.
I mean, AI is just matrix multiplication, amirite?
Pretty reductive argument honestly. AI services mean that a lot of AI operations are 'just HTTP requests' but it doesn't mean there isn't a huge amount of tooling that you need to work effectively with them.
AI tooling in this case being:
- Fine-tuning
- Eval test suites
- Observability based around AI interactions
Would you call Lovable a basic app that makes API calls? Or is it AI enough to justify the label?
Yeah there a ton of real AI work happening. And there's a number of apps that use the AI work. I don't think you can conflate the two.
Making a web page with Google Maps doesn't make you a satellite data engineer. Doing a query against a database isn't "RAG", it's just a query.
It's an API call, y'all. Making API calls to external AI services is a totally legit thing. I do it all the time. But I don't call myself an AI Engineer.
My advice would be to NOT pad your resume with AI-laden verbage unless you actually work on building core AI technology. If you build apps on AI, congrats, get in line and call yourself a software developer.
Readit News
Wow, all this time I thought transformer neural networks required expertise and specialized hardware to design, train, build, and operate. Apparently all you need to do is make an HTTP request. We've been wasting our time! /s
If your idea of "building AI" is calling someone else's web service, you might want to consider scaling back those grandiose claims on your resume. You're building a basic app that makes API calls, stop fooling yourself.
Pretty reductive argument honestly. AI services mean that a lot of AI operations are 'just HTTP requests' but it doesn't mean there isn't a huge amount of tooling that you need to work effectively with them.
AI tooling in this case being:
- Fine-tuning - Eval test suites - Observability based around AI interactions
Would you call Lovable a basic app that makes API calls? Or is it AI enough to justify the label?
Asking as they made a move from Python to Go just the other day for similar reasons as in this post: https://lovable.dev/blog/from-python-to-go
Making a web page with Google Maps doesn't make you a satellite data engineer. Doing a query against a database isn't "RAG", it's just a query.
It's an API call, y'all. Making API calls to external AI services is a totally legit thing. I do it all the time. But I don't call myself an AI Engineer.
My advice would be to NOT pad your resume with AI-laden verbage unless you actually work on building core AI technology. If you build apps on AI, congrats, get in line and call yourself a software developer.