jcutrell

I have been here for a while, in the earliest days of the gig there was a mini-rush of startups to Chatt. Low cost of living, relatively small/quiet city, access to basically all major southern cities (barring southern Florida) by either a quick flight or couple hour drive… makes sense that it just works out nicely.

I live about 20mi out from town, in a relatively rural area, and we still get excellent 1Gbps here. They wired as many drops as I asked for when we built here. It’s like a dream for a remote worker.

The city still has presence from some startups (I’m a bit out of the loop on who all is here), and I’ve known quite a few remote engineers who have lived in the area as well. Not sure how much this differs from an alternate universe where Comcast rules the land.

EPB is excellent all around. Service is incredibly consistent, it’s a bill I happily pay every month.

I can understand that. I have to follow through with logic for why the worry won’t help.

“What is the upside for me if I continue to worry?”

I’d encourage comment OP to continue writing comments online, so that you can learn. The damage done in misinformation here is probably extremely limited.

If comment OP was trying to misinform on purpose, it’s a different story as there’s no opportunity for improvement there.

While the most prevalent narrative in threads like this sounds something like, "back in my day, we weren't so scared!", there's a few assumptions being made. The primary one: people are overestimating the risks associated with autonomy we had "back in the day" as kids.

It's also just as possible that we are adopting a lower tolerance for that risk, or that the risk is better clarified than it once was.

When I was growing up, I was allowed to roam the neighborhood. I lived on a military base in my youngest years, but later I lived in a suburb of a small town.

Nothing seriously bad ever happened to me, but that's anecdotal.

I wonder what is more likely: my parents were more risk tolerant, risk ignorant, or the world has become more dangerous. Both are possible, but I think the former two are broadly more likely than the latter.

Which ultimately means the game becomes a step more towards exclusive, for better or worse. Probably for worse.

Your inbox is worth much more than your money, if they can take both they will. They are already charging for additional storage, so I expect it will just continue on that path.

I substituted "Being a dad _can be and commonly is_ a long, emotional, draining, and lonely journey", perhaps unfairly. This could really just be seen as an expanded version of "being a dad is hard", which some people will identify with and others won't.

This is also something that could be spoken from the perspective of that person.

"Being a dad is a long, emotional, draining, and lonely journey _for me_."

As someone who experiences medical anxiety regularly, this reminds me of basically every dermatologist visit I’ve had.

The doctors who cut biopsies out of your skin don’t seem realize how much you’ll think about there words when you leave. “How long has that been there? That looks a little concerning. That seems strange.”

Doctors have to deal with patients of all kinds of mental fortitude of course, but it wouldn’t hurt to be clearer about procedures, concerns, etc.

For example, tell me “I bias towards taking a biopsy if I have even a little bit of doubt.”

I take some issue with the comparison as an either-or.

Automation in its correct place shouldn't replace human effort - it should augment that effort.

In this case, it seems one step removed to just do both of these approaches, starting with the first. During the process of finding those 100 high-confidence matches, you could identify the ones that have the most general cases, and reuse the email copy from those.

I think the idea that automation is intended to replace human effort wholesale is improper. We should rely on automation to handle where computers are better than humans, to give the human more time to do things humans are better at.

My theory is that this has to do with our difficulty dealing with delayed gratification.

Tell people a short number now = immediate praise, long term pain.

Tell people a higher estimate, immediate negative; finish in time = delayed gratification.

The most important thing I’ve learned about estimation is that, especially in larger/more established companies, it really only matters in two basic scenarios:

- Order of magnitude differences - hard deadlines (like a public event you are supporting)

Usually estimations between two things don’t matter as much as prioritizing those two things. Work on the thing that matters the most. If it takes 2 days or 5 days, in most cases it won’t matter - it’s still what you would work on, so functionally estimation wasn’t needed.

If it is a difference of 2 days vs 2 weeks (or some meaningful magnitude to you) then you start having opportunity cost that factors into prioritizing.

Estimation is more often used as a tool for “control and prediction” - how many times have you had incredible success because you controlled or predicted an outcome?

At a former job when I had some organizational influence, we started doing this and called them “team weeks.” My goal was to sell the week x team model to avoid constant streaming of tiny straggling tasks. (It was an agency.)

I think the model works, but didn’t totally match that agency. It’s a good theory though

Makes sense - the 172 is one of the most common training planes, getting a TON of low-altitude hours in the pattern.

Also because of the low altitude flights 172s will probably run rich.

Granted, they aren't burning a ton of fuel per hour - around 8g - but considering the sheer number of 172s out there this will make a reasonable dent in the total fleet of pistons.

Though I expect the infra changes to actually support this will take a very long time to actually put in place, and many people will opt for 100LL for a long time because it is all that's available at their local airport or it is cheaper.

I own a 182 that has the STC for auto-gas, and barely anyone sells auto-gas on-field. The only other option is to maintain my own tank, but that can't go on trips with me.

Still good news in the long run.

Okay, so we end Scrum… now what?

