DevOps was supposed to save the world, not destroy it!
-
Microsoft's GitHub 'DDoSes' open source GMP project
A tale of emergency firewalling, a little bit of victim blaming, and workflow scripts gone berserk
-
Our machine is pretty powerful, it is a server class machine with many cores and lots of RAM, and its connection is 1GbE at a top-class datacenter
Ooooooooh! 1GbE! Apparently, that's top-tier high performance networking. I wonder what he'd make of the 2.5GbE port on my PC at home...
-
@Steve_The_Cynic Your home connection probably doesn't have balanced bandwidth or some sort of (real) SLA.
OTOH, putting a CDN in front of a server that's taking a bit more load than expected really isn't very costly, especially for something where you'd expect to be serving up the same content a lot of the time.
-
@dkf do CDNs meaningfully exist for Hg repos other than taking a local copy first?
I mean, this is some insane twisted bullshit that a downstream package pulls 100 separate copies of the repo to do a CI run…
-
@dkf Fair point, although these days there's no way I'd boast about a 1GbE connection.
And my ISP provides me with 2Gb/800Mb fibre.
-
@Steve_The_Cynic seems like less of a boast and more just him saying that his server has more than enough resources to handle a reasonable amount of requests.
-
A slight side tagent but does full-stack include devops these days? I’m touching up my CV and need to play buzzword bingo.
-
@DogsB include anything you’ve ever heard of. That’s how everybody else is doing it.
-
@topspin said in DevOps was supposed to save the world, not destroy it!:
@DogsB include anything you’ve ever heard of. That’s how everybody else is doing it.
Better to be safe and claim 7 years’ experience in a few things that haven’t been
inventedreleased yet too.
-
@DogsB said in DevOps was supposed to save the world, not destroy it!:
A slight side tagent but does full-stack include devops these days? I’m touching up my CV and need to play buzzword bingo.
My definition of "full-stack": You've done substantial work on all three tiers: Database, UI and the code that communicates between the two. So if your experience was exclusively in one or two of the three, you wouldn't call yourself full-stack. Doesn't imply that you have experience in all three equally. Pretty much all of the regulars here I would call full-stack.
-
@jinpa said in DevOps was supposed to save the world, not destroy it!:
@DogsB said in DevOps was supposed to save the world, not destroy it!:
A slight side tagent but does full-stack include devops these days? I’m touching up my CV and need to play buzzword bingo.
My definition of "full-stack": You've done substantial work… Pretty much all of the regulars here I would call full-stack.
You’re just itching for a bout in the Octogon, aren’t you?!?
-
@izzion but mother would never hear of it.
-
@Arantor said in DevOps was supposed to save the world, not destroy it!:
@izzion but mother would never hear of it.
?
-
@jinpa Musk’s mother called it off on Twitter, apparently.
-
@jinpa said in DevOps was supposed to save the world, not destroy it!:
@DogsB said in DevOps was supposed to save the world, not destroy it!:
A slight side tagent but does full-stack include devops these days? I’m touching up my CV and need to play buzzword bingo.
My definition of "full-stack": You've done substantial work on all three tiers: Database, UI and the code that communicates between the two. So if your experience was exclusively in one or two of the three, you wouldn't call yourself full-stack. Doesn't imply that you have experience in all three equally. Pretty much all of the regulars here I would call full-stack.
Huh. I've definitely done work on all three tiers in a professional capacity. The real question is whether my bits and bobs of DB work count as "substantial." I mean, I've worked with both SQL and NoSQL DBs, but always in a tangential "doing a little maintenance/just-enough-to-support-a-feature work because the real DB devs are busy" way.
Eh, I'm a straight white man. I am required to inflate my skills, because every single one of my peers does so.
-
@PotatoEngineer Which means if you've ever so much as touched those layers, that's already substantial by definition because your competition peers will be using a similar level of definition.
It's like how we all talk about "measuring 9 inches" for something that in reality is "6 inches", the assumption is that everyone does it therefore to compete we all have to do it.
-
@Arantor and those with some experience know to avoid the “measuring 9 inches” crowd just as well as those who list as qualifications every single topic or technology they as much as saw listed in the
college curriculumudemy website.
-
@Arantor said in DevOps was supposed to save the world, not destroy it!:
@PotatoEngineer Which means if you've ever so much as touched those layers, that's already substantial by definition because your competition peers will be using a similar level of definition.
It's like how we all talk about "measuring 9 inches" for something that in reality is "6 inches", the assumption is that everyone does it therefore to compete we all have to do it.
I would kind of hope that it's not even that. I haven't heard someone use the phrase, "measuring 9 inches", so if it's an expression that people understand, then the following would have to be modified, but...
If you sell a 6 inch strudel as 9 inches, you're lying, even if other people do it.
Saying you're a full-stack developer is a judgement call, on the other hand. So, for example, if you've had substantial UI and core services experience, and some DB experience, it's not exactly a lie.
But the whole discussion illustrates the problem of relying on others' self-evaluation.
-
@jinpa “strudel” isn’t quite the euphemism you’re looking for, but I’ll try to remember that one.
Filed under: my father, the inventor of toaster strudel …
-
@topspin Everyone's favorite lover of strudel:
-
@jinpa said in DevOps was supposed to save the world, not destroy it!:
If you sell a 6 inch strudel as 9 inches, you're lying, even if other people do it.
You're notionally correct, however the problem is that since everyone else is lying, you being honest will be assumed to be also similarly exaggerated.
But also consider the reason we have coding tests the way we do is precisely because we have to assume CVs/resumes are largely full of half-truths and exaggerations and we need to work out if someone who says they're a full stack dev really did work on both frontend and backend or not.
The trick is to be careful about what you put on and what you can big up to avoid disappointment later.
Which, ironically, does not change what my rather crude analogy was getting at - though I was referring to the size of a bodily appendage when society would like to proclaim that size doesn't matter... if it truly didn't, there wouldn't be any perceived value in inflating that number. And yet, it happens disappointingly often.
-
@Arantor said in DevOps was supposed to save the world, not destroy it!:
bodily appendage ... inflating
That's rather the point, yes?
-
@Arantor “society” isn’t a uniform blob. There’s people on whom it works, people who don’t care, and people who roll their eyes you even boast such vapid things.
-
@topspin I know this, there are always exceptions, but sadly the majority of the great unwashed do function broadly the same way, thus it has ever been.
-
@PotatoEngineer said in DevOps was supposed to save the world, not destroy it!:
The real question is whether my bits and bobs of DB work count as "substantial."
potatos don't have the ram to run most databases
-
-
@loopback0 "[more than] enough bandwidth" would be sufficient, without leaving him exposed to ridicule for vaunting what is essentially the minimum you can buy today.
-
@Steve_The_Cynic said in DevOps was supposed to save the world, not destroy it!:
@loopback0 "[more than] enough bandwidth" would be sufficient, without leaving him exposed to ridicule for vaunting what is essentially the minimum you can buy today.
Not to mention, if that was a direct quote, he's saying "yeah, we have a 1Gb port plugged into the server" and nothing about what committed bandwidth they're actually paying for on that port. So it's quite probable that beyond DDOSing them, this little excursion is actually costing them a shitton more money, since they're probably paying for something like a 100Mbps CIR "burstable" connection and paying a bunch for this new peak 1Gbps load.
