210
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 23 Jul 2024
210 points (95.7% liked)
Asklemmy
44151 readers
770 users here now
A loosely moderated place to ask open-ended questions
Search asklemmy ๐
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- !lemmy411@lemmy.ca: a community for finding communities
~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~
founded 5 years ago
MODERATORS
โIโm trying to identify a source of truthโ
As someone who had to work on syncing multiple databases of customer and order data this was actually very important for me to know. Turned out that it could vary on a field by field basis and could also depend on the type of customer and where they came from.
To sync up our new and shiny SAP CRM with several Access databases and our customer-facing software I ended up writing a script that would collect all data field by field with varying hierarchies and writing it back out to everything. Worked surprisingly well.
Is Access still in use?
Access will probably be the last thing to die before the heat death of the universe.
Even after things inappropriately hosted in Excel? Lol
Oh, yeah, forgot that.
I'm certain the access database living in a broom closet that someone setup 20 years ago is still going strong at my last job. It was also fed by mainframe dumps, I'm super glad I never had to go anywhere near the thing personally, different department and it was explicit that they owned it.
I think that's better than one department (with the clout to do so) going "this is going to be our source of truth" while completely unprepared for what it means.
They literally spent over a year in talks with the whole rest of the damn company about what that would mean and what level of responsibility that would entail, delayed the go live multiple months multiple times... and they still can't do fucking basic data validation.
Leading and trailing spaces. Names randomly in all caps.
Oh, there's a shit ton built off the requirement that this field is one of these options? Surprise, we silently added another option without telling anyone, after we agreed in planning that option was invalid. Not our fault, your fault for building shit based off the idea this was a source of truth and we actually took requirements seriously.
Why is everyone coming to us to correct this data? Why can't you just correct it downstream like you used to? What do you mean we were warned? I wasn't paying attention during that meeting that you held specifically to warn me about this in advance because I was too busy ignoring all the other warnings people were telling me!
What do you mean that the thing you warned us would be consistently be delayed until next day because of how our source of truth works can't be done on demand on the same day? Huh, we signed off on it being okay, along with every other relevant department?
It's supposed to be a good practice ... in theory. In practice nobody knows what exists and who's in charge of what and there's exceptions and exceptions to exceptions.
Speaking for software engineering perspective. I see in other comment you're doing process engineering, I assume the term is used in a similar way
Wait, do you work at my company?
What's your job?
Process Manager
I googled "identify a source of truth" and was treated to a plethora of buzzwordy tweets and articles worthy of Deepak Chopra.
I'm so sorry.
Letโs put a pin in it, and we can circle back when we have more bandwidth. Hopefully itโs not too heavy a lift.
Oh Ffs kill me I hate this nonsense.
I used to work with enterprise customers at a SaaS company, and still have a lot of anger in how corporate types use this fluffy language. I think my "favorite" example of this jargon is "Please Advise.", which basically just means "What the fuck?!"
Well, that's a new one (assuming it's not referring to a physical object) to me
First we gotta TOUCH BASE
https://www.youtube.com/watch?v=l8HnJHiu9d8
(warning: RCR, audio probably NSFW)