I understand the frustration. Even as a manager I can feel some disconnect. This series of assertions is this person’s observations.

It seems both one-sided and purely deconstructive. Even if it’s right, does ending scrum now actually produce fixes to this list of complaints?

Why not “fix scrum now” and a series of adjustments? This reads like a sophomore engineer that’s disgruntled more than a seasoned engineer trying to fix broken process.

Again, it’s easy to agree with a lot of it, but fixing it is harder than just stopping.

Congrats on the launch folks! Would you mind outlining why SAML specifically is hairy? How is it different from OAuth (for people who aren't doing a bunch of auth work on a daily basis, or haven't reached a scale where SAML is an issue yet)?

The problem is that most people don’t understand The chain reaction problem here.

Watching one calming video is unlikely to lead you to become addicted to calming videos. YouTube is optimized for the hook, and calming videos aren’t hooky.

The much more salient videos tend to be the sensational ones, and people who don’t have the understanding of that fact are much more easily hooked.

So while it can be a fountain of knowledge for one group of people, the insidious nature of the hooking algorithms still lurk beneath that surface.

I think this should be a side-story in a Wes Anderson film

Think of your experience and context as “ground floor.” You have a lot of it, which makes your starting point much higher than your colleague’s. Some things you are likely naturally taking for granted, he may have no context for. You can’t fake “taking for granted.”

Your goal should not be to help him do something that is hard. It should be to understand how to make it easy.

So, perhaps guide him towards the path of least resistance. He is likely not wanting to draw the wrong thing either; tell him to treat the first version as a draft and make him promise he will throw this one away.

Maybe draw something out for him and be willing to make mistakes in front of him, so he doesn’t feel self conscious about getting it perfect on the first shot.

Lower the stakes, focus on smaller problems, and find a shared vulnerability.

The amount of nuanced information available in this dataset is incredible.

Any plans to use these in tandem with X-Plane?

Looks really fantastic!

It’s gotten easier with Home Assistant but still, even as an engineer I prefer to use the easy APIs for these things sometimes than run my own support system for the Z-stuff

- Don’t write code until you need it. This results in less code, which is directly correlated with ease of change. - If you write lots of separated classes but then use them directly inside other classes, you’ve defeated the point. When you depend on something, pass it in instead of directly referencing, if possible. - keep methods less than 5 lines, classes less than 100 lines.

You're the right person to ask this I think - what is likely the attributable cause of death responsible for this? Mostly the overdoses, or other disease-related things?

There are studies that show not this level of extreme, but that there is what is called “wasted harm” - the harm done by 3 packs a day is not 3x the harm done by 1 pack a day, and 1 pack a day for 5 years is thus worse than 5 packs a day for 1 year.

Depends on the goal.

If the risk factor is homogenized, then the variable researched can be isolated theoretically.

However, this doesn’t allow you to test for interaction between those variables.

In the study for example, they identify an apparent interaction between ethnicity and the chemicals mentioned; we don’t know what the effect size would be (whether additive, multiplicative, or something else entirely).

(This is without any domain knowledge of the mechanisms of breast cancer to be fair.)

For most (not Peek), memory and knowledge are necessarily linked since memory tends to work better when there is a previously existing connection to attach a new piece of information to.

So, we don't tend to remember facts for the sake of facts. This obviously isn't always true, but for vast amounts of information, it would be very difficult to remember single "nodes" of information without having some connection to other information.

Memory contestants use this to their advantage, by creating some sense of story and/or place to attach the otherwise arbitrary information, like digits or cards, to.

I get the frustration, I really do.

But I think part of the issue here is the idea that time is fungible like money. That saving time by looking at Trello cards instead of meeting face to face is somehow more effective.

It might be. It might not be. But simply saving a few minutes of time doesn’t necessarily equate to “more productive.”

This kind of optimization of behavior assumes everyone will consume information uniformly.

Ever sent up a smoke signal for help on a blocker in slack, only for the comment to be lost in a bunch of messages and you stay blocked?

Again, in a perfect world, we could just record everything and do it all asynchronously. Wonderful ideal.

But the stand up, in my experience, accomplished more than just cold task management.

It gives a point for each person to consider what they’ve done, compose it, and to raise in a higher resolution environment the blockers they have.

It’s silly to think that we can replace every interaction with an async version of the same interaction, at least on my team.

At the same time, I don’t recommend dogma in either direction. Don’t find value in the standup? Do something different.

Deterrent is, I think traditionally at least, considered “negative reinforcement.” So, “I don’t want to end up like that person, so I won’t do what they did to end up in their situation.”

I can imagine some companies wanting that data to be accessed in a specific delivery format (i.e. with branding experience attached).

Also might be concerned about inaccuracies from variable pricing models for example. There’s a few reasons why you may not want it accessible - hence one of the reasons why CORS is even a thing.

I do the envelope method with EveryDollar.

I like the simplicity of everydollar, but I want some of the features you’ve built (like average for a category - so obvious and simple, but SO useful!)

How does this tool work in contrast to an envelope system?