fierro

lol this is a great point. Go's attitude is tribal towards these things -- "if you can't see why this is a good thing, the language is not for you". I say this as a huge Go fan and daily practitioner.

cue amateur historian pontification

I understand this perspective, but I take a different view on life. I don't worry about spending money. I have high leverage skills, so I focus on making more money. Life is more enjoyable to me when I can spend without care knowing I'm always increasing my skills, fulfillment, and by consequence earning potential.

Eh. There's nothing wrong with using tool or a stack you're familiar with and know you can execute well on. It may not be optimal, but it's certainly not always bad to reduce uncertainty.

glances at screen LGTM

thank you lol. Hello World engineers will never stop criticizing K8s.

no, because the bigger win isn't ingoring whitespacing. It's ignore refactoring changes like renaming functions

this is very, very safe to assume. There is probably a hundred engineer's worth of "secret sauce" for an entire managed DB product line.

lol at all the people saying "I've never copy and pasted from Stack Overflow!!!"

I mean sometimes you need the exact code described in a SO post, even if it's one line. So you either look at the screen and manually retype it, or copy and paste.

Reading this makes me think of the quite "If you're so smart, then why are you unhappy?"

well put. AGM's writing style is fucking cringe.

you're conflating "pushing for further tests" with "pushing for further treatment.' IMO, everyone should be entitled to as much data accumulation as they want. Insurance companies can set reasonable thresholds, but if I want to pay out of pocket to get bloodwork done, that should be easy to get.

Whether or not a doctor prescribes/advises a certain treatment is still firmly in their domain. The amount of biomarkers/biological evidence a patient has shouldn't sway a doctor's decision to alter a treatment plan. As a reasonably smart non-medical professional, I would rather have more data than less data, and it's paternalistic and a little condescending to say "no, you shouldn't actually take diagnostic tests because 'having that information might freak you out'"

this is a paternalistic point of view. People should be entitled to accumulate data about their own body -- any "negative" ramifications of this are personal problems.

VIM!

learning Vim well

which city?

probably not net positive if you factor in the energy required to load the ore onto the train at the top.

can you explain the `git pull origin master` thing one more time here?

How will the otters handle cross region communication?

this is the real reason I use Notion. Keeps that Dock looking nice and minty.

I'm not understanding the importance of distinguishing glue code from non glue code. It's still work that needs to be done whether it's "first class" or not. That difference boils down to who writes it, not the fact that it is present in the code base (as measured by LOC, which the author measures and attributes the cause of high LOC to glue code)

I read this article but am having a hard time understanding the point in concrete terms. What does it mean to make invisible glue code first class? How would reduce the #LOC, which is something the author mentioned many times?

yeah what I'm saying is that you can only pause as fast as your slowest currently initiated query. So if you have a diverse set of query patterns, you could be waiting for a really small percentage of small queries to wrap up.

nah not to the full machine. This is just a Slack token. Someone basically had the employee click on something with XSS or some other way to steal cookies (idk there's a bunch of ways you can steal cookies out of someone's browser)

sounds like it's a simple software token. Hackers needed an account for this, which they got by paying 10$ for stolen cookies lol. So now they can log into some random employees account, then get an admin issued 2FA code. Never seen these "bypass" codes before, but that's my best guess.

this is interesting. So you have a weakest link kind of problem here.

guessing it's somehow BGP related. can't wait to find out

excellent summary of the problem.

you could be behind NAT or reverse proxies or any number of virtual or physical network components. This service helps account for all of that.