dunk010

Air-source heat pumps give their worst performance when you need heat the most. Ground source doesn't vary year-round.

really ugly winter peaks

The problem is those peaks are at the exact same time you need the heat.

Name checks out.

Yeah, it needs heavy moderation to remove the worthless fluff comments so that readers get high signal-to-noise. You can think an idea is bad but, you know, you gotta say why and have a debate about the details.

When I was taken to the Tate Modern as a child I’d point at Mark Rothko pieces and say to my mother “I could do that”, and she would say “yes, but you didn’t.”

Yes, but you didn't https://www.signedoriginalprints.com/cdn/shop/products/wegot...

I've had to read so far down to get a single non-stupid, ignorant, or inflammatory comment. What's wrong with HN, jeepers. Some actual discussion of the thing itself and not just pearl clutching would be appropriate here.

I request you to publish it! :-D

Came to post that blog. It's awesome. Everyone should read it.

Perhaps you do ;-)

I think that the point here is that your domain registrar will pick up the phone if there is a problem, where Google clearly will not.

I worked at Last.fm from 2007 to 2012. The MIR team (think: research) developed a wonderful system called "RadioQL", which allowed you to stitch together custom ratio stations from any of a huge host of factors, joined together by AND, OR, and NOT. You could select artist radios, song radios, tags, and so on, but also combine this with things like the BPM or even some sentiment analysis. It was used a little bit inside some public-facing radio stations, but nobody outside of the staff ever got full access, and that's a tragedy as it was glorious.

Sure. I doubt that if some test at the moment takes an hour then you're getting much extra benefit at the five hour mark. The whole point of the time compression is to spread the grades out - along an axis different to "competence".

The whole thrust of the article is complaining about timed tests and some kids getting more time. That's doubtless unfair if some are overclaiming, but the real solution is to not do timed tests at all - they are only serving to produce an arbitrary bell curve so that some can have higher grades and get better career opportunities. Better to not have a timer at all, and let people's actual ability shine.

Nebula and Dante will do this for like $300, and you can get 30x coverage at every base or even 100x coverage if you pay a little more. The $1000 genome was here more than a decade ago.

I distinctly remember in one of his talks he said words to the effect of “I wrote corporate C++ and Java for years and eventually realised I had to do something else, or else quit the industry”. So he took a year long sabbatical and created Clojure.

It's useful to have as a resource that you can dip into; for instance to check a specific thing like "how fast do I metabolise caffeine (bad example as youc can get that from a SNV checking service like 23&Me. However, never ever EVER dump your whole genome into a program that will output every match for some potential condition. Now that's not for the reason you might immediately think ("Oh no look at all the bad stuff"), but rather because the databases that tools like this use are pretty chock full of junk where some researcher threw in a reference - along with a few thousand others - to say that their particular piece of research implicates this gene at this poistion with this variant. I've seen it with my own eyes, and a lot of it is very low quality. You therefore need highly curated databases where the genotype-phenotype associations are well-defined and thoroughly researched. You'll spend the rest of your life either trying to prove/disprove every potential false positive, or just worrying yourself needlessly. So, yeah, it's not a bad resource to have if you can be responsible with it.

Tailscale has that Taildrop thing now, too: https://tailscale.com/kb/1106/taildrop

I used to have mine in LaTeX, rendering a nice PDF. But here's the thing, you're up against automated CV parsing systems that you don't have any insight into - a total black box. And it's a different black box with every recruiter. If your CV fails to parse, then it kicks out into a manual system where the recruiter has to add it all in. And as the market isn't wonderful right now, I would lean into making your CV as simple and congruent with their systems as possible. Which is to say, maddeningly, you should Just Use Microsoft Word. I know, I know...

I've used this in the past, it's really great.

In case you want another of his videos and know much about eMacs then this one had me on the floor: https://youtu.be/urcL86UpqZc

If you could pre-sign the queries to prevent abuse (user edits to queries making them potentially slow) then IMHO it would be a nice idea in a load of cases. Datasette actually does this, though that’s aimed at a very specific subset of cases.

I think you’re somewhere off base here. Yes, you understand React very well, but many don’t. And HTMX gives you a lot of leverage without needing to (1) deal with learning React, (2) deal with all the extra baggage that comes with it (oodles of extra complexity and code)

Everyone wants to use k8s and like 1% need it in any shape or form. It basically acts as a conspiracy between otherwise-redundant ops level people and those running Kubernettes against the companies who have to pay for all this. Just use Fargate, and be done.

I remember this paper, and was at a company at the time that was one of the first to use MapReduce, so saw this all play out first hand. I appreciated the paper. Then and now developers rush to grab new technologies, especially those that stroke their ego-driven fantasies of “working at scale” without considering their underlying constraints or applicability. At the time this was published every company and startup under the sun was rushing to use MapReduce, most often in places where it wasn’t warranted. I’m glad someone surfaced this paper again; people still need to learn the lessons that it outlines. Microservices and k8s: I’m looking straight at you.

It’s a shame that most comments here are debating the meaning of “10x” and rather missing the point of the article. This one spoke to me completely outside of this productivity distinction. I’m forever finding myself doing the same; trying to rationalise dev envs, the write-once CI code that nobody will touch, or fixing egregiously bad tests. The author is right; nobody will thank you for it but it’s also crucial.

LSP is basically an open(-ish) source implementation of Google’s internal tool called Grok. Grok was made by Steve Yegge, a formerly famous tech blogger. Steve Yegge uses emacs, and half his motivation was to equalise editors by moving the language processing elements to an external place that’s shareable by all. He has a great talk on it: https://youtu.be/KTJs-0EInW8.

So it’s, like, not an accident that emacs can leverage this :-D. Though I never see anyone giving him credit.

Except plants increase the humidity, exasperating conditions.

The key is that if the contestant chose a goat then Monty is FORCED to reveal the other goat. It’s this which skews the odds. He has (often) added information to the game.

There are also chaperone proteins that help in the folding process: https://en.m.wikipedia.org/wiki/Chaperone_(protein)

Use reader mode.