108 karma · joined November 28, 2017
Outcome? Everyone on their own self-hosted git servers, zero collaboration.
Let's say I had a promotion, who changes my title in the system, who changes my responsibilities and my place in the org chart, more importantly, will they do it or is <HR_NAME_HERE> on leave and forgot? those are data points required by the agent to determine if I'm "good enough" to access a certain resource.
What if... someone spoofed my address and did a flood in one of the resources that are lateral to what I'm allowed to access (let's say I don't have access to company sales but I do to department sales and the attacker floods company sales with requests under my address), would the AI determine that I'm a high-threat actor and not allow me to access legitimate files going forward?
Will exceptions be made by humans? In which case we go back to human-managed permissions.
Sorry, I might be barking up the wrong tree but I think these are questions that are not meant to be solved during implementation. And they add to what @firasd said about legitimate-but-odd behaviour
Unless I gravely misunderstood the text, this seems like a terrible idea (fancy non-scifi, but still terrible)
That said, certain sectors like software (as in custom enterprise grade software dev) pull revenues that are much much higher sitting around 35%, but it's not that common.
The first mistake was management not wanting to pay for Neo4J, so we were working in production with the free edition (no backups, only one database, lots of limitations).
The second error was that none of us had production level experience with Neo4J apart from what you just said, tinkering in toy projects at home or very low stakes services, so in the end, the schema that was created was a bit of a mess, you would look at it and say "well, it makes sense..." but in reality we were treating Neo4J as a twisted NoSQL/SQL interpretation.
The third mistake was treating Neo4J as a database meant to handle realtime requests from thousands of users doing filtering and depending on huge responses from external systems (VERY OLD systems, we're talking IBM AS400 old) while in an environment where each response depended on at least 2 or 3 microservices. We had one cypher query to handle almost all use cases, you can imagine what a behemoth that was.
In the end as I said, compound error between lack of experience, not analyzing correctly our needs and a "just go with it attitude" that to this day I'm pretty sure it cost quite a bit to the company. Eventually the backend team managed to move to MySQL (by that time I had moved to Ops) and the difference was abysmal.
Nurture this, it will become a great tool in the belt for a lot of people
We need to reduce the entry barrier (it's meant for companies so it needs explicit registration) so anyone can use it as a proper SaaS but so far we already have a couple clients :D
Maybe it's my own personal working culture, but when I get into a company I'm not thinking about levels, growth, stock options... I go there with a salary, a position and a willingness to help in whatever I can, once I'm not needed anymore (it's usually a combination of managerial direction changes, new hires, new objectives) that's my cue to help somewhere else where I may be needed or wanted. Am I that weird? I honestly don't understand this culture of quarter finance agent, half developer, quarter manager aspirant :/
While I was working on the tablet interface (in Godot Engine) I put Claude to work on what after two minutes became a full product on its own with a new file format as well. Tell me what you think! (so far the response is meh...)
Fortunately I still only have a couple clients so no one was the wiser.
UPDATE: It ended up in a simple scare, nothing was affected and I'm not in any list that I know of, in case you're wondering