We provide an executable, governed semantic state in which data, entities, provenance, rules, missions, and agents are first-class participants and can be discovered and compared through a common ontological namespace.
After OpenAI stole the navier stokes work it is obvious that big orgs and universities will need to have their own AI centers running their private IP just like they have their own supercomputers.
Imagine being a big pharma company using ChatGPT rn.
That is urgent.
@JyiscS@bubbleboi Not sure how they train on code. All I know is code is a vehicle that wraps and transport the actual knowledge, mostly write in turtle format for easy execution. This is far from procedural code.
@JyiscS@bubbleboi Data and knowledge part is entirely a Librarian field of expertise. Computer science sits as a layer above data and knowledge engineering. CS provide the machinery to execute what a library curates. That's why in most institutions these courses are CS and Informatics.
@mattpocockuk Knowledge management demands governance as first class citizen. You cannot hallucinate a fact. Anything not supported by verifiable source assertion is treated as noise.
If you ask an LLM a question, it predicts the most likely next token based on training weights. Its "truth" is an illusion born of interpolation. It can hallucinate a corporate financial figure because, statistically, it sounds correct.
A Peculiar Librarian says:
-here is an ontological schema,
- a SHACL validation gate,
- and a 1:1 fact contract.
The fact is verified, cross-referenced, and absolute.
A Peculiar Librarian says:
-here is an ontological schema,
- a SHACL validation gate,
- and a 1:1 fact contract.
The fact is verified, cross-referenced, and absolute.
People think the hardest part about building tech products is writing code , i might be wrong but i tend to believe the hardest bit is actually engineering/ architecting a system.
Code is a language, engineering is a state of mind ( ideas, philosophy , logic )
I think if I was to advise a newbie coming into tech now, Iβd advise them to go into anything that relates to data.
Data science, data analytics, data engineering, ML engineering, etc.
But specifically, data engineering.
Why?
The truth about the matter is that we are in that phase where most of the applications being built are becoming highly data-centric.
We are generating massive amounts of data from users, transactions, logs, events, IoT devices, AI systems, APIs, you name it.
And somebody has to make sure all that data can actually be collected, cleaned, transformed, moved, stored and made available to the systems that need it.
That is where data engineering comes in.
You start getting into things like ETL/ELT, data warehouses, data lakes, streaming, Kafka, Spark, Airflow, distributed systems, cloud infrastructure and real-time pipelines.
And with AI becoming even more prominent, this is becoming even more important.
Models are only as useful as the data you can reliably get into them.
So if I were starting tech from scratch today, Iβd seriously consider building my career around data.
Not because other areas are dying.
Far from it.
But because almost every serious technology company is eventually going to have a data problem.
What most call "Machine Learning" is mostly just probabilistic guesswork wrapped in massive marketing budgets. They throw compute at messy data and hope a neural network finds patterns but what they get in return is pure hallucinations.