They were done the minute mods broke their habit of moderating their subreddits. Some dedicated mods might come back, but it is really hard to return to a lost habits so the damage is done already.
Probably blankets embedded with a conductive metal mesh in a pattern designed to block microwaves could be issued to all US personnel in foreign countries.
I remember on my first year here in Texas, driving by Arlington's city hall and there were a bunch of second amendment rights guys protesting outside, armed to the teeth with assault rifles and camo pants.
The police in their HQ right across the street didn't seem bothered by it so I assumed it must be legal.
Just want to point out the law allows unlicensed carrying of a concealed firearm, keyword here is concealed.
It is my understanding you already can walk around with a firearm anywhere in most US states that don't ban firearms as long as is not hidden from view, all this law changes is the requirement to get a license if you intend to walk around with a firearm concealed.
> If so many people have trouble implementing agile maybe it just doesn't work?
The problem with agile and other empirical processes of project control is that it goes against the OCD tendencies of scientifically minded people. They assume that, since programming is all math and logic, software development projects should be as well.
They add micromanaging processes in a futile effort to control what they perceive as chaos and end up trying to fit a square peg in a round hole.
> However, after seeing how badly it can be weaponized against developers, I'm certainly ready to throw out the bathwater, and I think this is what they're talking about.
Poor management is a separate issue from agile. Even so, I would rather stay on a poorly managed agile shop than go back to a waterfall shop.
As far as the "values on the left", I like to explain them as a 55/45 split (and adjustable depending on your reality): we still deal with processes and tools, we just take a second to think whether a process is actually needed when we can just talk to someone instead.
Example: on a small team, you might just ask "can someone please approve my changes?" instead of having a whole jira workflow with code reviews and approvals.
> Also I think the comparison to lean manufacturing has always been very shallow. I get the metaphor, I just don't think that human resources in engineering can be optimized like manufacturing processes.
Agile and Lean are empirical process controls, they are based on the same concepts. Ken Schwaber explains all this on the first chapter of his book "Agile Software Development with SCRUM":
Defined process control: same inputs always result in same output (manufacturing widgets on a production line).
Empirical process control: same inputs not always result in same output.
Schwaber conceived SCRUM (and was among the founders of Agile) after realizing software development required an empirical process control: give 2 dev teams same specs, 2 different apps will come out (they might do the same thing, but in different ways)
Every time I see an "agile sucks" post, I take the time to read it and every time (so far) I have found they blame the process for some key part of agile they missed. Quote from the article:
“Way too much of Agile has been not about technology, but about people and about managing things and about getting stuff done — not necessarily getting the right stuff done.”
This is the whole point of agile: progress on iterations, inspect and adapt at the end of each iteration.
Your team might build the "wrong stuff" for an iteration, realize it (inspect), then make a course correction (adapt). If you end up delivering the "wrong stuff" is because you didn't follow this very core principle of agile.
I find it hard to believe these so called "Agile Early Evangelists" can make such a statement. Their background in lean development should have made the familiar with empirical process controls, from where lean and agile come from.
My guess the author quoted them selectively to fit the "agile sucks" narrative of the article.
In agile, or any other project management process, the "customer" is not necessarily just the final user but any stakeholder.
As a rule of thumb: anybody who needs regular progress updates on a project is a "customer".
The difference in agile vs other development processes is progress reports are partial releases of working code instead of a percentage increase on a gantt chart.
I can confirm, I have grid-tied solar panels and have gotten outages in the middle of sunny days which is usually the time my panels are actually supplying surplus power to the grid.
Only way to have juice during power outages in my configuration is to add something like the 7K Tesla battery.
This is a good idea, but i think it could go even further.
Somewhat unrelated but if you really want to see how horrendously unfriendly the typical smartphone UX is, hand one to a technology-challenged grandparent (who can probably use a legacy cellphone/flip phone just fine) and ask them to call you.
They are more likely to accidentally take selfies than figure out how to call you, even if they have your phone number memorized.
It would be nice to have an android "main menu" which is just simply the dialpad when you turn on or unlock the phone. Add a button for "smartphone things" like search contact list or open other apps but keep it most elemental function (making phone calls) up front and and easy.
Rolling their own health care company might solve only part of the issue. I think the largest driver of healthcare costs right now is price gouging by providers with their charge masters, needless exams and procedures.
I have been thinking on a "simple rule" that could mitigate gerrymandering:
1. No congressional district can span more than 1 partial city and/or county.
This will force districts to be drawn to cover whole cities/counties and would stop ridiculous districts such as the Texas 34th which covers parts of at least 8 counties from the gulf coast up to San Antonio
> It also doesn't seem like the internet regulatory state of pre-2015 was a disaster.
This is a common inaccurate argument I have seen pushed by the telcos to justify repeal.
There are many well-documented cases of how the "big 4" ISPs were increasingly blocking, redirecting (Charter's DNS redirection), interfering (injecting javascript and/or ads) and throttling traffic to internet services (Netflix) from their networks before the Title II reclassification of 2015.
All these abuses happened during a small window of a couple years between the previous FCC's Net Neutrality regulations were thrown out by the courts and 2015, when the Title II reclassification happened.
Based on what happened in the south of Chile, I think they might want to wait a couple more decades before claiming escaped salmon didn't gain finhold in the wild:
My uncle was among the pioneers of salmon farming in the south of Chile on the early 70s. A storm destroyed their first farm causing salmon to escape to the ocean. The escaped salmon (chinook) started showing back in noticeable numbers just around 10 years ago.
The article's title seems click-bait. It makes good points identifying some of the already known weaknesses in bitcoin's design, but he is basically complaining that Satoshi didn't predict how his creation would evolve over time which seems unfair.
Maybe we don't need a unique id at the federal level after all. Financial institutions are already required to follow KYC (Know Your Customer) laws. For this they need a way to validate the identity of the customers they do business with. I guess they already have enough ways to do this without relying on SSN or a potential national id card.
BTW, after the Equifax hack, financial institutions should be mandated to stop trusting SSN as proof of identity.
> Lenny actually changes it's response depending on what the caller does. Pauses, keywords, etc.
It's actually a sequence of recordings played in the same order every time in a loop from the 5th. Telemarketers usually realize it a few recordings into the second loop.
Now imagine combining machine learning with conversation analysis to create the ultimate Lenny.