←back to thread

IBM to acquire Confluent

(www.confluent.io)
443 points abd12 | 10 comments | 08 Dec 25 13:43 UTC | HN request time: 0.433s | source | bottom
Show context
theta_d ◴[08 Dec 25 15:07 UTC] No.46193066[source]▶
I worked for IBM Cloud about 6+ years ago. While there, we had to connect to a Softlayer VPN to get into our Jira instance. My VPN account and Jira account never got provisioned so I couldn't connect nor see the Jira board. My team-mates couldn't even assign a ticket to me b/c of this. They would just put my initial's in the ticket summary and send me a slack of the details.

It was right before I left that we got our own Jira instance. This was all around the time of the Red Hat acquisition. I remember the announcement b/c we used SuSE for everything IIRC.

replies(1): >>46193552 #
1. askafriend ◴[08 Dec 25 15:42 UTC] No.46193552[source]▶
Why didn't you ask to get the accounts provisioned?
replies(7): >>46193758 #>>46193939 #>>46194446 #>>46194841 #>>46194872 #>>46196123 #>>46197272 #
2. Reubachi ◴[08 Dec 25 15:54 UTC] No.46193758[source]▶
I imagine that's done via JIRA tcket/IT before onboarding.

So if they somehow can get past initial device deployment/user account logon, and get other resources IE; slack....well that speaks to how difficult/pointless it would be to get proper VPN/Jira access.

replies(1): >>46196145 #
3. esafak ◴[08 Dec 25 16:06 UTC] No.46193939[source]▶
You'd have to be able to find the person to do that first hehe!
4. ecshafer ◴[08 Dec 25 16:42 UTC] No.46194446[source]▶
What's the largest company you've worked for? A lot of big, older companies, are just so messed up that its just not worth it. How do you do this? Well you have to find the specific form, or specific person who does the thing, who is that? no one knows. So that provisioning of a vpn and getting in jira might literally be like a month of work.
replies(1): >>46194609 #
5. thinkingtoilet ◴[08 Dec 25 16:54 UTC] No.46194609[source]▶
I've worked for S&P Global, so pretty large. If you don't have an account that you need, then you need to be tenacious, which of course is super annoying. If you don't have an account on a system you should, it's 100% on you after a while.
6. prmoustache ◴[08 Dec 25 17:11 UTC] No.46194841[source]▶
I work for a company that has so much bureaucracy and silos that teams maintain wiki pages with links and routing on how to create tickets for specific tasks and wether there is a specific mandatory information needed in order to not have your ticket just closed as incomplete without an explanation.

Sometimes a team unilaterally decide to change the process, info is sent to a random number of mailbox/managers who may fail to pass the info. Some entire teams just put themselves in away status 24/7 and do not respond to direct messages.

So yes I can believe his story. Sometimes in these kind of companies you just don't know who and how to ask for something and you just hope someone knows someone who might know.

7. Zigurd ◴[08 Dec 25 17:14 UTC] No.46194872[source]▶
On consulting engagements, 0% of the time are Jira and git provisioned correctly for an outside consultant. I used to be appalled at being paid for two or three days of waiting for the IT guy to fix this. Now I use the time to find cleaning supplies and deep clean my cubicle and chair. People do look at me funny, but I feel better not just sitting there reading.
8. theta_d ◴[08 Dec 25 18:51 UTC] No.46196123[source]▶
I did, multiple times. I was a contractor. I was the only one on my team of contractors whose account was screwed up. There seemed to be no priority to do anything there. One of many many reasons I left when I could.
9. theta_d ◴[08 Dec 25 18:53 UTC] No.46196145[source]▶
I believe it was an ancient ServiceNow incantation that all the current employees couldn't seem to hunt down.
10. bongodongobob ◴[08 Dec 25 20:34 UTC] No.46197272[source]▶
I had a similar thing happen to me with a huge company as a contractor. I couldn't work for 3 weeks due to a combination of login issues and permissions settings. Couldn't file a ticket and no one was really sure who to call/ask. Finally a director caught wind of it and knew who to talk to.