What I can tell is ICE starts to open a door, and a clerk immediately stops them and ICE shut the door a second later. The clerk opens the door to further tell them they are not allowed to enter. The ICE person states they will not try to enter and if the clerk touches them, they will yank the person out of the building. ICE then leaves.
I'm not ok with what ICE has been doing. But, it feels like a bit of a stretch to call this threatening staff, to me. Saying what will happen if the other party escalates feels like a different axis than threatening. Def taken as another data point in a sea of overreach however.
> The ICE person states they will not try to enter and if the clerk touches them, they will yank the person out of the building.
I'm not sure what the agent has to do to qualify as a threat to you, but at the very least this is thuggish behavior. The embassy is Ecuadorean sovereign territory where the staff have immunity from US laws, threatening to yank someone out of there is like extracting someone from Ecuador by force. It's highly offensive.
If you tried that at a US embassy you'd probably be shot, but it's generally impossible because they are all heavily secured and fortified.
I don't think that it's reasonable to see this behavior as anything but threatening given the location and the ample context provided by ICE's behavior up to this point.
> The ICE person states they will not try to enter and if the clerk touches them, they will yank the person out of the building.
> “The brand new agents are idiots,” an experienced ICE agent assigned to homeland security investigations told me.
> The new ICE officer continued: “I thought federal agents were supposed to be clean cut but some of them pass around a flask as we are watching a suspect,” observing as well that the new guys “have some weird tattoos.”
Did you drop a sarcasm tag? Anyone can make a fire on a plane as they allow lighters on a plane, and batteries, and any number of flammable objects. None of that is facing any scrutiny nor stopping crazy people from being crazy.
Ironically, both India and China forbid lighters on planes. Famously you see a collection of them around the bins just outside the airport as all the smokers leave them for others.
Yes it's possible to make a fire on a plane, but it would be even easier to cause a big fire if there was zero monitoring of bags. As flawed as airport security is, it should generally catch things like somebody trying to get a carry-on bag full of gasoline or extremely large lithium-ion batteries on board.
I take security that catches 50 or even 20% of threats any day over 0 security.
I've heard that cell phones often catch fire on planes, and the crews know how to deal with that. I guess they have to because the odds of one going up are pretty good across so many flights.
It's easier to deal if it's in carry on bag. This is why batteries are forbidden in checked luggage. Once it all burns the airplane has got to land asap and it's an emergency.
My checked luggage did not pass xray multiple times because they detected powerbanks. I had to come back and take it out. However it also did pass xray a couple times with powerbanks so it's not a reliable system.
> Well at least be honest that these things are organized professionally and funded with tens of millions of dollars
source? best I see from the linked fox news article is less than $8M. Note, we have customers sending marketing email and sms spending more than this and they are not getting the same attention No Kings did.
> though Soros' foundations have awarded grants to Indivisible every year since the organization's conception in 2017. In total, the Open Society Foundations have awarded $7.61 million in grants to the group behind the "No Kings" protest [1]
While good points are made, I worry this gives the wrong impression. The paper doesn't say it is impossible, just hard. I have, very successfully, worked with dev owned testing.
Why it worked: the team set the timelines for delivery of software, the team built their acceptance and integration tests based on system inputs and outputs based on the edges of their systems, the team owned being on-call, and the team automated as much as possible (no repeatable manual testing aside from sanity checks on first release).
There was no QA person or team, but there was a quality focused dev on the team whose role was to ensure others kept the testing bar high. They ensured logs, metrics, and tests met the team bar. This role rotated.
There was a ci/cd team. They made sure the test system worked, but teams maintained their own ci configuration. We used buildkite, so each project had its own buildkite.yml.
The team was expected by eng leaders to set up basic testing before development. In one case, our team had to spend several sprints setting up generators to make the expected inputs and sinks to capture output. This was a flagship project and lots of future development was expected. It very much paid off.
Our test approach was very much "slow is smooth and smooth is fast." We would deploy multiple times a day. Tests were 10 or so minutes and very comprehensive. If a bug got out, tests were updated. The tests were very reliable because the team prioritized them. Eventually people stopped even manually verifying their code because if the tests were green, you _knew_ it worked.
Beyond our team, into the wider system, there was a light weight acceptance test setup and the team registered tests there, usually one per feature. This was the most brittle part because a failed test could be because another team or a system failure. But guess what? That is the same as production if not more noisy. So we had the same level of logging, metrics, and alerts (limited to business hours). Good logs would tell you immediately what was wrong. Automated alerts generally alerted the right team, and that team was responsible for a quick response.
If a team was dropping the ball on system stability, that reflected bad on the team and they were to prioritize stability. It worked.
I've worked in a strong dev-owned testing team too. The culture was a sort of positive can-I-catch-you-out competitiveness that can be quite hard to replicate, and there was no concept of any one person taking point on quality.
I think some pythonistas maybe got their feeling hurt by your comment causing it to grey out.
Over the last 25 years in the SaaS world, I have never seen python evolve into a system that is easy to reason about and debug. It lets you do too many things. In over 30 cases, I have seen teams deliver better software faster in Go after replacing their Python.
https://www.theguardian.com/us-news/video/2026/jan/28/footag...
What I can tell is ICE starts to open a door, and a clerk immediately stops them and ICE shut the door a second later. The clerk opens the door to further tell them they are not allowed to enter. The ICE person states they will not try to enter and if the clerk touches them, they will yank the person out of the building. ICE then leaves.
I'm not ok with what ICE has been doing. But, it feels like a bit of a stretch to call this threatening staff, to me. Saying what will happen if the other party escalates feels like a different axis than threatening. Def taken as another data point in a sea of overreach however.
reply