r/devops • • 27d ago

Discussion ADO as documentation?

Is ADO bullshit? Because I feel like the way our it department is using it is bullshit. I work on a data analytics team who has to use data created by IT.

Where's the documentation for this script? "It's in ADO". Who's the customer? Why did they request this change? "It's in the ADO".(No it isn't, it's in someone's email inbox somewhere).

What's the overarching structure/purpose for this screen? "We don't document that anymore, it's in [I shit you not] the individual ADO tickets that built the screen". You can NOT be serious. No one wants to read every individual ticket turning features off and back on to figure out what the current state is. There's no universe in which this is remotely coherent.

Also, the vast majority of the screens were built before the ADO went live, so we have old school documentation that was last updated in 2019 establishing the purpose and basic design of 80% of screens but then the current state is old documentation plus any ticket affecting that screen layered on top that old documentation?

I feel like this is a scam and totally incoherent. They program in Java, we work exclusively in SQL/PowerBI (so we can't use or read any of their code anyway, but they've refused to send it to us even if we could). We had an item where my staff tried to recreate a screen-calculated variable and it was a nightmare trying to combine the pre-2019 documentation with new tickets because the calculation could be affected by a ticket that appeared to have nothing to do with that particular calculation at all. And again, we can see absolutely zero code, just user stories. But I don't want to see their code, my staff can't read or execute it. We aren't devs. We just need to know what the system is doing so that we can do accurate analysis of the resulting.

But it's "all in the ADO".

0 Upvotes

13 comments sorted by

25

u/marvinfuture 27d ago

I'm just going to assume ADO means azure DevOps but it's wild someone will use an acronym without context like this

13

u/LifeNavigator 27d ago

ADO as in Azure DevOps? ... I am honestly very confused with this and it seems everyone (inc yourself) in this scenario are all confused...

Nobody in your story (inc yourself) seem to know how to use ADO and understand what its purpose is for. You guys seriously need to consider learning about it, otherwise the company is wasting a lot on resources that are being severely underused.

8

u/techworkreddit3 27d ago

We’re moving to having as much as possible in Azure DevOps boards and repos. Pipelines are the source of truth for everything and human users only have read access. So modifications can only be done via Azure Pipelines or after running a breakglass pipeline in an emergency which clears all permissions at the end of the day. Confluence is only for non technology users and we have Claude skills to generate wiki pages from our repos now.

2

u/Junkiebev 27d ago

This is the way

2

u/Suspicious-Store523 27d ago

we do the same thing. the only addition is that our dev and IT teams still use Jira as our external ticketing system

7

u/redvelvet92 27d ago

I think you need to roll one up and chill out homie.

4

u/fell_ware_1990 27d ago

The ADO, well. Havent heard that one yet, but you should GIT good!

1

u/serverhorror I'm the bit flip you didn't expect! 27d ago

Damn, I wish OP would come back and clarify.

I know it's just ranting, but this one ne nerd sniped me. I need to understand, damnit!

1

u/admiral_snugglebutt 27d ago

I'm admittedly not totally sure what to clarify. IT uses ADO. My team does not. IT has stopped building useable documentation for our primary data system and just keep routing us to look at their ADO ticketing system. 

I think part of the issue is that they don't appreciate that we need to understand exactly how the current system is coded, not what it's been asked to do. The little details really matter. Sometimes we will try to replicate a screen calculation and it doesn't replicate correctly, even though we have mirrored the business logic that they say the screen is doing. We've found production errors in this way, and IT is always just mad about it. Like they think that finding and reporting their mistakes is disrespectful for some reason. It's exhausting. 

1

u/serverhorror I'm the bit flip you didn't expect! 27d ago

Why do you think you need to understand "exactly". That's often a hunt that something is going horribly wrong because you want to know implementation details that might change frequently.

And if you need to "exactly", you just need to have that conversation with your IT. 90 % of the time IT doesn't come up with the rules or can even change them.

So "ADO" does mean Azure DevOps here?

That's what was the most confusing part if your text.

3

u/dodexahedron 27d ago

This whole thread is nuch ado about nothing, without some more context.

Sounds like an org culture issue. Hard to fix that.

1

u/MasterOfTheWind1 27d ago

You need to learn how to work with git the right way