I’ve heard about people being encouraged to use AI-Tools and monitoring how they are used is good to identify if people are actually more productive with it, but forcing people to use it seems like forcing a gardener to use an excavator where a shovel would have been a sensible option.

and atleast so far the experience at work is, that stuff that the AI can handle somewhat reliable, we have determinstic tools for. guess working a boring java job has its perks :D

who gets fired if they don’t use garbage generators?

knowing where something happens is not knowing what happens and especially not knowing why it happens.

A big import of data caused a specific datapoint to be inserted twice into the database, but that only happened in our shared testing environment not in our development environment, logs made it clear that we tried to insert something twice into a join table but not why.

the fix was easy, we can remove the duplicated datapoint from our data before writing it to the database, and we found an edgecase we can handle further upstream so we don’t end up duplicating it in the first place, but why didn’t we run into this issue in dev?

the data is consumed from a kafka topic with a single partition and read order is allways the same as write order, so our service behaves the same way if the same data is written to the topic everytime, but it turns out the producer does not necessarily write in the same order to the topic given the same input and gaining that understanding was a goose chase with debuggers, logs and combing through code of multiple services written by multiple devs working at multiple companies and thats the true horror of enterprise development jobs, teying to get someone from a different team or even company on the phone who can actually explain something to you with whom you can analyse a bigger part of a system.

that just seems like putting the same work into ‘spec’ i now put into code, but having to hope the ai produces something usable, and not like something that would save actual effort.

my boss is going to love that though…

does authentik offer an option to preview a jwt for a given user? might be as simple as that the claim is not named “ocisAdmin” or is not a toplevel entry in the jwt.

not an authentik user, but after skimming their docs i think you have to:

1. create a role “ocisAdmin” via authentiks admin interface
2. give this role to a group in the admin interface or create one.
3. assign a user thats supposed to be an owncloud admin to the group

it might be that you also have to define somekind of mapper to include this in the informations owncloud receives from authentik, but as i said i only skimmed the docs and would personally just try it without the mapper.