• 0 Posts
  • 27 Comments
Joined 2 months ago
cake
Cake day: September 21st, 2024

help-circle
  • “it works on my machine.”

    It’s funny that that’s the answer that they always gave, considering there were times that we had screen shares, and I asked them to walk me through how they actually got it to work.

    When they attempted to try to run it, unsurprisingly it broke.

    There were even a few times that I didn’t even review it and the first step I took was to inform them that it wouldn’t run. Also, unsurprisingly, I was right.

    Management at the time was driven by product development and delivery of “high-value” features. As long as deliverables were delivered, this dev could do anything they wanted to. At the end of a year, I’d lost about four weeks of productivity. That doesn’t even cover the hours of after work time that I spent on trying to fix their fuckups.

    Needless to say, I stopped doing that. I used to be a nice guy to work with, but now… Let’s just say if you can’t do the work, I’m not covering for you. If your PR doesn’t get merged because it’s broken and you can’t fix it and you spend six weeks trying to fix it, that’s on you.


  • dude. i feel that pain.

    i got a dev fired because they absolutely refused to test their changes before submitting.

    I’m not talking once or twice either. at least a year of that bullshit. i had to show my boss how many hours of wasted time it was taking me because I look at the code first, like literally anybody. Eventually boss pipd them and fired them but holy fuck i wanted to kick that douche in the groin every time i saw a pr with their name on it.

    next place I work I’m insisting on a build step success to assign a pr.







  • pipeline schedules. once a month I clone the remote repo into a local branch, and push it back to my repo with an automatic merge request assigned to me. review & merge kicks off build pipeline.

    I also use pipeline schedules to do my own ddns to route 53 using terraform. runs once every 15 minutes.

    also once a week I’ve got about 50 container images I cache locally that I build my own images from.



  • what’s old is new again! they tried to pull this shit back in the day but physical media was the only delivery method. now that everything is downloaded there’s a bunch of legal grey area they’re hiding in.

    so the next question, is this retroactive? if so, then when will I get my money back? Licensed software is cheaper than the full MSRP I paid for titles that had physical options I could have bought at a store. this is because licensed software usually has an expiration date while physical media with software can be installed anytime after purchase.

    so, Valve, one last question.

    where is it huh?!









  • as a full stack dev, everything you said has offended me.

    port 20 is used for FTP, unless you were using FTP, then go right ahead. Guessing that since you didn’t know the protocol you were not using FTP.

    port usage reservations are incredibly important to ensure that the system is running within spec and secure. imagine each interface like a party telephone line and the ports are time slots.

    your neighborhood has reserved specific times (ports) for everyone to call their relatives. if you use the phone not in your slot (port) your neighbors might get pissed off enough to interrupt your slot. and then it’s just chaos from there.


  • the government does, and what they do with it is harshly regulated.

    the TSA is part of DHS but operates outside of DHS and can do whatever it wants with your information if you give it freely. it’s one of the reasons how that facial recognition apparatus works. it was developed by a contractor to USDOD and delivered to DHS for the TSA to use on the public.

    DHS cannot investigate the general public without probable cause, TSA can. so what information they gleam from the general public is then shared with DHS, DOD, and sold back to the contractor as a part of the delivered contract. what they do with it afterwards is entirely up to them.

    both accepting and rejecting the scan is harmful to your privacy. by accepting you are now indexed in a database and that information can be used in multiple government sanctioned investigations. by rejecting it, you are flagged as a concern and your profile is then processed through and algorithm to identify your threat level.

    the TSA are doing more than just looking at your passport when you reject. they’re waiting on that threat level response to identify if you should be taken for further questioning.