plausibilities

Impulse would be a good technical term to describe this.

The impulse from the first 0.5s of my clean & jerk is significantly higher than the first 0.5s of me grinding out a heavy deadlift rep

This one?

https://images.app.goo.gl/9TaZjLSfvdduab6d6

if(x) { debugger }

Pair programming and mobbing are tools which may be appropriate for some situations.

Unfortunately when tool use is mandated without applying critical thinking, it often results in a great deal of waste. Mandated collaboration is also very susceptible to abuse as it typically provides an additional layer of obfuscation to shield low performing leechers.

High school group projects dialed up to 11.

Me too, my shoulders feel all pinched together and my back feels hunched over when my hands are super close together in the home row position

One of its dependencies, OpenSfM, does a lot of the heavy lifting with regard to generating things like HOG descriptors (since SIFT = $IFT)

That project used to have a bug with their multithreading implementation where if your photo sets got too big children threads would terminate but fail to get reaped and your heap size would just continue to grow until things kaboomed at the SfM phase.

Not entirely their fault though as it stemmed from a deeper issue with Python stdlib's pool implementation.

Back then, with certain photosets I would literally run OOM on my homelab which was equipped with 128 GB DDR4

Should be fixed by now though.

You wouldn't happen to work for a small MPLS based startup would you?

bingo

well, you _can_, but IME having a reference monolith to excavate will likely net you significantly more reliable, holistic, and consistent requirements/specifications information than whatever the fuck comes out of the product guy/gal's mouth

Message:

You/we lack the proper (production runtime) environment conducive to practicing and learning this particular technique.

Reminds me of that dude who made a rather impressive amount of money posting classified ads on how to make money where the "secret methodology" being sold turned out to be a set of guidelines which simply instructed the buyer to follow suit.

srs = serious

my bad

https://github.com/purtuga/esm-webpack-plugin + webpack libraryTarget

So I basically don't exclude node_modules, and set up a simple webpack config to suck in my deps and output them as ESM modules to a given static dir of my choice

>I read through the linked page and it's not totally clear to me why you can't just import directly from node_modules.

Bingo

This is why it doesn't fully pass the smell test for me

Here's the problem I'm struggling with:

1. Typically, you only ever care about minimizing bundle size in cases where latency is consistently questionable

2. In those cases, whatever UI you're supporting is likely then not meant for latency-sensitive operations, and thus the overall workflow tends to have low state complexity

3. Just how much actual value is added in those scenarios by having the ESM workflow specifically in conjunction with importable NPM modules?

I'm sure you can think up some contrived use cases but I'm just not seeing any particularly compelling ones.

This feels like RequireJS all over again...

But for srs, couldn't I achieve more or less the same effect by not putting node_modules in my .gitignore and then making aforementioned modules accessible via static content dir pathing?

"We've evaluated ourselves and concluded that we are superior."

I bought a 48-core rig (Dual socket ASUS Z10PE-D8 WS w/ 2x Xeon E7-8890V4's) w/ a 10TB RAID5 array of 10800 RPM disks, 128GB DDR4 ECC, and a 1TB SSD for $5k...

Granted it was from some dude's homelab after he got laid off at Cray but still.

When you get up to that dollar amount I feel like there's just much sweeter shit out there.

One gripe is the thing is fucking massive and kinda unwieldy stuffed into a Coolermaster Cosmos II case...

Sure, what you are describing I would consider "passive suppression".

I should have been more specific and mentioned "active suppression" to imply a focus on behaviors inclusive of things like pre-emptive sabotage.

>you embrace it, escalate or forward it to the correct people

This here is key.

There are plenty of seemingly-intelligent individuals out there who refuse to acknowledge gaps in their knowledge.

They instead favor suppression and/or deflection over escalation because their own fragile egos could not handle the fact.

Full ownership mentality tends to weed these people out.

This seems consistent with personal anecdotal evidence.

Whenever I start eating "too clean", which for me consists of mostly bland foods and protein shakes, my appetite for calorie-dense snacks/meals tapers off and eventually results in me losing weight.

This usually happens over the course of a 7 - 12 days at which point I catch myself, overeat for a couple of days while going a bit harder at the gym, and bring myself back to baseline weight.

I'm 5'11", 172 - 178 lbs with an average TDEE of ~2800 and change.

Yes, I even lift, bro. And climb. And run. etc.

Good luck getting concrete interfaces locked down to the point where you can write meaningful tests - all the while managing the rest of your workload - when the business requirements change every week or so.

The concern with pay-to-skip-grind revenue models isn't so much with any notion of "fairness" or "integrity" as much as the fact that it greatly incentivizes asshole progression design which typically manifests itself in the form of intentionally-way-more-grindy-than-necessary midgame/lategame progression pathways.

Designing the ideal rate of progression to keep a given game engaging is difficult enough as-is. Too little content gating and you risk burning through all the content too quickly and players getting bored. Too much content gating and the grind begins to feel punitive.

In this context, muddling the mixture further by throwing in this kind of incentive just feels like a recipe for shit-tastic UX/CX.

I think these dudes have it in their head that they just wrote the next React/Vue-tier JS framework, but in the CMS space.

Hem-hem.

Allow me to pontificate for your edification, as to why wanton use of esoteric terminology is in fact a paragon of lexical mastery and thus ideal for the optimization of literary accuracy...

/s

Let me take a stab at it - perhaps it makes you feel disingenuous to some degree to propose large-scale, "silver-bullet", beaten-to-death solutions/strategies.

Reason being that, from a practical/cynical perspective, these proposals can too easily be co-opted into red-herring cudgels intended to end discussions before they delve into the realm of the more granular, nuanced, uncomfortable details.

What if I told you it's possible to accept one's privilege while disputing the degree to which it has directly contributed to specific, positive life/professional outcomes?

JS injection into display ads, which happens a lot more often than you would think when it comes to ad display network content.

In the land of the blind, the one eyed man is king.

Throw The Emperor's New Clothes, Impostor Syndrome, and Late Stage Capitalism mentalities into the mix and it's little surprise that these things play out the way they do every single time.

const length = (string) => (string.length)

It is unnecessary to adopt a naming convention which implies a scope within the context of "names" when the method is compatible with all strings.

Turn it into 2x PPL splits with 1 rest day in between for your weekly routine and you can look like a Men's Health cover model in ~6 months of hard work.

I hover between 172 - 176 with a 405 deadlift and 275 bench press.