Looking at "hard facts", the yield curve is in the "most inverted" position in a LONG time. I'd still be cautious.
1,944 karma · joined May 4, 2012
@santiagobasulto on Twitter.
Want to try DataWars? app.datawars.io/register
Want to reach out? santiago [dot] basulto [at] gmail
meet.hn/city/45.0677551,7.6824892/Turin
Socials: - github.com/santiagobasulto - x.com/santiagobasulto
---
Looking at "hard facts", the yield curve is in the "most inverted" position in a LONG time. I'd still be cautious.
The issue is all the libraries and packages that were built around it. It's now been YEARS of building on top of the GIL.
So anyways, PEP 703 is a a nice effort, but I doubt we (everyday mortals) can enjoy it. Meta, and big companies with a specialized team might be able to exploit it by making sure their entire stack is GIL-free.
EDIT: My bad, the talk is from Larry Hastings: https://www.youtube.com/watch?v=P3AyI_u66Bw
the one from a MS researchers that has been recommended to all of us probably. Good video btw.
There are some AI Engineers with strong scientific/mathematical background, but that's rare. Usually, you're paired with these ML people that actually develop and evaluate the models.
So my advice is to start with Data Engineering and then find a specialization AI. You should have a VERY solid foundation on scripting and programming, specially Python. Also, a lot of concepts of "data wrangling". Understanding how data flows from point A to point B, how the intermediate storages and streaming engines work, etc. Functional programming is key here.
I also like to follow Tobi Lütke. The guy is the founder/CEO of Shopify (with all which that might entail), and he still tweets amazingly interesting low level coder stuff.
EDIT: I think it included an example of NYPD under Rudy Giuliani LOL :)
We're not monetizing this in any way, it's just an MVP we're building.
If you're hiring Data Science/ML Engineers/MLOps candidates, and you want to either do a technical interview during the process, or you need to do a "Skill Gap" analysis once they're hired, let me know.
You just tell me the technologies that your company uses and I build tailored projects for candidate to resolve. Then submit a full report on their strengths, weaknesses and the aprox time for them to catch up (if any).
We've restricted all outbound traffic since then.
The process roughly is:
Ingestion:
- Process embeddings for your documents (from text to array of numbers)
- Store your documents in a Vector DB
Query time:
- Process embeddings for the query
- Find documents similar to the query using distance from other docs in the Vector db
- Construct prompt with format:
""" Answer question using this context: {DOCUMENTS RETRIEVED}
Question: {question} Answer: """
Is that correct? Now, my question is, can the models be swapped easily? Or that requires a complete recalculation of the embedding (and new ingestion)?
I have several consoles open in different monitors and sometimes I accidentally run commands in some because the focus is in some other one :/
I'm not saying this is right or wrong. It even sounds a bit dated to me. But that's the underlying reason.
Podcast: https://open.spotify.com/episode/6RZm7V8IcvuMuaCmVBE4EG?si=v...