erik_seaberg

Hi, all I can see is a "join group" button that seems to depend on an instant messenger that I don't use. It's not clear what features your platform has, or how you and the coaches get paid while avoiding conflicts of interest (a frequent problem in financial advice).

I remember hearing that Microsoft was excited to get full NT builds below 24 hours.

Some companies might make you hold for a few months until the next earnings report and trading window. After that it depends on your tolerance for risk and your attitude about the IRS.

If LLMs start thinking, we should expect to see entire new industries that didn't used to exist because they required too much menial work.

But that's a big "if." They seem to be parroting stuff without knowing or caring what's true.

Every service is either deprecated or not ready yet.

"Now, this is only temporary ... unless it works."

"Do we really need to test all our code?"

"No, of course not! Only test the code that's supposed to work."

I don't know about routine skimming of history, but promo committees in big tech look at both commits and code reviews (the comments you left on others' commits).

This. Since 2008 I've worked at one company using a Perforce derivative and three others using Gitolite or GitLab privately, but never GitHub. Maybe commit history matters to recruiters, but I've been on a lot of interview debriefs (discussing whom to hire) and it never came up.

Oddly, C-g in Emacs isn't idempotent when it's hung or doing something slow.

https://www.gnu.org/software/emacs/manual/html_node/emacs/Em...

There's actually a list, but it's really big and includes possible exposure to toast (acrylamide) and beer (ethanol). There's also no compensation or incentive for doing any work to prove that a warning isn't justified, so everyone errs on the side of spamming them everywhere.

Each time you do this, you're forcing someone to forget whatever he was in the middle of doing. In the best case, your interruption might be for a much more urgent project, but often it won't.

> A single meeting can blow a whole afternoon, by breaking it into two pieces each too small to do anything hard in. - https://paulgraham.com/makersschedule.html

Title is pretty misleading without "Photos Purport To Show Damage" when the article is debunking old or mislabeled photos (one was identified as a Russian refit and another was a videogame?)

There was an HRXML spec back in the semweb era, I've always wondered what happened with that.

The optimal vacancy rate isn't zero, renters (and relocating homeowners) need to be able to move and to reject bad landlords.

With an MMU, segfaults cause pretty abrupt and obvious failures for straying outside the heap or stack. Violating memory safety may cause subtle and unpredictable errors even in correct functions, which is a lot more dangerous.

Buying a house in walking distance isn't crazy when you get a private office with a door, and can expect to keep it for life.

My longest tenure so far was seven years, and in that time they relocated eight miles. Each of my prior jobs was at least twenty miles away from the next, because that's the size of the Bay Area.

This is a three part series about language-neutral ABIs. It should probably evaluate https://en.wikipedia.org/wiki/SWIG and C# as possible solutions.

It's light, and some animals can see it, just not us. https://en.wikipedia.org/wiki/Infrared has some pictures from the right kind of cameras and telescopes.

Sure, but the curbs three blocks away do not, and around here there's been no progress towards building it.

The performance of the happy path matters a lot more, and I don't know of any compiler smart enough to return to different addresses for good and bad error codes. How much is the penalty for always checking a code after returning, compared to a try block that didn't catch anything (which should be free, apart from a compile time unwind table)?

I've seen https://en.wikipedia.org/wiki/AAA_(computer_security) because authentication, authorization, and accounting (audit trails) need to go together so often. You need to know who they really are and whether they're abusing the system.

HTML 5's error recovery pseudocode replaced the formal grammar that HTML 4 had, and in authoring I find it harder to take guidance from.

Yeah, I'd heard good things about the Mercurial UI but bounced off when "how to branch" turned up https://stevelosh.com/blog/2009/08/a-guide-to-branching-in-m... with not one but three radically different answers. Seemed somehow unfinished to me.

> In the middle of delivering a lecture, Hardy arrived at a point in his argument where he said: "It is now obvious that..." Here he stopped, fell silent, and stood motionless with furrowed brow for a few seconds. Then he walked out of the lecture hall.

> Twenty minutes later he returned, smiling, and began: "Yes, it is obvious that..."

Do you find that better than a stash or a branch because it shows up in ls?

Git is well worth learning for any kind of collaboration or speculative work. It's fundamentally better at resolving merge conflicts, because it doesn't rely on being informed about which files may have been moved or copied. The Subversion maintainers owe me days of effort salvaging my small team's branches.

I nohup anything slow that isn't interactive, it's POSIX and the logged output might be useful if it dies halfway.

Brother was good for a long time but they seem to now lock out competing ink and/or toner cartridges with DRM: https://news.ycombinator.com/item?id=31860131. I suppose I'll get an Epson ink tank next.

Brother's USB drivers have also dropped support for some old models, though I guess newer hardware all uses IPP (until that goes obsolete).

W3C laid the groundwork for everything on the Web to be heavily cacheable, so it's weird that there are so few general-purpose proxy caches. Are publishers sending short "Cache-Control: max-age" or "Vary: Cookie" responses when they didn't need to? Are too many ISPs paying for transit rather than peering?