spjt

The worst thing I have ever seen is Plaid. I was trying to fund a brokerage account last week, this window pops up asking for my bank account login and password... Uh, no?

What usually happens to me is, I get stuck where whatever service I'm using insists the password must be changed RIGHT NOW before proceeding. There was something I was trying to do. Maybe I don't have a pen, I'm on my phone, whatever, I don't have time for this shit. I need to change it to something I will remember, which is something like "Password1". Maybe I remember to pick a better one later, maybe I don't. Maybe (looking at you, Okta) I can't change the password because I changed it too recently...

I guess I just don't see much value in using enums at all. My most memorable experience with them is when our production system went down because a third-party service added a value to an enum.

LLM "safety" (censorship really) is stupid anyway. It can't create new information, therefore all the information it could give you is already available. There are plenty of uncensored LLM's out there and the world hasn't ended.

Code formatters are the best of both worlds. I despise Allman-style indentation for reasons I can't explain or justify, but if I have to work on a codebase that uses it, I can simply put hooks to reformat it to whatever the repo style is before commit.

The purpose of writing is to produce something to be read, and typesetting is an important part of making a document readable.

It is incredibly irritating if I need to reformat code to be able to read it clearly before modifying it, then have to either back out all of the formatting changes to create a clean PR that shows the actual change, or create a PR full of formatting changes with the actual logic change buried somewhere within.

I would pay more for a slower ride just to avoid having to pay a tip.

I would be very wary of relying on anything from OpenAI, pricing and availability can change at any time.

I also know almost nothing about insurance other than what I've observed as a policyholder. Two things I would note though:

1) Maybe there needs to be some adjustments to how risk pooling is done. I live in Florida, so my homeowner's insurance is ridiculously expensive, but my property isn't really at risk from hurricanes etc, being very far inland. Realistically my property isn't any more at risk of anything than any property anywhere else in the country.

2) There doesn't seem to be enough flexibility in the offers. Most people seem to think insurance should cover any losses, but really people only need insurance to cover losses that they cannot recover from. I'd take a $100K deductible on my homeowner's insurance if it was offered and lowered my premiums significantly, but it's my understanding the law won't allow that.

All that is needed is a willingness to be broke. The only reason I can't change careers is because it might take years until I get to the point where I could make enough money to pay my mortgage, but that bill comes due every month.

> single-maintainer projects (or subsystems, or packages) will be seen as risky

I would actually see a single-maintainer project as less risky. Looking at the XZ backdoor issue in particular, nobody even knows who the person is that introduced it. With a single-maintainer project, you only have to trust one person, who is often a known quantity.

My estimation technique is to completely ignore the nature of the task, and instead just try to figure out the highest number the person asking will accept.

Not really a "company" but any number of OSS projects. Linux etc.

> people perceive all these tiny non-verbal signals like changes in posture, gestures, mimics, breathing,

I don't know what line of work you're in but I would consider that stuff "noise" in a technical discussion.

My solution was to not have any windows.

My solution is to not have any windows.

FWIW, I have three kids so I've had to repair a fair share of broken phones. Two kids have Galaxy A52's and one has an iPhone 7. The A52's are WAY easier to work on.

At least in my line of work, the utility of the telephone is one-sided and the utility is not on my side. It allows any random jackass to force me to drop whatever I was doing and remotely stand over my shoulder breathing into my ear while they wait for me to look into their problem.

They have to say that anyway, because Microsoft is acquiring Semmle, not GitHub. It is joining the GitHub "product family".

Looking at the announcement it seems they're basically folding all of the Windows-specific stuff back into .net core. Isn't that just going back to a compatibility minefield?

Sounds like he just needs to learn how to lie better in a job interview.

Sony makes other stuff.

It will if/when Crostini becomes mainline. For now, I'd agree - the iPad has a browser, and that's all the Chromebook has.

Sounds like a great idea but when you feel that crappy it's going to be almost impossible to arrange that. The last time I was seriously depressed I actually managed to call a few places, soonest anyone could see me was like three months out. I just ended up drinking very heavily, fortunately that seemed to work.

If it was easy, you wouldn't need a webpage with a configuration video tutorial series to convince people of the fact.

I can speculate as to why this would happen. People expect unit-tested code to have shorter methods because it's easier to write tests for shorter methods.

However, writing a new test for a new method can be harder than just stuffing that code in some other method that already has a test. Depending on how testing is enforced, you might be able to at get away with not having to do anything at all if the existing test still passes. If you're in a hurry and the test fails, just change the assertion to whatever happens. Is it right? I dunno, the test says it's working.