|
App13 posted:Former navy, agree on all fronts. Finding out via ticket that someone you know was about to be shitcanned sucked. One of many reasons I am happy to be on the software side of the house these days.
|
#
¿
Jul 21, 2022 20:59
|
|
|
|
| # ¿ May 9, 2024 17:02 |
|
|
+1 for having gotten my last 2 jobs on LinkedIn. One was an old colleague looking me up to join him on a team he was building at a new gig, the other a straight up recruiter cold call that ended up being exactly what I was looking for. You obviously can't count on the latter but hell, can't win if you don't play. I'll happily connect with recruiters or others who craft a coherent and relevant intro. Ignore obvious salespeople or the recruiters from Pakistan offering a 3 month helpdesk contract in Oklahoma. Unless I'm actively job hunting I spend less than an hour a month on or thinking about LinkedIn. I'm sure as poo poo not scrolling through my feed reading anyone's posts. But it's literally changed the trajectory of my career and life for the better a couple times so I don't mind periodically clicking yes/no on some connection requests.
|
|
#
¿
Jul 22, 2022 20:08
|
|
|
AA is for Quitters posted:Welp, I'm now one of you. I used to work as a sysadmin for a rural ISP, which was part building and maintaining systems and part acting as an escalation tier for poo poo the NOC couldn’t figure out. Working in our NOC was kind of what you made of it. Some guys were pretty unmotivated and were content to chill watching YouTube until some issue generated a ticket. Follow a rote playbook then close the ticket or escalate. Basically help desk except for network equipment rather than end users. Others showed interest in actually understanding what they were typing into their computer and why. They usually got some mentoring and training and became junior network engineers. If you have a supportive culture at your company and find that kind of stuff interesting it’s not a bad path. Just don’t let yourself get stuck there doing nothing but follow canned scripts for years on end. Look for ways to learn and help out the more senior engineers. Especially at a small company there are always opportunities. If you can somehow transfer directly to a sysadmin or network engineer role without doing time in the NOC that’s even better. NOC isn’t really a career goal of it’s own, it’s a stepping stone, like help desk. Docjowles fucked around with this message at 04:37 on Jul 25, 2022 |
|
#
¿
Jul 25, 2022 04:35
|
|
|
Sickening posted:I am quite convinced the Architect does less than the CISO while probably making a little less. Our CISO is the embodiment of the meme that tech execs find all of their ideas in their airline seat back magazine. His main contribution to the org is forwarding emails announcing security vulnerabilities and asking “we good?” I’ve never seen a more fabulously cushy job. The senior security engineers at least stay busy setting up endless PoCs for products they don’t end up buying.
|
|
#
¿
Jul 29, 2022 16:52
|
|
|
tokin opposition posted:i was going off to college when this thread started God drat I didn’t realize how long it had been since we rebooted this megathread lol. My first kid was an infant and now she’s entering third grade. My workplace still had a small amount of Cfengine, a lot of openstack, and exactly zero containers or public cloud.
|
|
#
¿
Jul 31, 2022 04:37
|
|
|
I put in a help desk ticket requesting a new laptop because my 2018 Macbook pro barely works anymore. If I join any sort of video conference (which is like, 90% of my day because it's 2022) the fans ramp up to 42069 rpm and my cpu gets throttled to original 8086 chip speeds. I can't use other applications while the video is playing because it's so slow, and often the video ends up hanging too. It also randomly kernel panics several times a week. They just mailed me a 2019 Macbook pro barely any different than the one I had. Cheap fucks  edit: now that I open the box it's also all scuffed up and clearly reused lmao Docjowles fucked around with this message at 22:12 on Aug 5, 2022 |
|
#
¿
Aug 5, 2022 22:03
|
|
|
Today on "why do infosec people make mid six figures again" Got a ticket that they were setting up some new application in AWS and it can't hit internal servers back in our data center. The DNS name they are trying to use resolves to a 10.x IP, and exists in a private internal-only zone so doesn't even resolve in the first place from the public Internet. They are just using a bog-standard AWS account that has not been hooked up to Direct Connect or had DNS rules enabled or anything. I'm not sure if they did literally zero troubleshooting, or just don't understand how the cloud or networks work. But given that the request was "please open firewall" I am going to go with Both. Coming from someone with "cloud security" in their job title this does nothing to boost my confidence in our protection from security threats.
|
|
#
¿
Aug 11, 2022 17:35
|
|
|
|
| # ¿ May 9, 2024 17:02 |
|
|
Thanks Ants posted:I've been asked by dev teams to "turn down the latency of the internet connection" so yeah I'd say a network-focused job is going to be fine until you hit retirement age This reminds me of when I worked at an ISP and marketing asked how fast our packets travel in miles per hour so they could put big numbers in an ad. That was an all-timer, I thought our lead network engineer was going to have a stroke. “Technically the speed of light I guess? But that is NOT how this works and has no bearing on customer performan—“ “Hot drat, the speed of light?!? Say no more, we’re printing the mailers” closes laptop, heads directly to the bar They put a pic of a stealth bomber on it and the speed of light in mph. I really wish I had kept a copy. Docjowles fucked around with this message at 20:23 on Aug 11, 2022 |
|
#
¿
Aug 11, 2022 20:20
|
|