orestes910

This is weird thought where your solution to the problem is just "have the people on the team be better."

The entire phenomena exists because people that see how important these things are end up on teams led by and staffed by people who either don't see how important they are, or aren't competent enough to do the glue work.

The lack of parties and happy hours is music to my ears, personally. I can't stand these events, and they often work in the service of this strange social construct that we all know and love - "culture." At some point socializing with your teammates outside of working hours became part of the job. Its strange really, to almost force these things on people, as it doesn't even serve to strengthen the team bond that much. Soldiers don't bond at the bar, they bond on the field; they socialize at the bar.

Loneliness and isolation is often cited as a downside of remote work, but as someone who doesn't like to mix work/personal and has a healthy personal social life, I just can't see it being an issue for everyone.

Someone else can find the source, but Netflix themselves have stated that the lions share of viewing on their platform is aimed at TV shows, so it doesn't surprise me that they haven't invested in quality (and expensive) movies. Why would they if no one is watching them?

Can anyone help me understand why we're even performing studies like this anymore? It would seem that all these years of "x can cause cancer" studies have just revealed that we generally know very little about what causes cancer. Is prevention really a viable avenue of control anymore? Shouldn't we just be focusing on early detection and treatment?

I think it comes down to performance measurement being a really weak area for many companies. No one really knows whats real when it comes to output over a 40 hour week, and so bosses are afraid of getting shafted by an employee whom they can't see toiling away at their desk.

It's all but fact that a 40 hour work week doesn't result in 40 hours of productivity. Those non productive hours are seen as acceptable in an office for some reason, but when you're at home and can fire up a video game, it's sacrilege.

I'm glad someone else mentioned it. Thought it might just be my imagination.

A friend of mine is making thousands per month simply selling notification bot subscriptions to people who run private discords. His don't even buy, they just send stock notifications to the rooms. Madness.

As someone who used Percona in production, its fantastic for a small/medium workload, (depending on your definition of those) but it has pretty hard limits on scaling without an intermediate layer, which then mostly defeats its purpose - dead simple clustering.

I agree completely that 100k directs is bad, but they're writing from a perspective where the alternative would likely mean switching to a different product.

That is actually a really solid point. I still don't know that it's necessarily the right way, but I'd certainly rather those scripts be tested!

Outside of the scope of elaborate CI pipelines, I wonder how useful this can really be.

Big CI pipelines are one of the few instances where I can think of Bash being both an appropriate choice AND the resulting product being large, elaborate, and sensitive to failure - which would benefit from being tested. Most other applications of Bash are generally just so simple that fundamentally altering how you write scripts ("Bash scripts must also be broken down into multiple functions, which the main part of the script should call when the script is executed.") for the sake of testing them seems like it could easily fall into the category of over engineering.

Beyond the CI pipeline use case, wouldn't the tools in which this would actually be properly useful be better off written in a proper programming language?

My first guess would be that power consumption drove those decisions.

I also liked how "risk taking" was in the toxic group, while "courage" was seen as a positive. Right alongside "leadership".

So, be courageous and lead, but don't do things that require courage or put you in a position of leadership.

Is it really THAT hard to to run on prem/cloud because of the "complexity that comes with setting up and managing MongoDB clusters at scale"?

The documentation is strong, it was built with horizontal scalability in mind. I don't see the struggle.

Upon looking around in the demo repo, this seems like so close to pure Python that I almost don't see the point. A Terraform for config management sounds grand, but this just seems like a collection of Python classes.

While the network bit is valid, it implies that networking in smaller areas can't still have the same impact in cost adjusted terms, meaning that while your lifetime earnings may be 20% lower, if you're living in an area with 20% lower cost of living its a wash.

When combined with a generally snooty attitude about "small pond" people, it seems like you simultaneously feel that you're going to be the smartest guy in the room and yet aren't smart enough to see the MASSIVE potential benefit of that in a smaller pond. If you have even rudimentary soft skills you could end up a VP of a Raleigh or ATL based company while possibly never even making it out of middle management in SF.