ericdykstra

AI didn't X, it Y. Where Y is write this post.

The Artisan of Glimmith is so good! Biggest surprise of the year for me so far.

I got 12/18 on faces as an American-born Caucasian living in Japan for over 10 years. Since the subjects were photographed in New York City (and from the other comments, at least a decade ago), cues from fashion and makeup only helped me get about 4 of them, another 6 had pretty strong ethnic features. Of the remaining 8, it was a bit of a tossup and I did worse than guessing, getting only 2 correct.

13/18 on food. Even with a lot of the same general types of food, the presentation and specific ingredients made a lot of them somewhat simple. I got tripped up on a few, though, where I overthought it ("a Japanese X is usually not like this") or ones where it was really a tossup for me between Chinese and Korean since I'm less familiar with those foods.

I won't ever put my name on something written by an LLM, and I will blacklist any site or person I see doing it. If I want to read LLM output I can prompt it myself, subjecting me to it and passing it off as your own is disrespectful.

As the author says, there will certainly be a number of people who decide to play with LLM games or whatever, and content farms will get even more generic while having less writing errors, but I don't think that the age of communicating thought, person to person, through text is "over".

I studied poker a lot in high school, and it still influences how I think today.

Probabilistic thinking about the EV of your decisions is a good framework, but "Just keep making good decisions" is the hard part. Same as in poker, though, the hard part about making a decision in life isn't the middle-school level probability math, but about making the right estimates about payoff potential and success rate based on incomplete information.

Analyzing things as they are rather than how you wish they were, being able to separate useful information from noise, and taking a step back to look at second-order effects are all useful skills that will help you make better decisions the more you develop them.

There is a bit too much emphasis on the relationship between the manager and individual subordinates as the only thing a manager does. It's certainly the relationship that programmers have with their manager, but it ignores the reason why managers exist at all. In the end, managers are part of the translation layer between the company's top-level goal of acquiring customers and improving profitability and code that gets written and deployed.

The day-to-day responsibilities of a manager vary by company, but in essence can be boiled down to: Take priorities that are handed down from above -> apply those priorities as efficiently as possible to the team -> assist in execution.

The manager might be part of the discussion of priorities and clarify them before relaying them to their team, they may actually have quite a bit of freedom of interpreting the priorities, or they may literally just be a task-assigner-and-enforcer. The manager might also have technical leadership authority, architecture responsibility, or anything else, but these are still all in service of coordinating a team to produce the best output possible.

How a manager relates to their subordinates is important, of course, and the best managers treat their subordinates as individuals that have different needs. There's a responsibility to give them room to grow, keep them happy, and keep them productive as part of the job, but that alone isn't the job.

I've seen it work in a few ways; these are not mutually exclusive:

* You have someone whose job or as part of their job is to it is to discover these kinds of internal organizational efficiencies and automate them. Something that organically comes up like this gets assigned to that person.

* Managers are not incentivized to stick to a rigid schedule or metrics based on an inflexible roadmap.

* Flexibility and autonomy is built into developers' schedules so they can work on things outside of just their rank-ordered task list.

RTS has always been my preferred competitive genre. Yes, basic build orders are pretty well mapped out. In Starcraft 2, for example, the first 1:30 or so for beginners, the first 3-4 minutes for intermediate players, and the first 8-9 minutes for pros have "standard" build orders.

But once you get past this, there's so many things to worry about - balancing tech versus units versus upgrades versus economy, micro, scouting, unit composition, harassing and defending harass... And then the meta layer, which is allocating your limited time and APM to those decisions and actions! Really challenging and rewarding to improve at, and the only "e-sport" I find interesting to watch.

This article, like Duke's book, has a solid premise, but fails to provide any actionable advice aside from a simple risk/reward framework. When I read the book, I was hoping there would be more information about how to properly handicap various situations, but there just wasn't.

Business and life decisions aren't as simple as calculating pot odds and outs. Anyone who has estimated a complex and unfamiliar programming task knows that the unknown-unknowns are the biggest part of any equation.

There's a kind of vicious cycle here where people feel disconnected from their surroundings and communities, and attention-stealing apps make a business of providing a surrogate through parasocial relationships and infinite access to the spectacle and new ways to interact with it.

Parasocial relationships aren't real relationships, and the spectacle replaces doing anything directly, there is no fulfilment and the cycle continues. There's an epidemic of people who can't have hold a conversation or relate to anyone without mediating the conversation through a common topic that they've experienced on mass or social media. They're addicted to watching a simulation of having a life, and not actually living the one life they have.

I like the feature of being able to select what equipment you have available. Lots of us lost access to a gym with COVID and don't have the ability to put a power rack in our abode. A simple concept, but great execution!

PS: Do you know where I can download more RAM for my computer? It's been a bit laggy recently.

Many companies implemented work-from-home policies very quickly, almost all public events (sports, standardized tests) were canceled, schools and sports gyms closed, and some companies that didn't go to remote work had employees stagger commute times so trains would be less crowded. This all started, iirc, while the number of cases was still in the tens (not counting the cruise ship).

It is also more accepted to wear face masks, as many people have pollen allergies so it's quite normal, and there is less direct physical contact between people overall.

I remember reading that the number of flu cases was about half that of a normal flu season because of the precautions everyone was taking, which points to a high percentage of people doing their part to help prevent the spread.