Aboutcybersecurity engineer in aerospace
Skillspython, c++, flask, linux, security, containers, docker, container security
Joined devRant on 5/17/2019
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Dev from MIT argued about every. Single. Thing. I said. I'm not talking language or cultural or political barrier, I'm talking about just a naturally confrontational person. Maybe it was just his nerves (people do weird shit when they are nervous), but damn if i didnt want to throw him out after "agreeing to disagree" for the 4th time in 10 minutes.7
Anyone here play an instrument (yes, singing counts you dim wits)? Almost 85% of my colleagues do, and i was wondering if it holds true here...11
I've discovered there's two sections of devRant:
- Individuals in the workforce fed up with /r/programmerhumor and who hate Twitter
- Teens with a superiority complex, no friends, and acne12
Do you guys have people in your office that just REFUSE to cooperate, or people who tell you they'll cooperate, but then they literally do anything except for cooperate?
I'm having trouble with the latter; I've been trying to get one of our less experienced members to work on our deployment. He's successfully configured at least 4 other deployments, and this one is the EXACT SAME as the other ones. The issue is that the person who is im control of this particular master console is someone higher up than me, but they don't know how to delegate. Thus everything that they touch becomes their own little pet project that no one else can dare touch, because they'll "mess it up" (not do it the right way according to his limited bible of best practices).
So now I'm stuck here, trying to convince HIS BOSS to get him access, but i even HE cant get him to do it! Now I'm sitting here waiting, getting more and more fed up with this guy, because like i said, it's his MO: im on two other projects with him, and they're all moving at a GLACIER'S pace.
Seriously, if you dont have the time for a project, but it on the backburner, dont start it and make your other projects suffer.6
Alright boys, let me tell you how someone fucked up so hard they got their deployment schedule delayed "indefinitely".
Being security, we get to oversee most deployments, and we especially get to oversee all deployments that are on IT-managed tech. Knowing fullwell about this fact, some dumb motherfuckers woke up and thought to themselves "You know what would be good fun? To piss on security's asshole and then try and ream them up the backside before they notice the piss!"
Well let me tell you, we noticed. And our boss noticed. And his boss noticed. And the CIO noticed. Thus it came down the chain that this particular group of lie-spurting, baseless accusation-leveling group of developers would have their deployments put on hold. How long? "A while."
I have never quite heard my higher-ups this mad before, but damn if i dont share in their enthusiasm to stick it to entitled cunts.18
I'm doing the thread again; post music to code to. I'll go first with 8-bit influenced jazz fusion band Sungazer:
My team: "Hey were getting errors with this process, whats going on?"
Net team: "Hey were getting errors with this process, whats going on?"
Me *looks at logs once*: "Did you guys check the logs? There's a 500 error on the Net side app since 3am this morning..."
Net team: "Oh yeah we changed that but we forgot it would break your shit"
Goddammit why am i not on the alertlist if you are all going to call me when shit breaks?! Doesnt make any sense!!
Davi Ottenheimer; security wizard and one of the coolest and most knowledgeable guys i know. Met him at IANS2019 and haven't worked up the courage to email him
Anyone have those coworkers that completely interrupt people? I've found that a couple people i work with just were never taught to wait for someone else to finish. Doesn't help that they're really smart and also really opinionated.
How do you deal with these people? I've found steamrolling them or asking them to wait works, but only if you raise your voice a bit, which is mostly inappropriate, but easy to do on a web call.
Any suggestions for keeping this out of private life? I've found that i steamroll my friends sometimes even though i don't have any reason to, and I've become quite good at it...3
My man said "What should I return if the True/False field is left blank?"
WHY WOULD A BOOLEAN BE ANYTHING OTHER THAN TRUE OR FALSE???!!!
I'm gonna have an aneurysm. I shouldn't be educating people on best practices for something that's already been written about time and time again. RESTful philosophy has been documented so much, and all it takes is a quick google search, but noooo! I have to take time out of my day as if I'm a regular old stakeholder to explain that I want the exact thing that I sent in an email two weeks ago. Amazing.20
Version control is important... But holy shit I'm having an anxiety attack from this: https://what.thedailywtf.com/topic/...2
*The one where he breaks ssh*
TL;DR: Minikube's dick is too big, and my ass wasnt ready.
So there was a time about 2 weeks ago where i wanted to try and set up a minikube cluster using SOP, and that actually went okay, aside from having to move over to a completely different server after discovering that my processor doesn't support virtualization.
So i set it up on my other server, and everything immediately starts going to shit; i can no longer run commands without processor latency. Also top shows 200% CPU usage. Maybe i should stop... NAHHH... so i continue on, and the biggest fuck up was starting up the nginx pods. I have 6 of them, and the moment i try and stand up my custom container which was the WHOLE POINT of this whole exercise, i lose ssh access and cant get back in. I go over to the server and kill the minikube and virtualbox processes, and everything's back to normal.6
My best review was when i changed the code that someone suggested in another PR, which was highly critiqued by the OG devs. One pull to the latest commit and PR to his fork later, the OG dev comments "that looks good" and merges it.
Celebrated for sure that night. I've been hooked on contributions to open source ever since.3
Wanted to remind you Americans that it's too late to start on a new feature, function, or debug. Go to sleep after leaving yourself some notes. You'll be better off in the morning.3
Is it possible to have an "epistemological bug crisis"? Because i feel like everything I referred to as bugs in my early career weren't true bugs, they were just bad programming or architecture flaws. I feel like real "bugs" are weird issues with the language, compiler, module, etc... that should work one way but work another way. Anyone else had that experience?
This gives rise to the secondary question: who perpetuates the idea that bugs are just "anything wrong with the current codebase"?4
Put the meeting agenda in the meeting invite: after a few meetings of you referring to those notes in a condescending manner, people will get the hint that you want them to familiarize themselves with the agenda before the meeting. It also gives you a nice reference point if you ever get off topic.
1] Being able to say "the easy way or the hard way" when people ask if you can build them a website/app
2] Telling people they can't afford me when they ask if i can help them with something computer related
3] The feeling of encountering a problem and solving it gives me a drug-like high when i've finished a project. Even the feeling of finishing all the day's tasks and having time to work on ongoing greater tasks fills me with a sense of accomplishment and victory.
We have a 15-machine cluster that went down last night because one machine in the cluster went down. Apparently having a cluster for redundancy is just a nice idea and doesnt actually work in practice.
Also I shouldnt have to go to a vendor's forums to find out the bug that is causing my cluster to go down is fixed in a future version. It should be in the goddamn patch notes!!!
Let me tell you the story of how a feature request no one asked for got put in an early grave:
PM walks into weekly meeting with a single use case that one user called in about, despite never having this issue during the past year and a half that our app has been in production. PM's boss (genuinely one of the best people i have ever worked with) happens to sit in this particular meeting for no reason other than he felt like he should once in a while.
PM brings up use case and wants to devote 3 weeks' development time and another 3 weeks to test RIGHT NOW while other projects are already in motion. PM's boss speaks up with this: "Listen if this guy is really this upset, we can just tell him to build his own service. All the other end users have no problems with this, so it's not worth spending the resources on, i don't think."
And that is how i went from "this is bullshit" to "i love you" in the span of 20 minutes.2
I reached out to a developer who's site was being contracted out to Amazon devs, because when their site launched it had a couple of security issues. This was his response:
"An additional thought/opinion... Just because a college freshman from Arizona wasn't too hungover to make the effort to notify us and take the liberty of classifying this as a security issue for us doesn't mean we need to take their word for it."6