I think its worth noting that inconvenience aside, the high rate of theft and stock loss is correlated to item price increases overall -- even above inflation.
Watched a man walk out of Safeway with two 12-packs under his arms makes me understand why eggs are $8 a dozen.
No doubt that there have been poor teaching experiences, but I would counter that my experience with EdTech teachers has been amazing and empowering. Really don't think we can tar all the teachers with the "EdTech sucks" brush.
Aside from the Knowledge Graph buzzword, isn't this exactly the same idea as Tim Berners-Lee and the Semantic Web back in 2001?
- web of resources, not pages
- ontology-based schema
- RDF based encoding
- URI (IRI) resource identifiers
- Automated agents and reasoning (DL) support
Considering the ensuing reception and general avoidance of the semantic web outside academic papers, I guess no one wants to talk about it.
Very interesting article and helpful to visualize the layers and perspectives in and more comprehensive architecture diagram. I would add that the layers of abstraction could also be represented in a standard Semantic Web OWL ontology which would capture a lot more context and sematic detail related to hierarchies, concepts, classes, and object property relationships. Picture are great, but it's always a struggle to get them complete.
I agree with you, but I read this as:
> No process and tools
> No / limited documentation
> No RACI or alignment (yay, kumbaya)
> No plan or managed dependencies
I'm not saying this is the outcome of an Agile approach, but sure seems common on the Scrum projects I work on.
I would venture the implied discussion is about more than shipbuilding. Resources, labor, regulation, and other factors raised in the article are endemic across lots of areas and seems symptomatic of market forces and government policy. As a counter argument, I have to ask why the U.S. needs to build ships faster, larger, cheaper than other countries? The U.S. certainly seems to be able to build infrastructure and housing reasonably competitively.
I hadn't heard the term "architecture astronaut porn" before. Seems highly accurate in this context and wondered if you could point me to other resources on this term?
Good article on the high level concepts of a knowledge graph, but some concerning mischaracterizations of core functions of ontologies supporting the class schema and continued disparaging of competing standards-based (RDF triple-store) solutions. That the author omits the updates for property annotations using RDF* is probably not an accident and glosses over the issues with their proprietary clunky query language.
While knowledge graphs are useful in many ways, personally I wouldn't use Neo4J to build a knowledge graph as it doesn't really play to any of their strengths.
Also, I would rather stab myself with a fork than try to use Cypher to query a concept graph when better standards-based options are available.
Paywalled, but not a huge surprise really. Sounds like part of the problem was the internal pharma team not having a plan for what to use CoPilot for and going for the "it's AI!" theme from Microsoft.
I am seeing great value in AI-based solutions related to knowledge assistants and for automation N(A). Neither of these seem like strong suites for CoPilot, but it's very early days.
That we're seeing much better results using self-hosted open source models (Llama 3.1, etc.) should be concerning for Microsoft as well.
>> The attitude this instills is that of having to work hard, while scheming against the taxman, to improve your life.
Sounds like a lot of politicians I know. Really, how is this not being "Smart" and gaming the system? If we're all upset about being "fair" then we would have changed the system.
To take this a different way, Devs need AI-driven system design tools, not diagramming tools. The work to automate the process to define, code, deploy, and document tech/app solutions using GenAI is arguably well underway and the days of humans producing layers of boxes and arrows documentation is thankfully numbered.
More directly, the need for the special snowflakes and the ensuing complex system design processes will be reduced as we drive towards more automation N(A) frameworks.
These are great questions and match my conclusion after many years of big5 management consulting: (A) Organizations are not optimized towards efficiency or value, they are optimized to align power between the executives and their self interest. Any heterodox organization with virtuous claims of egalitarianism will quickly reset to the default (A).
Wholeheartedly agree, however... It's well accepted that most developers would rather chew off their own arms than write documentation. The acceptance, sort of, of TDD shows that developers would rather code even in pseudo code test languages than write narrative prose.
Some much this. If executives were held accountable and terminated for performance failures resulting in layoffs rather than rewarded with earnings bonuses I would feel more sympathy.
Kudos for sharing this and the implementation details.
I guess I'll never get over not liking Cypher queries or the other ways property graph engines query the graph: (MATCH path = (s1:Station)-[r1:CONNECTED_VIA {line: 'U1'}]->(s2:Station))
Seems like standard SPARQL and RDF* work better for me.