Noodleface
A Mod Real Quick
- 40,561
- 20,641
Ah yeah I think this is probably part of the problem. Also sounds like you're working off hours too - what if you just stop doing that?
IT/Software career thread: Invert binary trees for dollars.
- Thread starter Traak
- Start date
- 17,860
- 8,797
I honestly don't know. It's a fair question and I don't know why I'm not more insistent about sticking to regular working hours despite being sick of it. I've become more non-confrontational as I've aged and I don't like letting others down. Off hours work is often catching up on stuff I feel is blocking others, like reviewing MRs. AI has made that worse recently.
Control
Avatar of War Slayer
- 6,436
- 17,848
as much as i loath meetings, especially in the office, this is one case where a big whiteboard with all of your sprint postits comes in handy.
"great! i'll get your 10 new postits added right now! which ten current ones should move to the "these get fucked" stack?"
Noodleface
A Mod Real Quick
- 40,561
- 20,641
Not judging as I've been in some serious crunches - but does anyone else work this much? Your boss maybe?
In my opinion, just based on what you said, your team really needs better sprint planning and as
Control
said you need to move less important things out if they're coming in like that. There are always going to be spikes, but there needs to be some give and take with that. When we take a spike, we move something else completely out of the spring unless we think it's a story that someone else can swarm on. Now... I hate scrum terms, but it's the easiest way to describe what I mean.- 1
TJT
Mr. Poopybutthole
- 48,094
- 132,705
While I do understand not letting others down its just a corporate job.
What I mean here is that as you have been around at that job for a long time you should have leverage. I've gained enough expertise, leverage, and confidence at this point that I shutdown at 4PM and stop responding to messages entirely. No way they would ever fire me or anything as I complete 3x the work of anyone else anyway. If you are clearing all your sprint work don't just go and do extra, force leadership to make tickets, document stuff, and so on.
- 4
Seananigans
Honorary Shit-PhD
- 16,270
- 38,351
Make sure everyone needs a new password with 4 special characters every 2 days
- 2
Noodleface
A Mod Real Quick
- 40,561
- 20,641
Just 90 days you say?
Don't do too well of a job or without the pay or title will be permanent.
- 2
- 1
Control
Avatar of War Slayer
- 6,436
- 17,848
- 1
- 1
Kuro
Bronze Baron of the Realm
- 11,289
- 36,542
DNS server down this morning, and of course salespeople came in on a Saturday when they're not supposed to be here so they're all panicking that they can't reach the file server. Dragged my sick ass out of bed to drive down here and get it fixed.
EDIT: Took a while but figured out the Virtual Servers for the DNS and backup DNS had somehow rolled over their memory limit at 2:30 in the morning. Was able to increase partition size and get them back up, but need to figure out how that happened once the work week starts.
EDIT: Took a while but figured out the Virtual Servers for the DNS and backup DNS had somehow rolled over their memory limit at 2:30 in the morning. Was able to increase partition size and get them back up, but need to figure out how that happened once the work week starts.
Last edited:
Siliconemelons
Ssraeszha Raider
- 15,844
- 25,450
Uggh… how crazy is your internal DNS needs if its just not chilling on the router or a L3 switch…
Kuro
Bronze Baron of the Realm
- 11,289
- 36,542
We have a couple hundred arm-crusher-9000 machines connected to the network, including routing (cutting) machines that assign themselves an internal IP that you can only see in their bespoke app but are technically still on the network and if you try to connect to their IP they turn on and chop the hands off of anyone trying to position metal sheets on the table at the time.
This setup was inherited from the previous IT team.
This setup was inherited from the previous IT team.
Last edited:
- 1
- 1
TJT
Mr. Poopybutthole
- 48,094
- 132,705
I got one for
TomServo
So again, I work in data infrastructure so this is more side drama to me. A few weeks ago a B2B sales guy comes to me and asks how we expose data in general. I said that that data platform itself is very much locked down. It does not export any of our internal data directly to anyone outside of certain services like a few financial ones we have. This guy was not really technical but he was very astute and he explains to me what he has been seeing.
In a several of his sales calls he said the potential customer knew far more than he thought they would about our sales process, final prices, and so on. I spend like 30 minutes showing him some of the inflows and outflows of this data, where it sits physically on our on prem systems and what consumes it. The primary consumer being the product application itself. The one that drives the entire business. He just goes okay, I will continue looking.
He goes to the app devs asking about it and this makes the rounds as the tech org is all seated in the same area of this startup type company. One that is doing ten times more business than it was 4 years ago and we have billions in revenue now. The app dev team finally asks this guy for some examples of what he suspects. Sure enough the customers are using datapoints that app dev says they should absolutely not have access to. Now we are forced on the hunt and to find it. Very easy to prove it can't be my space so we move on from that quickly.
Keep in mind we have exactly one dedicated infosec guy in the entire company and he is much more of a traditional IT systems infosec guy. He knows almost nothing about application architecture and security in general. The cause? Our internal only product was not nearly locked down as we thought (lol). The rotating key system that did indeed rotate internal access keys per session was actually exposing them in plaintext and the internal app itself not fully isolated from the greater internet. Leading to some of our customers figuring this out and scraping it constantly.
Our industry is highly transactional and volatile making this data very helpful when it comes to negotiating pricing and they knew what all of their competitors were paying. Overall a small sample of customers figured this out but still. LOL. The general philosophy was that the teams can handle their own infosec stuff. I bet we get a few hires for it now.
TomServo
So again, I work in data infrastructure so this is more side drama to me. A few weeks ago a B2B sales guy comes to me and asks how we expose data in general. I said that that data platform itself is very much locked down. It does not export any of our internal data directly to anyone outside of certain services like a few financial ones we have. This guy was not really technical but he was very astute and he explains to me what he has been seeing.
In a several of his sales calls he said the potential customer knew far more than he thought they would about our sales process, final prices, and so on. I spend like 30 minutes showing him some of the inflows and outflows of this data, where it sits physically on our on prem systems and what consumes it. The primary consumer being the product application itself. The one that drives the entire business. He just goes okay, I will continue looking.
He goes to the app devs asking about it and this makes the rounds as the tech org is all seated in the same area of this startup type company. One that is doing ten times more business than it was 4 years ago and we have billions in revenue now. The app dev team finally asks this guy for some examples of what he suspects. Sure enough the customers are using datapoints that app dev says they should absolutely not have access to. Now we are forced on the hunt and to find it. Very easy to prove it can't be my space so we move on from that quickly.
Keep in mind we have exactly one dedicated infosec guy in the entire company and he is much more of a traditional IT systems infosec guy. He knows almost nothing about application architecture and security in general. The cause? Our internal only product was not nearly locked down as we thought (lol). The rotating key system that did indeed rotate internal access keys per session was actually exposing them in plaintext and the internal app itself not fully isolated from the greater internet. Leading to some of our customers figuring this out and scraping it constantly.
Our industry is highly transactional and volatile making this data very helpful when it comes to negotiating pricing and they knew what all of their competitors were paying. Overall a small sample of customers figured this out but still. LOL. The general philosophy was that the teams can handle their own infosec stuff. I bet we get a few hires for it now.
- 1
- 9,062
- 23,668
Can i come work there? No homo. A serious response tomorrow.I got one for
So again, I work in data infrastructure so this is more side drama to me. A few weeks ago a B2B sales guy comes to me and asks how we expose data in general. I said that that data platform itself is very much locked down. It does not export any of our internal data directly to anyone outside of certain services like a few financial ones we have. This guy was not really technical but he was very astute and he explains to me what he has been seeing.
In a several of his sales calls he said the potential customer knew far more than he thought they would about our sales process, final prices, and so on. I spend like 30 minutes showing him some of the inflows and outflows of this data, where it sits physically on our on prem systems and what consumes it. The primary consumer being the product application itself. The one that drives the entire business. He just goes okay, I will continue looking.
He goes to the app devs asking about it and this makes the rounds as the tech org is all seated in the same area of this startup type company. One that is doing ten times more business than it was 4 years ago and we have billions in revenue now. The app dev team finally asks this guy for some examples of what he suspects. Sure enough the customers are using datapoints that app dev says they should absolutely not have access to. Now we are forced on the hunt and to find it. Very easy to prove it can't be my space so we move on from that quickly.
Keep in mind we have exactly one dedicated infosec guy in the entire company and he is much more of a traditional IT systems infosec guy. He knows almost nothing about application architecture and security in general. The cause? Our internal only product was not nearly locked down as we thought (lol). The rotating key system that did indeed rotate internal access keys per session was actually exposing them in plaintext and the internal app itself not fully isolated from the greater internet. Leading to some of our customers figuring this out and scraping it constantly.
Our industry is highly transactional and volatile making this data very helpful when it comes to negotiating pricing and they knew what all of their competitors were paying. Overall a small sample of customers figured this out but still. LOL. The general philosophy was that the teams can handle their own infosec stuff. I bet we get a few hires for it now.
I spent the day losing my shit on people and i got no chill right now