Yes, but it’s a little worse than that. One might take that to mean environmental, congenital, or even genetic factors. But there’s more. Consider the role that trauma has to play here as it can directly cause arrested psychological development:
You’re not alone. I recall getting sniped from every direction at some points, with very tough 1:1 battles and boss battles that just kinda “happen” out in the open.
I mean, maybe if you bake a stone cold potato that was in the fridge and then cook it for two hours? But even then we’re probably talking about a handful of minutes at the most.
Which
car companybar did you say you work for?
A major one.
Just automatically started uploading everything on my hard drive to an account I didn’t set up
Wait, what?
Real question here: has anyone else had luck side-stepping the Live365 signup during/after install? I’ve done this, and I’m very confused that more people haven’t.
Hate that my government is apparently dead set on all of us driving massive trucks and SUVs spending thousands to money lenders, auto manufacturers, and dealerships over realist vehicles.
Doubly so if those parties are campaign contributors. Always follow the money.
a lot of devs love watching stuff like speedrunning
True, but some of them hate it. But with the growing presence of speedrunning friendly features in new titles (looking at you, Supergiant), I think that’s becoming less of a problem.
Either way, these “devs watch” reaction videos are fantastic.
Exactly. And while we’re educating the forum here, Wikipedia has the details on the loophole that circumvents this:
https://en.wikipedia.org/wiki/Gun_show_loophole#Provenance
Sometimes referred to as the Brady bill loophole,[9] the Brady law loophole,[10] the gun law loophole,[11] or the private sale loophole,[12][13][14] the term refers to a perceived gap in laws that address what types of sales and transfers of firearms require records and or background checks, such as the Brady Handgun Violence Prevention Act.[15] Private parties are not legally required by federal law to: ask for identification, complete any forms, or keep any sales records, as long as the sale is not made in interstate commerce (across state lines) and does not fall under purview of the National Firearms Act. In addition to federal legislation, firearm laws vary by state.[16]
I am not a lawyer. I do not sell firearms.
The gist I get is that this opens up enough loopholes to permit unlicensed mules/fences on either side of the transaction. Depending on what political leanings and circumstances are in play, this legal framework might actually encourage that behavior.
The problem is that requirements refinement has been unceremoniously dumped in your lap. The failure here is organizational; maybe you have a design person involved, maybe devs are expected to do this. Either way, your job now also includes communications.
One strategy I’ve used is to draw a low-fi example of what they’re going to get - Figma is great at this these days. Then I add it to the issue and push the whole thing back for early approval in order to suss out these finer points.
Not to come off as misanthropic here, but many people are hot garbage at describing what’s in their head. Most of the time, it’s all abstract concepts up there until you start asking the real questions. They really do need a whole-ass conversation to sharpen that mental image. Or in this case, what they want that feature to look like. Incidentally, this is also the reason why therapy is a thing, and why it takes people years to make sense of themselves, and that outcome is usually far more crucial than anything we’re doing at the keyboard.
Honestly I don’t mind the indentation since C isn’t going to give us many ways to address this with as little code.
That said, with compilers that are good at inlining trivial functions, I really do appreciate the “it does what it says on the tin” approach to using functions on things like this. Even if they’re only used once. Comments would help too.
The logic in these if statements is inscrutable on a cold read like this. To me, that’s a maintenance risk; imagine seeing a snippet this size on a PR. Having functions that name what the hell is going on could only help.
In a one-liner competition, sure.
In my codebase? I’d pull a “let’s linger after standup about your PR” and have the coder sweat through a 10 minute soapbox about nothing before laying down the law.
One nit: whatever IDE is displaying single-character surrogates for == and != needs to stop. In a world where one could literally type those Unicode symbols in, and break a build, I think everyone is better off seeing the actual syntax.
can also get a gun and blast these things before it gets out of hand
Honestly, I get the distinct impression that everything in the hunting section at your local Walmart is going to be woefully ineffective. May I recommend a defensive position with difficult to traverse stairs?
It’s even easier than that. Both of these genres have design features that require minimal balancing, making for an even faster dev cycle.
Roguelikes side-step the need for traditional game balance by providing meta progression and building inevitable-death-by-impossible-odds into the core game. For Roguelikes that actually have an ending, all the developer needs to do is provide enough meta progression perks to overcome the game’s peak difficulty, for even the worst of players. Everyone else gets bragging rights for beating the game faster than that. Either way, the lack of balance and “fairness” in the core design are features, not flaws.
Deck builders follow in Magic The Gathering’s footsteps: you never need to fully balance it. Ever. The random draw mechanisms, combined with a deep inventory of resource and item/creature/action cards, make it unlikely that a player gets an overpowered hand all the time. Pepper a few ridiculously overpowered cards in there, and it just feels more fun. Plus, if you keep the gravy train going with regular add-ons, the lack of balance is even further masked by all the possible choices. And yes, some player will min/max a deck at great personal expense and wipe the floor with their opponents because it was never fair in the first place, and doing so is a feature.
More like: it’s eventually going to break your weekend or even your whole week, but you don’t get to pick which one.
Edit: To put that in perspective, there are 260 working days in a year. Let’s say that you have just one of these hardware failures in a five-year career with the MTA. That’s roughly 1/1000 odds. If the lottery had chances like that, you’d play it every time.
My theory: the system they purchased was based on an older and proven design for railway automation and control. Add to that however said company/contractor was set up to support their customers (e.g. OS only ships on floppy). That said, I agree that ten years without so much as a drive upgrade is a bit long in the tooth for something that can kill people or become a logistic and/or political disaster if it malfunctions.
This is interesting. The longevity of this legacy tech may be secure if they use the right channels.
SoCal happens to have a very active retro-computing scene right now, much of which is in the bay area. If they can breathe life into an Apollo Guidance Computer, bog-standard floppy drives will be a piece of cake.
On the other hand, the same scene has modern emulation for just about every (popular) legacy media format imaginable. Upgrading the drives to use SD cards and USB thumbdrives is something they could buy off the shelf today: Apple II, C64, Tandy, misc. So there’s no reason to suffer through hardware failures when more reliable tech is available.
There are even commercial options out there. Example: https://www.shopfloorautomations.com/hardware/floppy-connect/
More: https://en.wikipedia.org/wiki/Floppy_disk_hardware_emulator
There’s also the concept of “build to sell” instead of “build to last.” Longevity of a company is not a consideration when the vulture venture capitalists see a bigger return in pawning off their investment instead of reaping dividends. Sadly, this outlook isn’t always knowable by everyone in said company. In my experience, it’s usually impossible to tell unless the company is already in the red or is about to be.
Sorry to hear about your friend. While I’m no doctor, that seems to fit the bill to me. I’ve known people that had other trauma when young, and yeah, maintaining healthy relationships seems to be the hardest thing for them. Your story reminded me of a lot.