fierro

11 ms·

91.
by fierro 5y ago
these are valid questions to ask but I'd be wary of falling into this very common trap that I see on HN, which is dismissing the sophistication of a product based on, well, nothing really. Given that another company was willing to p
92.
by fierro 5y ago
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.
93.
by fierro 5y ago
cue amateur historian pontification
94.
by fierro 5y ago
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
95.
by fierro 5y ago
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.
96.
by fierro 5y ago
glances at screen LGTM
97.
by fierro 5y ago
thank you lol. Hello World engineers will never stop criticizing K8s.
98.
by fierro 5y ago
no, because the bigger win isn't ingoring whitespacing. It's ignore refactoring changes like renaming functions
99.
by fierro 5y ago
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.
100.
by fierro 5y ago
lol at all the people saying "I've never copy and pasted from Stack Overflow!!!"
101.
by fierro 5y ago
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.
102.
by fierro 5y ago
Reading this makes me think of the quite "If you're so smart, then why are you unhappy?"
103.
by fierro 5y ago
well put. AGM's writing style is fucking cringe.
104.
by fierro 5y ago
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, bu
105.
by fierro 5y ago
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.
106.
by fierro 5y ago
VIM!
107.
by fierro 5y ago
learning Vim well
108.
by fierro 5y ago
which city?
109.
by fierro 5y ago
probably not net positive if you factor in the energy required to load the ore onto the train at the top.
110.
by fierro 5y ago
can you explain the `git pull origin master` thing one more time here?
111.
by fierro 5y ago
How will the otters handle cross region communication?
112.
by fierro 5y ago
this is the real reason I use Notion. Keeps that Dock looking nice and minty.
113.
by fierro 5y ago
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 fa
114.
by fierro 5y ago
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?
115.
by fierro 5y ago
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.
116.
by fierro 5y ago
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 brows
117.
by fierro 5y ago
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
118.
by fierro 5y ago
this is interesting. So you have a weakest link kind of problem here.
119.
by fierro 5y ago
guessing it's somehow BGP related. can't wait to find out
120.
by fierro 5y ago
excellent summary of the problem.

More ›