HN user

hackpelican

109 karma
Posts0
Comments34
View on HN
No posts found.

What you’ve hit is uneven extraction. Parts of the puck were over extracted and other parts under extracted.

Usually the cause is channeling, where some pathways in the coffee puck are easier for water to get through, so they get eroded first which leads to even more water going through these channels. Coffee around these channels then gets over extracted (bitter).

Conversely, much less water is reaching the other parts of the puck, leading to those parts getting under extracted (sour)

Better puck prep helps. Using a WDT tool (some acupuncture needles on a cork would do) or a blind shaker to break up the clumps leads to good results. Making sure the surface of the puck is level after tamping is a big one as well.

What also helps is going coarser in the grind. The coarser the grind, the less puck prep matters and the less channeling occurs. Warning, you’ll no longer be getting the thick crema you may associate with espresso, or the instagram worthy beautiful rat tail extractions. But the coffee produced from coarse grind espresso is IMO much better.

I was taught a lot of this by Lance Hedrick and I applied these learnings to achieve mostly consistent fruity and sweet espresso on most mornings.

Muslims don’t believe Arabic is the language of God. They believe that the Quran was revealed in Arabic (true). Thinking the creator of the heavens and earth only speaks one language is absurd. It also kind of implies that Muslims believe in a superiority of Arabs which is also not true.

Weird to say Arabic hasn’t innovated or evolved considering the wild variety of dialects spoken in the modern world.

Conflating the language with the script is also bizarre. In terms of adapting Arabic to technology, look into romanized Arabic which was used before Unicode was common.

I hope you’re still joking.

Data caps are to an extent “fake”, in that telcos’ costs aren’t measured in how many bytes their customers download/upload. Telcos’ costs come from renting bandwidth from tier 1 and tier 2 ISPs. This bandwidth is constant.

And for popular websites, they will cache lots of content on their own network or peer directly with data centers so they don’t have to pay for the bandwidth there. The routers will continue routing and the switches will continue switching whether you download 5GBs or 5TBs.

One more way to understand how much of a scam mobile data caps are, is that the same ISP will sell you unlimited fiber plans even though essentially your traffic goes through the same backbone.

Data caps may help lessen congestion on their cell towers, but they don’t need to be as low as they are today.

How does routing work?

How do I know that for device A to reach device B, I need to go through device C but not D?

And if I try to go through device D but device C actually delivers the message, then does device D get paid? How would you validate which devices actually participated in the transmission of the message? How does this not turn into a privacy nightmare?

It was definitely a bad system that leads to wrong incentives.

Due to this, a lot of the time, leaving a comment would lead to friction with the owner of the CR, thus disincentivizing leaving comments, which leads to worse code being merged.

In some companies, (ahem… Amazon), engineers are judged by their code review/comment ratio. Especially L4 engineers trying to make it to L5.

So actually putting positive comments in the code review isn’t really much appreciated.

I gained this habit and now for me, a comment is a suggestion of improvement, I deliver praise out-of-band.

In the places I’ve worked, a war room was always the place where we cut the bleeding and revert the system to a working state. Never was the RCA the intended outcome of a war room, though we’d often reach the RCA in the silence of the meeting bridge while something deployed/rolled back.

Root cause analysis is definitely not a group activity, it’s best done in a place where one can have complete focus.

However, cutting the bleeding requires plenty of communication, weighing different options, having a higher-up sign off on a tradeoff, getting our ops team to coordinate towards some common goal, monitoring the recovery… etc.

I categorize myself as a “don’t care, would use whatever the codebase is using”.

But I realize now that I rarely press tab or space when I indent. I find that most of the time, I am either leveraging auto indent, or using vim’s/IdeaVim’s >> and << commands to indent. At this point, I honestly have no idea if I’ve been using tabs or spaces in the last 6 or so years.

Architects produce buildings. These buildings are useful and remain useful for decades. We build software that may be useful to the average joe at first, but it's only to acquire users. Then the enshittification cycle begins to extract as much value as possible from said users. It's not the same.

We can sit here and provide examples of software that is useful, safety-critical, etc. And you're right, there is a lot of software out there keeping people alive in automobiles, airplanes, medical equipment etc. But this software is not borne of the tech industry culture, but rather one engineering culture or the other. Not the programming that I or most programmers do.

Policing is definitely a real job. Though abusers are plentiful, the ones harming society are rightly called abusers. Programmers writing software that harms society are just regular tech industry professionals. Same as banks that invest in companies profiting from apartheid systems or from destroying the environment.

I don't think I'm being unfair when I compare the morality of your average tech industry professional with the morality of your average finance bro or investment banker.

I have long since disabused myself of the notion that programming is morally anything more than a job in finance, investment banking, or any other bullshit job.

Bullshit jobs, as opposed to real jobs, don’t benefit the community the way a doctor, a teacher, a plumber or a farmer does. Bullshit jobs are there to make the boss man rich by inventing mechanisms by which money is funneled from the general public to a few elite pockets.

I think this is also in part why dreaming of buying a farm and living off the grid is common among programmers.

The 2017 MBP is indeed horrible hardware. You’ll find many testimonies of 2012-2015 MacBooks being incredibly resilient.

The new 2019-2023 models are too recent to judge, but seem to be back on track resiliency wise.

I hope Apple never releases a touch screen MacBook. MacOS is the only operating system that still has UI elements appropriately sized for mouse use. Everything else uses huge buttons to account for touch use-cases.