@YADU one or the other? 🤔

I feel this. I got in a huge argument with a co-worker because I figured out that the macOS version does some hand wavey magic to make interactions with the host file system easier, which was why it "worked on my machine" but not when deployed. He _would not_ accept that docker worked any differently between host operating systems, even going so far as to claim he'd accomplished exactly what we were struggling with before. I told him to prove it and miraculously I never heard anything about it again.

Don't store anything that you wouldn't want stolen. Also don't provide any service that would cause you problems if compromised. Then you're basically immune to attacks and probably don't have a company to protect!

@just8littleBit Our Jenkins environments do a well enough job. Until you're forced to work in them. Making new pipelines or updating existing ones is a giant pain the ass and has been at literally every employer I've had that used it

Edit:
You're not wrong, though. Most of the pain comes from the decisions that were made by the teams responsible for Jenkins.

@AlmondSauce my last gig used gitlab CI for almost everything. It had its quirks, but I'd go back to that yesterday if I could

@jiraTicket to be fair, no. You could just run a minimal Jenkins setup and leave out 90% of the cruft. I've just never been at an org that did that. It always ends up loaded with random plugins and pipelines get over engineered because it gives you easy access to a "real" programming language. So not Jenkins' fault, just every installation I've ever seen 😅

I generally agree with the advice given to talk to your new manager and escalate as needed from there. However, you understand the culture and office politics better than we do, so I think it's equally valid to say "fuck this" and look for other work to do if you feel trapped. If it's an internal move, maybe they'll try and work with you to remove the problem. If it's external, the same might happen along with some extra compensation. Otherwise, the world is your oyster.

In either case, internal or external, there won't be much doubt that you're serious about the issues.

@electrineer I told him I didn't agree and reminded him of the things I'd spent this year working on, but all of those were brushed off as not "big" or "important" enough for my level. I'd take more action, but I have no intention of sticking around much longer, so I'm not sure if it's even worth the headache

@Cyanide this is also the only thing I could focus on in this post lol

@heyheni I'm normally pretty good at navigating politics, this is the first of four employers I've run into this problem 🤷‍♂️

@heyheni it's even more of a shame because there are a couple folks on my team that are experiencing this environment as their introduction to the industry 😞

I'm 28 with 6 years of experience in tech

In my opinion it shouldn't matter. Challenging the status quo shouldn't conveniently omit challenging him or company processes. If he can't deal with constructive feedback in a public setting, he shouldn't be in people leadership.

That said, I've only made comments in forums where it's expected. i.e. sprint retrospectives, 1 on 1s, and more recently in the routine meeting with my boss's boss (which I think is probably where the retaliation is coming from). My whole team is afraid to speak up about anything because the leadership is toxic, so I've been trying to open a dialogue on things like being pressured to underestimate stories and potentially splitting up our fairly large team to make things easier to manage.

What are your requirements for a dev machine? I recently spent $1,400 on a Lenovo X1 Carbon that I booted linux on and it's been an absolutely stellar dev machine.

At least k8s is a popular, standard tool at this point. You could be provisioning your apps and infra using shitty homegrown tools full of bugs and lacking documentation 😅

@Demolishun Unfortunately there isn't. And after a few discussions about that we were told to just make the report happy so it stopped coming up. The same security tool will fail your project if you don't have any third party dependencies, because it assumes you did something wrong 🤷‍♂️

I'm sure there are good theoretical reasons for most of the things that get passed down to us. The hard thing is that there's virtually zero nuance when it's a large company. Everyone gets the same blanket requirements even though the projects are extremely varied.

@Demolishun the problem with a lot (not all) of the types of things I'm talking about is we often circumvent the actual value-add in order to show up green on a report. Dumb example: We submitted our code for automated testing to our security scanner, just to show up green, because the app itself wasn't supported. Later, there was a vulnerability in a dependency that required us to cut the dependency out of our tests. Again, so we show up green on a report. This was in code that never ran on production infra, that had no security scanning requirements.

Other instances are easier to see at least SOME value-added, but the continued work required to remain in self-imposed compliance is not small.

@halfflat I mean this is a fair point. The change management folks are even more insufferable than the managers though 🤦‍♂️

@ScriptCoded well then it sounds like they forfeit their right to having an opinion 😄

Have you asked your colleague "if not this, how would you prefer we solve it?". If they can't give you even a hint towards an alternative, ask them why you shouldn't use your solution. If they give you some bullshit answer like "I just don't feel good about it", tell them that's a dumb reason not to fix a real problem and you're going to deploy it.

Seriously, if they sat with you and you both came to the same conclusion, it sounds like they're just being needlessly difficult.

@saucyatom depends on the audience. Performance requirements for internal tooling are typically described as "fuck all"

That sense of satisfaction, though, when you can just immediately respond with a link

@SortOfTested had no idea about the prorated repayment. That might actually change things a lot, so thank you! 😄

Oh and some additional context I forgot. I took a signing bonus that has to be paid back in full if I leave within the first year, so I'm trying really hard not to just jump ship. But fuck, maybe it's worth the financial hit at this point. I don't even know anymore...

Python is probably the best if they aren't actually interested in becoming a programmer and just want to script useful things quickly. I'd toss Go in as a contender if you really want strong, static typing. It's a super simple language, sometimes to a fault, and would probably be even easier to pick up if you didn't have a bunch existing knowledge to "unlearn"

The only thing I don't like about them is how non-standard the definitions are. I agree with a lot of the comments here, in that full stack to me means you can do everything required to ship a software product yourself. Given enough time, of course. Where it gets confusing is when people take subsets of "all-the-things" and call _that_ full stack.

I think the real question here is who hurt you so bad that you run Alpine as your workstation OS...?

I've never come across someone that corrected me with GNU+Linux, but I'm not sure I could contain the urge to punch them in their stupid face 😐

Not sure if actually missed @netikras joke or just being an ass 🤔

But...you can? 😅 A cert isn't required to get a load balancer running

Normally this doesn't get me, but at 6:00am after 5 hours of sleep, I apparently fall for this hook, line and sinker.