Balladeer

How does "R language" compare to searching for one of the popular R packages? Searching for "tidyverse", "dplyr", or "ggplot" seems to get a good chunk of hits. That being said, yeah, there does seem to be a trio of skills that often go together (R, python, SQL)

How long did it take you to go from "making a new server / copying configs is fine" to "this is tedious enough I'd like to abstract it?"

Like, was it a years-long journey or is this the type of thing that becomes immediately obvious once you start working w/ N servers or something?

I'm trying to learn the space between "physical machines in my apartment" and "cloud-native everything" and that's led me to the point where I'm happily using cloud-init to configure servers and running fun little docker compose systems on them.

Hah! Thanks for the correction / info; I do appreciate it.

> Markets prevent monopolies and cartels.

A lot of the optimism seems to rely on this statement and...I'm not convinced? But I also admit I'm not well informed on the topic. Does anyone have suggested reading on 'market discipline', as they're calling it?

I mean, the first person on their "Patron Saints of Techno-Optimism" is Jeff Bezos, who is actively dealing with an antitrust lawsuit from the FTC regarding Amazon's frequent and regular push toward monopoly power.

I understand and even expect the lack of empathy from RTO executives, but the lack of empathy on the part of the 'remote work for everyone, always' camp saddens me.

I've worked primarily remote since 2016; but I have the option of going to an office a few miles away when I want to. My wife, forced to work from home, finds the entire experience to be socially isolating and misery inducing.

> work from our own comfy homes instead of rolling into a crowded, stuffy office everyday?

This one-sidedness is a strawman. Not everyone's home is comfy or has space for working; some people made housing decisions based on one person leaving the home for most of every day (e.g. choosing a smaller apartment closer to city). Not every office is crowded and stuffy; some are quite pleasant. Not every worker gets their social needs met outside of work, and forcing them home ends up isolating them from the primary source of social interaction in their world, with all of the mental health and well-being issues that entails.

Personally, think that "more remote work" is the way to go, but the issue is more nuanced than "why are people resisting this obviously beneficial change?"

> some will learn, but most will fall for the cloud marketing depts and become infra renters for life

Do you have any learning recommendations for someone looking to start down this path? I've only ever worked in an infra-renter context, and I've begun exploring the 'rent from Hetzner, manage your own infra' for personal projects, but I would love to learn from the paths of experts where possible.

This "article" is a 10+ year-old website that's been tracking an ecosystem-wide migration from one style of preparing python code for distribution to another, more robust style of preparation.

I'm cautiously optimistic here. I have a very specific idea that the Vision Pro might make real. There's a great urban park nearby and I so want to just...walk while I work. Not on a treadmill and not 'to get away from my work'. Just: walk on a safe road / trail and do my computer work at the same time.

I've been exploring the consumer AR space --- I have a Viture One and have been eyeing the Xreal Air, but neither seems to solve the problem of "keep the virtual screen stable while I walk through real space".

If the Vision Pro can do that for several hours at a time, my interest in getting one will skyrocket.

(The whole 'how do you type while walking' issue is a separate problem, but one I feel is far more solvable than the virtual screen stability issue).

For typical use cases, you're probably persisting the data, so I'll assume your use case is "Python with a database ORM like Django or SQLAlchemy".

The really short version of "use statemachine" is: store a single, explicit state for every 'thing' and create a log row every time that state changes.

- Make a python model / database table to represent "the things whose state can change" (like an Order or a Task).

- Give each a unique id and a 'state' column that is either a text field or an enumerated type (or a foreign key to a 'valid_states' table if you want to get fancy). Do this _instead_ of adding boolean columns like 'is_completed' or 'is_deleted'.

- Create a log table with the same columns as your Order table -- whenever you update an Order's state (or create a new one), add a new row to the log table with the new state and a timestamp. Now your 'Order' table shows the current state of every Order, while your log table shows every state that every Order has ever been in, which will come in _super_ handy for analytics later.

Everything else can be built on top of the above:

- defining valid states and their transitions (aka formalizing the state machine)

- preventing 'invalid' transitions if you want

- creating analytics tables to show the 'typical' flow of an Order (e.g. columns like 'creation_date', 'payment_date', 'ship_date', 'return_date')

- triggering other systems when Orders enter or leave a given state - etc

This "suddenly requirements change" is why I get instantly wary whenever I see a boolean column like `completed` in a design.

Sure, you start with two explicit states. But then you add `deleted` and now you have four states, whether you know it or not. Then there's talk of adding a third boolean column, and folks are wondering what it _means_ to be "deleted" but not "completed" and whether that is a valid state, and pretty soon the team is reinventing the concept of a state machine without any of the vocabulary that makes it straightforward.

Yeah, having a nuanced vocabulary to talk about misophonia really helped me. Even just in the context of English, the vocabulary just wasn't there back in the early 2010s when I first sought out treatment; basically all you could find as a lay-person was articles like "What is this 'misophonia' thing? Is it even real?".

Thankfully, the field has developed in the last decade, but I can only imagine that if people find themselves struggling to conduct day-to-day interactions due to language differences, then trying to talk about something as nuanced as misophonia responses would be unreasonably difficult, if not impossible.