ryan-duve

I just learned Erlang this year and I love the syntax. Ending expressions with periods took getting used to, but capital first letters distinguishing variables, non-rebindable variables, semicolons between function clauses, a lack of boilerplate (defmodule et al), a fraction of end keywords, commas separating expression, ... all make for a very fun to use and ergonomic language, IMO.

I haven't tried Gleam yet, though. I'm interested in the focus on simplicity but a little wary because I understand they sacrificed niceties to minimize the language footprint, e.g., pattern matching in function heads. I intend to give it a shot the next time I'm greenfielding something.

> Passkeys are passwords your second device makes/types for you, without you ever seeing it.

My bigger problem with passkeys is how there's no universal way to register more than one device (in case the first one is lost).

They're all set for the day. I probably wouldn't do it if I had to log in every hour.

My work ritual every morning:

1. Power on laptop (it is powered off every day at 5 PM).

2. Log into VPN.

3. Log into Okta.

4. Log into AWS accounts, one per container (about 7 or 8).

5. Log into Docker Desktop.

6. Log into AWS CLI to get daily credentials.

The whole thing takes about 3-4 minutes. A former colleague referred to this as my "mise en place", or my daily arranging of my working environment. Like the article suggests, I find this offers me a "centering" before I open my email, calendar and missed chat messages and get started for the day.

[666]

I only spent a minute on the trainer, but my recommendation is to change the user experience from "type M 5 times in a row" to something like "get to the target with a single keystroke". Without any expertise is making a Vim training program, I feel like showing someone a goal and having them think of what keystrokes gets them there will be more effective than telling them the keystroke and having them type it 5 times consecutively.

Good news: no p-value threshold needs to be passed to switch from one UI layout to another. As long as they all cost the same amount of money to host/maintain/whatever, the point estimate is sufficient. The reason is, at the end of the day, some layout has to be shown, and if each option had an equal number of visitors during the test, you can safely pick the one with the most signups.

When choosing one of several A/B test options, a hypothesis test is not needed to validate the choice.

I wonder if the author would have thought Pandas feels less clunky if they knew about `.eval`?

    import pandas as pd


    purchases = pd.read_csv("purchases.csv")

    (
        purchases.loc[
            lambda x: x["amount"] < 10 * x.groupby("country")["amount"].transform("median")
        ]
        .eval("total=amount-discount")
        .groupby("country")["total"]
        .sum()
    )

> The current 9-series configuration, which will end with 9ZZZ999, is projected to end sometime in 2026... The next generation of license plates will flip that structure on its head, moving to a “Numeral Numeral Numeral Alpha Alpha Alpha Numeral” format — such as 000AAA0.

Does anyone know why they care about this structure? Naively, there are 36^7 (minus edge cases) combinations available, which will always be sufficient.

When I click "Join the waitlist" on Firefox I see an empty beige box on an otherwise blank page.

What "very simple columnar format" did you switch to?

For the curious, from the link above:

> log, plank, stick, crafting table, wooden pickaxe, cobblestone, stone pickaxe, iron ore, furnace, iron ingot, iron pickaxe and diamond

Could you share an example of a workflow using the built in feature to run tests in Vim?

TL;DR, YAGNI

I had a former boss who strongly pushed my team to use the repository pattern for a microservice. The team wanted to try it out since it was new to us and, like the other commenters are saying, it worked but we never actually needed it. So it just sat there as another layer of abstraction, more code, more tests, and nothing benefited from it.

Anecdotally, the project was stopped after nine months because it took too long. The decision to use the repository pattern wasn't the straw that broke the camel's back, but I think using patterns that were more complicated than the usecase required was at the heart of it.