The situation you described doesn’t sound like “Right Way Guys”. It actually sounds like “Bikeshedding” [1]. This means giving a disproportionate amount of attention or importance to the trivial details while neglecting or giving less attention to the significant issues.

Imagine a committee commissioned to approve plans for a Nuclear Power Plant. But the committee spends all their time discussing the color of the bike shed that they want built nearby.

In your case, their focus on separate VMs for QA/Production, systemd deployments, templating system for a few strings, and an ORM for a few SQL queries, especially for a project with a limited user base (10 people) really exemplifies Bike-shedding.

They’re emphasizing minor, arguably unnecessary details rather than the core functionality or purpose of the project [2]. This usually occurs because these trivial aspects are easier to understand and discuss, especially for junior devs, which leads to increased involvement on minor details while the more meaningful parts of a project (which might be more challenging to address), are overlooked or given less attention.

IMO, a good leader knows how to strike a balance between the “Right Way” and avoiding the pitfalls of “Bike-shedding”.

[1] https://en.wikipedia.org/wiki/Law_of_triviality

[2] I would argue complete documentation of the meaningful parts of the project is not bike-shedding.

Bikeshedding is the act of debating trivial details. They're just overcomplicating something that should be simple, but it doesn't seem like there was much of a debate about it at the time, so it's not bikeshedding.

It sounds more like a case of "Use the tools you know". Like, the stated ORM toolkit may be complete overkill, but if they don't have experience doing object relational mapping by hand that's one more thing to learn to get the job done. The asserted goal is to deliver something for a group of people to use, so it's not a hobby of trying to find as many new lessons to learn as possible.

I see it funny when this behavior is assigned as one of symptoms of quite quitting, and Allies advice to rebellious German workers in WW2.

Sounds more like scope creep (due to "Right Way") rather than arguing about details.

Not having separate VMs for QA and Prod seems like madness to me

which model regurgitated this reply ?

>and the ability to have different tips on them to increase fit for more people and to provide the option of sealing out outside noise.

This is the single biggest reason why I won't upgrade to the AirPods. For me, the AirPods simply fall out of my ears. That's why I stick with the Etymotic Ear Phonnes: https://www.etymotic.com/consumer/earphones.html

For whatever reason, that flanged shape fits my ears so perfectly well and blocks out all other noises that I don't see myself using any other Ear Phones for a long while. If AirPods provided the option of a flange shape like the Etymotics, then I'd be compelled to buy an AirPod.

This is a really good point and I'm not sure why you're being downvoted. Think of it this way, who the heck approves of an Incident Response Policy or an Information Security Policy without reading it? Oh wait, your downvoters would approve an Incident Response Policy without reading it, /facepalm.

She was talking to citizens, not to congressmen.

Why does that matter?

Because in context, “We [legislators] have to pass the bill so that you [citizens] can find out what is in it” does not at all imply that congressmen don’t need to read the bill.

How does GDPR play into the requirement to store passport numbers?

If there’s a legal requirement to store passport numbers you can store them. It’s one of the cases where you don’t need consent. You still have to store them in a safe fashion and the customer still retains most of the rights under GDPR (information about what you store and for which purpose, etc.)

It plays. The way these hotels are doing this maybe probably isn't GDPR compliant, but the same applies to vast amounts of other things.

Hard to share any very useful insights on this, it's just the state of most things.

Can GDPR be used as an audit mechanism for breached passport numbers? And if so, what would that process look like? Can hotels be fined if they’re found to not be GDPR compliant?

>Can GDPR be used as an audit mechanism for breached passport numbers? And if so, what would that process look like?

I'm not quite sure what you mean, but the answer is probably no.

>Can hotels be fined if they’re found to not be GDPR compliant?

Sure, but is anyone GDPR compliant yet? I'd imagine that all the DPAs in EU are extremely busy right now.

Yeah but all of a sudden this new title seems waaay more interesting considering the recent journalist describing his experience working as an Amazon Flex Driver. Just saying.

Nutrition Label upfront, in words and text. I know there is a picture but I missed it, some of the nutrition labels are like the 4th picture.

Some of the starter packs don’t have nutrition label on it either.

Great feedback. We will update our website accordingly!

Don’t encourage heavy handedness by the government, instead push for a better system of checks and balances.

>> California should exercise their eminent ___domain powers and purchase it for what it's worth.

> Don’t encourage heavy handedness by the government, instead push for a better system of checks and balances.

That's not heavy handedness, it's calling a hyper-rich entity on its greedy, obvious bullshit. It'd be a welcome lesson to all to all such organizations.

I'd also say such eminent ___domain actions would be a reasonable part of checks and balances: no one would under-represent the value of their property, at least not as much as Apple has, if they invited that kind of risk.

I think it was sarcasm to prove a point. If the government did it, it would be outrage, but the reverse, and it's just business being "efficient".

>Coverage is a measure used to describe the degree to which the source code of a program is executed when a particular test suite runs. A program with high test coverage, measured as a percentage, has had more of its source code executed during testing, which suggests it has a lower chance of containing undetected software bugs compared to a program with low test coverage.

In case folks are wondering about what we mean by coverage...

PS. Love Rails.

Double Pasta, now that’s embarrassing.

I think issues left open > 12 months is antithetical to the idea of lean/agile and could be a sign of suboptimal project management.

But don’t get me wrong, I <3 Ruby and am excited about Crystal.

>issues left open > 12 months is anti-thetical to the idea of lean/agile

OSS doesn't care about lean/agile, those are ideologies consultants sell to enterprises.

Things are done when they are done.

> I think issues left open > 12 months is antithetical to the idea of lean/agile and could be a sign of suboptimal project management.

Totally depends on the nature of the project, its policies and users.

Any popular FOSS project that allows anyone to post a bug, and doesn't just close unattended bug reports (which is bad imho), is likely to end up with some (usually minor) bugs open over 12 or more months.