Ozymati @ Ozymati @lemmy.nz

https://www.instagram.com/heretherebe_dragons_wellynz/

---

Read more

Posts

5

Comments

286

Joined

2 yr. ago

Very stylish

So awesome!

28, according to google

It's hot here in the Hutt

It's warmer than expected today

Not having to pay a redundancy package? Or just sociopaths in the management team.

Fantastic!

If I can brain my way into cutting down the total amount so I can just make a sample without having to sterilize jars etc I may give it a go

Hm, might watch for a chance to play this

Got a recipe?

Sure did.

So how's the gameplay on Five Tribes?

That sounds potentially delicious though

Managed to catch my calf with the corner of the car door this morning. That's gonna leave a mark...

dunno, but surely there is a name for it

People soup

Yep we can do all kinds of stuff that the account user will not notice at all (unless of course they fail a check) while having to do an ID validation is very noticeable.

You can trust them within a framework of expectations. Bureaucrats gonna bureaucrat, and it's not a monolith. The level of mistrust should rise steeply with the level of money that can be made by being in a given governmental position. Do I trust rando post office employee? Sure, they're just some schmuck with a job. Do I trust a congresscritter? Oh hell no.

Yeah I don't wanna go back to work. whinges in corporate

When I get back I have to try to unsnarl an issue with user identification and access to client data where the user login is mediated by a separate app (SSO as part of a whole other project that is going on). The current requirements call for a verified identity from the admin user at account creation which puts the requirement for ID validation outside of the app my team is trying to implement. However, it has been pointed out (quite legitimately) that doing that puts up a barrier to account creation.

I'm of the opinion that we could track ID verified users downstream in the user profile in our app instead, which not only lets them get in the door nice and easy but also gives us future options about just how aggro we want to be with having an actual identifiable human associated with an account.

However, doing the legwork to validate my opinion is going to be a huge PITA. Also the vendor is onboarding next month so in addition to this nice little mess I get to revalidate pretty much all requirements against the actual capabilities of the chosen platform. Including the idea I have that we could incorporate an admin user ID verification step into profile creation. Le sigh. At least I have a minion to help.

And I don't know maybe the project director will swoop down accompanied by a beam of heavenly light and angelic choir to tell us we don't need ID validation at all....

I guess going back to work is a bit of a mixed bag.