Perhaps there are some mitigations for this I'm unaware of?
294 karma · joined April 26, 2021
Perhaps there are some mitigations for this I'm unaware of?
For example I asked chatGPT about birds that can't fly and it started bullshitting about all sorts of birds that clearly can, those facts would likely be in the KG.
Meta are trying to force AR into the world, like trying to produce a baby in 3 months by having having 3 women. Maybe they are close, maybe they are producing a load of useful research for someone else to exploit in the future. Apple supposedly bringing out their thing 'this year', but there has been little exposed of it, maybe they are just egging on Facebook to waste there time/money .. time will tell.
Like you probably have something called an iterrable in your programming language of choice, so why not just call it a linked list, or a vector, is basically the argument you're making in my opinion.
To be fair, I do find some modelling languages do disappear into too much abstraction, they basically end up like being a Upper Ontology [1] and lack instances/examples that make them approachable in practice.
This argument gets thrown up by someone nearly every time documentation gets mentioned.
1. Does it matter if not entirely accurate with the as-is? It showed the previous state or intention, that is typically very useful and a lit better than nothing.
2. Your unit test are out of date when your change code yet that typically gets updated, or new tests added, and is typically more work than updating the docs.
3. If what you document is so wildly different to the solution, you're probably documenting too much detail (this is where most junior devs go wrong), if it's that your arch has actually radically changed it sounds like your documenting too early, do you do spikes etc to figure out your arch before you commit to it?
All the comments here have been great validation, that there is others with a need, which is encouraging.
I've mostly been working on the data aspects, so not much to see as yet, but if a new approach to this is of interest to you, please signup.
I think the other solutions out there focus too much on note taking, and manually organising stuff, hopefully I can create something more compelling for the rest of us!
Although the definitions are some what murky, this is the generally accepted model.
I think what you are talking about is personal knowledge management.
A trap that sometimes gets laid out is it a binary build or buy decision, there is typically options in between in my opinion. Build isn't necessarily as onerous as it once was either, the use of cloud, frameworks, libraries, low code products and SaaS means you can often construct something from these legos.
In my experience, there are some in enterprises with procurement and IT management skills who tend not to have a clue about building modern software, and often push for buying stuff (keeps them busy), and sell it as a win, bought a thing, set it up, declared victory and fucked off to the next project leaving the users and technologists to figure out how to unfuck the mess that has accumulated around this clunky COTS product that is now a critical part fo the business.
half joking I don't really know much about languages, I just don't see how a graphical programming model would be better than a text based one in expressiveness or compactness?
It's more than just a graph database, which is typically misunderstood by most devs (including me), when they start looking at this.
However designing an Ontology is hard, just as getting a good database schema is hard, failure of most systems is the data model builds up tension over time, which leads to code complexity/hairballs, effort in adding new concepts to the model, operational work arounds, which then start to poison the data quality (start adding freeform text to store 'data').
There is no god given ontology or one way of modelling the world, crowdsourcing is a good approach, but looking at this one you can see some questionable practices (tradeoffs to be fair), and there is a big gap in people who have skills and experience.
Problem with so much syntactic sugar is you need to retain/recall the semantics of the vocabulary. As a polyglot programmer who doesn't write much code anymore, it slows me down.
I suspect the 'Top Mathematicians' are not those that are best at calculation, like you might get in Olympiads, but those which are able to apply maths to solve real world problems or produce creative breakthroughs. Being good enough at calculation very likely helps, but isn't sufficient.
On a more practical aspect, you don't want to relearn the feel of your trucks, and for what benefit, if the word was they grind better, or are lighter without a reduction in strength, maybe, but neither are likely to be more than marginal. Also skaters can be a bit superstitious, have a crap session, blame the stoopid new fangled trucks.
Anyway may take on it, but not skated for years.