Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S

steventhedev

@ steventhedev @lemmy.world

Posts
2
Comments
42
Joined
3 yr. ago

  • EC2 hosting be like

    Jump

  • I think you're over exaggerating the effort needed for tagging resources. Between terraform/pulumi/cdk and the tag tool, it's relatively easy to make sure everything is tagged. Doubly so if you have a finance department who's literal job is to go through and do that (or ask you for help with it)

  • EC2 hosting be like

    Jump

  • You can get a full itemized bill. The only thing that isn't fully broken out are elastic ips. We found that out because we were tagging everything for billing and those weren't showing up correctly.

    Mind you, it's likely a bit more itemized than you want. Like you'll see a separate line item for each price tier you paid for something, and things like ebs disks are all split out. It can be a bit...much.

  • Edge case? Corner case? Basket case.

    Jump 
  •  
        
When I was a young dev
My senior took me into the city
To push my code to prod
He said "Son, when you promo
Would you be the savior of the broken
The buggy and the OOM'd?"

  • Water

    Jump

  • *OH2

  • No, the Chinese Have Not Broken Modern Encryption Systems with a Quantum Computer - Schneier on Security

    Jump

  • The original article smelled wrong when they claimed to have broken AES. Thankfully, Bruce Schneier is far more authoritative than I ever will be and gives a short and succinct list of links to debunkings of this.

  • Deleted

    Trump win means ‘time has come’ to annex parts of West Bank, Israeli minister says

    Jump

  • The anti-Israel crowd are basically the MTG and Boeberts of the Democratic party. Right on down to outlandish claims about crisis actors

  • Fridges never die.

    Jump

  • Those young machine spirits need their rest

  • Self-documenting Code

    Jump

  • One upvote is not enough.

    I once wrote a commit message the length of a full blog post comparing 10 different alternatives for micro optimization, with benchmarks and more. The diff itself was ten lines. Shaved around 4% off the hot path (based on a sampling profiler that ran over the weekend).

  • Self-documenting Code

    Jump

  • Ew no.

    Abusing language features like this (boolean expression short circuit) just makes it harder for other people to come and maintain your code.

    The function does have opportunity for improvement by checking one thing at a time. This flattens the ifs and changes them into proper sentry clauses. It also opens the door to encapsulating their logic and refactoring this function into a proper validator that can return all the reasons a user is invalid.

    Good code is not "elegant" code. It's code that is simple and unsurprising and can be easily understood by a hungover fresh graduate new hire.

  • Deleted

    Permanently Deleted

    Jump

  • Gotcha. So all horses are purple?

  • Packet Loss

    Jump

  • None built in from what I recall. That was from back in 2011, so it's possible things changed since.

    Reading through, it looks like retries do exist, but remember that duplicate packets are treated as a window reset, so it's possible that transmission succeeded but the ack was lost.

    I remember the project demos from the course though - one team implemented some form of fast retry on two laptops and had one guy walk out and away. With regular wifi he didn't even make it to the end of the hall before the video dropped out. With their custom stack he made it out of the building before it went.

    I'll need to dig through to find the name of what they did.

  • Packet Loss

    Jump

  • To be fair, because of window size management it only takes 1% packet loss to cause a catastrophic drop in speed.

    Packet loss in TCP is only ever handled as a signal of extreme network congestion. It was never intended to go over a lossy link like wifi.

  • "Would U.S. tech workers join a union?" survey average: 67% likely

    Jump

  • Only on signup

  • "Would U.S. tech workers join a union?" survey average: 67% likely

    Jump

  • Anything using Blind as a "verified industry source" is going to be skewed to the type of person who uses Blind. Beyond that, it's low sample size, and there are suspiciously round fractions for some of the larger companies. Worse, because Blind is blind - this doesn't represent current employees, but merely people who worked at some point in the past at those companies.

    Not saying it's not good - just saying not to get overly excited over a badly done survey

  • Is it viable to use a gaming handheld as main dev machine?

    Jump

  • I have worked remotely on and off for years. Having a physical separation between the space where I work and the space where I play is an absolute must.

    Beyond that - the hardware needs for development and gaming are wildly different. If you want something that's going to be good at both, you're going to either going to have to spend a lot of money or compromise heavily on quality.

  • Is it viable to use a gaming handheld as main dev machine?

    Jump

  • I'd strongly recommend against it. Nothing to do with specs or viability but psychologically you'll want to play games - they're enjoyable. You can work around that in a few ways: only use the keyboard/mouse for dev work, only play games outside the workroom, etc. it will still take a lot of self discipline, but it's nothing compared to having a different OS, physical machine, etc.

    In terms of specs - if it can run vs code, you can use the remote development plugins to run things on a beefier computer if you do heavy data work, etc. I don't know if it will do video editing though.

  • When happy teams are an issue

    Jump

  • Seriously though - JIRA isn't always a massive pain in the ass. It's just the way it's used that sucks. Workflow restrictions so devs can't move tickets from testing back to in progress, dozens of mandatory fields, etc.

    When your tools start dictating your workflow rather than the other way around then it's time to switch tools.

  • When happy teams are an issue

    Jump

  • Friends don't let friends use JIRA

  • Better merge it, too!

    Jump

  • I have either written or gotten a variant of every single one of these comments 🫠:

    Please include the JIRA task in the commit title.

    Did you run any manual testing?

    Where's the PRD link in the commit message?

    Can you please split this into multiple smaller commits?

    Can you combine these two commits?

    Did you email Jon about this because he's working on that project with Sarah and you might be duplicating efforts.

    This should be named BarFoo instead of FooBar.

    Why aren't you using CorporateInternalLib16 that does 90% of this?

    Why aren't you using ThirdPartyPaidLibByExEmployee?

    Why aren't you using StandardLib thing you forgot existed?

    All our I/O should be async.

    All our hot loop code needs to be sync.

    This will increase latency of NonCoreBusinessFlow by 0.01%. can you shave some time off so we can push in feature B also?

    Please add a feature flag so we can do gradual rollout.

    What operational levers does this have?

    Lgtm - just address those comments