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).
762 karma · joined October 4, 2020
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).
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.
When choosing one of several A/B test options, a hypothesis test is not needed to validate the choice.
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()
)Does anyone know why they care about this structure? Naively, there are 36^7 (minus edge cases) combinations available, which will always be sufficient.
> log, plank, stick, crafting table, wooden pickaxe, cobblestone, stone pickaxe, iron ore, furnace, iron ingot, iron pickaxe and diamond
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.
Could I get you started? Or could you point me to a place to get myself started? I primarily code in Python and I've found dependency injection, by which I mean giving a function all the inputs it needs to calculate via parameters, is a principle worth designing projects around.
- share your screen
- download/open the coding challenge
- you can use any website, Stack Overflow, whatever, to answer my questions as long as it's on the screenshare
My goal is to determine if the candidate can be technically productive, so I allow any programming language, IDE, autocompleter, etc, that they want. I would have no problem with them using GPT/Copilot in addition to all that, as long as it's clear how they're solving it.
> Have you ever used U after dd? Don't even try.
I never know about `U` before now!
random.seed(hash(user_id))
I think the bigger problem is handling the fact that not all users click through the same number of times.What's nice about AB testing is the decision can be made on point estimates, provided the two choices don't have different operational "costs". You don't need to know that A is better than B, you just need to pick one and the point estimate gives the best answer with the available data.
I don't know of a way to determine whether A is better than B with statistical significance without letting the experiment run, in practice, for way too long.
brew install coreutils
and whathaveyou.