beardedetim

ah, the good-ol 'Every other release is the good one' MSFT that we came to know and love!

Maybe there's two sets of ads being discussed here: exposure/top of tunnel and conversion/bottom of funnnel?

Exactly the right term to use: Expected Value. If we have 1/6 chance of winning and each win gives us 6x, we have an EV of 0.

Poker is a great game to learn to understand EV/variance.

Microblogs are _the thing_ just have always been "too early". Not sure _how_ this will work but I strongly believe that microblogs are the _end goal_ here.

On my wife's iPhone, they have groups that allow _certain people_ to contact them with _everything else_ being disabled. I would assume there's similar settings across devices.

Not OP but I do both. I pay for a fastmail account and have <myname>@<one of their domains> which all my _personal_ things go to and then I have my business emails all route via their Aliases and certificate pointing.

There have been some instances where both the fastmail domain and my business domain ended up in Spam for the receiver but that is less than a handful of times and I used Fastmail via Nodemailer as a proof of concept for a newsletter service so (ab)used the service without any issue.

Have been rocking Elementary for a few years now as my main Linux desktop. It has some quirks here and there but most of them are probably User Error to be honest. It's basically Ubuntu++

> making sound decisions ... Is a skill

I agree! It sucks that most jobs don't care about paying for that skill though.

> If you only make enough enough predictions then some of those will turn out predict the future correctly.

If we have a coin and we say "It's 50% chance it lands heads" and it lands tails, were we wrong?

If we have a 20-sided die and we say "It has a 5% chance of landing on 20" and it lands on 20, were we wrong?

GrubHub?

As an Interviewer:

I think it's helpful, in order for me to understand the person I'm interviewing, to pair program on a problem together. I don't think it makes sense for them to LeetCode an algorithm in front of me; I think it makes sense for us to build a working API or an Async Worker. I need to know that you _know_ these things or at least know that _you can figure these things out_ and know how to _ask questions when you are stuck_.

As an Interviewee:

I won't do take-homes. I barely like having to do 1hr long interviews, there's no way I'm going to take 1hr+ of my time _outside of work and interviewing_ to do your toy problem _and then talk to you about it_. I would love to hang out, sling code together, and spend time nerding out for 1hr with people as an interview. In fact, I know that if the interview is a "let's code together" one that I'm pretty likely to get the job so I look forward to those types of interviews.

There are pressures, making it a choice of the actor. That actor will have consequences regardless of what choice they make. I disagree that 'i needed money' is a valid excuse to do things you morally disagree with. I also disagree that 'i needed money' is an excuse for others to do things that they believe is immoral.

Personally I don't like crypto so maybe that's where my opinion is coming from. But it sure feels like everywhere in life we are presented with a choice to do what is right and what is easy. Both have consequences.

> If while reading a document, you find a mistake, instead of changing it, the normal reflex is to create a Jira ticket?

I would say the first reaction is to create the PR to make the fix. Then, while CI is running, I create the JIRA ticket and update the PR description to point. Best of both worlds!

Ethically dubious, sure. But legally?

Are you counting Chef/Ansible/Puppet/etc as things that came during the cloud era or that those things were not used to solve the problems you raised before the cloud era?

> giving each kid a therapist is not feasible.

Why not? We expect a healthy child to have a doctor, a healthy child to have a friend group. Why not expect them to have a mental doctor/therapist?

> The struggle is between creating simple solutions vs over-engineering for future proofing. I'm pretty sure I'm biased towards simple solutions.

I want to encourage you to keep learning about your own biases here but to continue to have that bias as much as possible.

I like the term "throw away code" here but I think another way to say it would be that most of the code I write is like a jig for woodworking. I don't need it at the end of the day, it looks like shit, and holds up the real Things while I figure out how those things actually work.

Sometimes in code though, I find, that the jig _is good enough for now_ and it's super easy to replace the three that break instead of all 20 I needed to build it.

I think it is but it's worth asking ourselves: is a global fold system worth the trouble we have to go through?

I once heard that you're the average of the 5 people you spend the most time around and the older I get the more true that rings. I try to be _really_ particular with the communities I join and I have _no qualm_ removing either people from my communities or myself from theirs if I don't feel like we're helping each other; or more specifically if _I don't feel_ that _I am growing_ in the way _I want to grow_.

