chaps

Sure, but there are some jobs that are so bad that this advice readily applies to. The sort of job that takes you away from your life, family and friends in a way not entirely unlike poverty does. It's good to recognize whether working somewhere will turn into this because it's... hell... working at those places.

Bows and arrows are still widely used for hunting all over the world. I was able do freelance work on a relatively low income because of access to ~150lbs of deer meat that came from multiple bow-hunted deer.

Presumably it's a system that can be viewed from a phone or from dispatch remotely right? All they'd have to do is share the credentials and that's that.

A weird tradeoff but an increasingly important tradeoff to keep in mind nonetheless. Like I said, updating immediately isn't a perfect answer. But neither is waiting. I hope you're having this discussion, at least.

Worked at an exchange in 2007/2008 and... we had systems still running from the 80s. Mostly tape audit stuff.

That honestly sounds amazing. Imagine booting into something like a grub menu that's just a list of classic games.

No, this is not always the case. Regulated industries pin their package versions and store those versions for pulling.

Friend, considering the supply chain attacks going on these days, automatically updating everything, immediately, probably isn't the perfect move either.

Your question feels insane to me for production environments. Why aren't you doing a version cutoff of your packages and either pulling them from some network/local cache or baking them into your images?

Sure, but you're just shifting that cost elsewhere. Not defending the no-code services (they're extremely predatory), just that it's not as simple as cost-vs-no-cost.

These days I think airtable and other "no code" systems fit this bill well.

On the flip side, every single MSSQL instance that I've encountered has been legacy. For at least five years.

Honestly I'm not sure. I think I include them under the same umbrella because how often they work together, plus all the systems integration that they have together.

Someone once dropped some fireworks not too far from me at 3am a few years back. They were loud and, yeah, cops were called. A few minutes later about five cars drive past me about 30mph over the limit. Not sure how they didn't see me or try to see me. But I know they didn't catch the BRIGHT orange and lifted care.

Me being me, I submitted a FOIA request for the dashcam footage of the five cop cars and the dispatch logs.

Instead of pulling over the easily identifiable car, they pulled over some random guy. They were behind him the whole time but five cop cars pulled behind him thinking that he fired a gun a few minutes back.

He was let go without a citation, but the official reason, despite being paired with the dispatch for the firecracker, was a broken headlamp.

Yikes. Have a good one.

Sigh.

Look friend, I really hope you can realize how you sound in your post. You're extraordinarily confidently saying that you refactored some ambiguous endpoints in 30 minutes. Whenever I see someone act that confidently towards refactoring, thousands alarms go off in my head. I hope you see how it sounds to others. Like, at least spend longer than a lunch break on it with just a tad more diligence. Or hell, maybe even consider LIEing about how much time you spent on it. But my point is that your shortcuts will burn you. If you want to go down that path, I'm happy to be a witness to eventual schadenfreude.

My issue isn't with the fact that you used AI. My issue is with how confident you are that it worked well and exactly to spec. I'm very well aware of what these systems can do. Hell, I've been able to get postgres to boot inside linux inside postgres inside linux inside postgres recently with these tools. But I'm also acutely aware of the aggressive modes that these systems can break in.

So again, which company should we all avoid so that we can avoid your, specifically your, refactoring?

It's because you're deflecting. :)

I mean, I'm always down for learning something new. But I hope what I learn includes the name of the company I'd like to avoid.

Which company do you work at so we can avoid your migrated endpoints?

I play roguelikes tons and agree with the article's analysis.

A lot of these games feel like the "game loop" only exists as a project management tool to refine the game's release rather than to refine enjoyment. It's made so much worse with games that are in early development where EA feels like just a refinement of the loop rather than refinement of enjoyment .

It's hard to explain, but it feels like a symptom of loop focus over gameplay is that the game peaks suddenly and hard but expects you to keep going.

A game that illustrates how to break past that point is noita -- there's definitely a gameplay loop.. but it's made in a way where the loop is eventually recognizable as not actually the full game. It then goes from being a gameplay loop to a stream of play that doesn't need to loop on itself.

Really, I wish game devs, both indie and otherwise, would try to break out of these loops more readily.

How exactly does this provide more surveillance of the police themselves? I've done about ten FOIA lawsuits against police departments and it's laughable to think that they won't just lock footage away and exempt it from the public's eyes. Probably through a trade secret exemption because private companies are involved.

There's more than one definition of missile. Florida criminal code's just one place where a drone could be considered a "missile".

Florida criminal code:

  "790.19 Shooting into or throwing deadly missiles into dwellings, public or private buildings, occupied or not occupied; vessels, aircraft, buses, railroad cars, streetcars, or other vehicles.—Whoever, wantonly or maliciously, shoots at, within, or into, or throws any missile or hurls or projects a stone or other hard substance which would produce death or great bodily harm, at, within, or in any public or private building, occupied or unoccupied, or public or private bus or any train, locomotive, railway car, caboose, cable railway car, street railway car, monorail car, or vehicle of any kind which is being used or occupied by any person, or any boat, vessel, ship, or barge lying in or plying the waters of this state, or aircraft flying through the airspace of this state shall be guilty of a felony of the second degree, punishable as provided in s. 775.082, s. 775.083, or s. 775.084."

Got it, a surveillance missile.

I'm sorry but, in what way is a swarm of surveillance drones NOT a mass surveillance system?

Kind of. Motorola (axon) effectively acts as an integration system for flock and about 20 other services. Motorola's stuff is IMO the bigger problem because it includes access to flock.

yes, people tend to act differently. not the people they're trying to afect, just random people just minding their business. but it is not an effective deterrent to things like "violent crime".

• Meta-analyses (studies that average the results of multiple studies) in the UK show that video surveillance has no statistically significant impact on crime.

• Preliminary studies on video surveillance systems in the US show little to no positive impact on crime.

https://www.aclu.org/sites/default/files/images/asset_upload...

Speak for yourself, big-holes-in-ground are very valuable to me.

I don't have much advice here because ever situation is different and the sensitivies of asking is different with every organization. What's worked for me is being absolutely direct and honest in the situation and the urgency of needing pay. Often times the other side doesn't realize how much it affects you, and shattering that illusion is what's needed. In other words -- you kinda need to make them feel like an asshole for not paying you. Sometimes it doesn't work, though. At some point you will need to raise it as a legal issue and begin refusing work.

Good luck!

Then you might be surprised to know that a lot of those numbers were exaggerated. If you're trusting people to tell you accurate things based on numbers that they won't share.... you're gonna have a bad time.

https://www.nytimes.com/2023/12/08/business/organized-shopli...

You're missing my point again.

My privacy problem exists with third parties AND internally within OkCupid. At some point, running NLP over messages necessitates that an analyst or ops person actually has to look at the underlying data at some point.

The 3rd party stuff just exudes something like a privacy "code smell" -- "orthogonality" doesn't really matter to my point because 1. these things don't exist in a vacuum and 2. stench has a way of permeating through layers, regardless of how orthogonal underwear is.

Like, do you trust that OKCupid staff didn't download user messages to their laptops?