We should be kind to each other, for sure, regardless of what _Group_ we're in. Everyone should have equal access to their needs and desires. But. I am not _obligated to allow you to influence me_.

> Help me understand why Wall Street greed would prefer trains that derail to ones that don’t?

I don't know if it is true that they _prefer_ trains that derail vs ones that do not. I can try to understand their _incentives_ though.

I would assume that they are incentivized to make money _this quarter_ or _this year_. I would also assume that they aren't really _caring_ about consequences that are not _fiscal_.

Given these two incentives, if someone asked me "Should we ship this train that might derail?" I wouldn't say "no". I would ask "what are the fiscal consequences if it does?" and "How much does it cost to not?"

Famous Fight Club quote about recalls and such. Same thing with companies breaking the rules in exchange for some sort of fine. It's not that they _want to break the rules_ it's that it's they are _incentivized_ to make the choice that _increases their odds of fiscal growth_.

> But using a database to find a recipe has never been interesting to me, personally.

I've built a few toy apps like everyone else and found the same feeling when it was just a CRUD listing app of recipes that I could search. What I found was an interesting take and one I'm wanting to take further is I want not recommendations on recipes but _almost_ generation of recipes. So when I search "Chile Colorado" it returns a specific recipe that I created but for each "step" it "links" to relations/more info/etc.

Example:

Ingredients:

- 1lb beef <this is the recipe itself either from a source or you put it in>

  - Ribeye is best <this is from the recipe itself and notes you made on this specific ingredient>

  - Sometimes substituting chicken is healthier <linked from some other recipe about beef that you saved once>

  - This doesn't double like most things do if you are making more portions <linked from some private notes you made about cooking>

- ....

Do you think that caries the context enough? Or do you think that you would just much rather have a list of vetted + manually entered ones?

In USA this isn't true. We bought a house using an FHA loan and put down less than 5% and our interest rate was lower than 3% if I remember correctly. Maybe not as reasonable as you are imagining but it was really low in our mind.

Ah, the goat farmer fantasy that always seems to come _at the cusp_ of the solution.

Yup yup yup! Good shouts all around. Already reaching out to people directly!

Usually the difference is the "mailbox" an actor has, making the difference more about the level you're calling an actor more than the differences in any code you might write.

This has been my experience as well along both sides of the axis. If you're not "Lets Go Brandon" or whatever the equivalent is on the left, you usually are reasonable and have valid opinions.

Even more so, we usually share the same ideals just have different ways of getting there. There isn't huge division out there. Just two camps of dicks with most of us in the middle.

My experience matches yours and I've always thought it was due to trust. Leadership doesn't trust their team and have no idea if they're being productive or not. So they use "at desk not talking with head down" as a proxy.

.catch() returns a promise so you can call the then method on it again, yes. If you throw from either catch or then it will trigger the next catch method.

I've never thought of a PR as causing conflict. For sure, you're right now that you've explained it, but as an engineer I've never felt that way.

But I'm okay with the conflict! There should be conflict at work! Ideas should be freely expressed and those ideas are going to meet contrary ones!

What wouldn't be healthy is a place where that conflict isn't resolved or doesn't lead to a better idea winning. Or where only the Lead "wins" because of their position.

There shouldn't be arguments, no one should yell or be hurt. For sure that's a bad place to work. But conflict about where to place a piece of code? Sure! Conflict about if we name it Foo or Bar? Why not?! That conflict is like the sharpening of Iron! It hurts _today_ but can strengthen and make _you_ better let alone the organization as a whole.

> so I know who to avoid

This is a good point! I think that the concept of "who do I want to associate with" is a different way to view things than "everyone I see in the world needs to treat me with agency"

I have a hard time knowing where that line is. Like you said,

> I AM a free speech absolutist (or close to it), even if it does result in some discrimination. (Even against me.)

People out there, due to their agency, may not agree with where my agency ends and theirs begins. I think if we have the privilege and feel able to "choose to avoid" those that we disagree with, we could have these discussions in the open without fear and actively change people's minds.

I don't know how to though. I've written about it here [1] but I still don't have a good answer for how do we draw that line of where your agency ends and mine/theirs begin.

[1] https://timonapath.com/articles/body-politic