jroseattle

5 ms·

1.
by jroseattle 21d ago
Watching the demo video, they haven't created open executives. They've created open managers. It looks like most of the work of the package is reactive -- monitoring external things and responding. It's not proactive just bec
2.
by jroseattle 23d ago
True, things in the west tend to cost more than elsewhere (I'm in Seattle WA.) My mother-in-law lives in rural Missouri and had her 6x10 bathroom remodeled in 2025. Full gut replacement of everything. Total cost: $5600. I got a quote f
3.
by jroseattle 28d ago
Heartily agree with the metrics for analysis, but this seems anchored around a focus on introduction of "something else" without regard firstly to correctness. > The server is not the most important thing, and each new kind of
4.
by jroseattle 28d ago
> Events, queues and persistent logs are getting more and more important in today’s software systems. Systems like Kafka, RabbitMQ, SQS and others provide that functionality. But maintaining them is annoying, custom and you need the skil
5.
by jroseattle 1mo ago
> VG didn't do a great job there but the idea of doing it remotely being evil or whatever was ridiculous I don't think the issue was the communications medium (Zoom.) > I don't think much about my time at Better but it
6.
by jroseattle 2y ago
This is exactly how we arrived at our solution. We needed to satisfy the constraint; locking was one means of addressing the constraint. Maybe we were lucky in our implementation, but a key factor for our decision was understanding how to m
7.
by jroseattle 2y ago
> up to 50000 atomic, short-lived transactions per second 50000? > You need distributed locking if the transactions can take seconds or hours, and the machines involved can fail while they hold the lock. From my experience, locks are
8.
by jroseattle 2y ago
We reviewed Redis back in 2018 as a potential solution for our use case. In the end, we opted for a less sexy solution (not Redis) that never failed us, no joke. Our use case: handing out a ticket (something with an identifier) from a finit
9.
by jroseattle 2y ago
Congrats on writing and completing a book! I was involved in a few myself long ago, when I had the time available to contribute to those endeavors. In a world that often measures "the juice being worth the squeeze", I'm not s
10.
by jroseattle 2y ago
> The vulnerability was addressed with the release of Docker Engine v18.09.1, but it was not included in subsequent major versions, causing a regression. Without further information, this sounds like code introduced in a hotfix that wasn
11.
by jroseattle 2y ago
> Resume fraud is rampant. So is interview fraud. The remote-interviewee-answers-questions-while-her-face-reflects-windows-popping-up-on-her-screen is tiring at this point. So, I decided to find a way to inform me if someone was being fe
12.
by jroseattle 2y ago
What I find more important than the timestamp format -- the timestamp source. Centralize from where the ts is set (the db is a great place to do this.) Don't let client-code set the timestamp.
13.
by jroseattle 2y ago
You learned some great lessons there, but I would challenge one item early in the "script": > 2. Verify if it’s a problem from search volume. It contextually depends, but correlating a problem-to-be-solved with search analytics
14.
by jroseattle 2y ago
I really like your on-device storage approach. I did something similar with an app for my smartwatch a few years ago to prompt/track my gym workouts. At the time and on the particular platform, other apps felt very spammy/scammy,
15.
by jroseattle 2y ago
Way back in the day, I picked up a cheap ($5!!!) copy of Readings in Database Systems from Michael Stonebraker. I found it fascinating to read the original papers that proposed concepts, and then to see those concepts implemented and become
16.
by jroseattle 2y ago
This is generally good advice with depth, but I would add a disclaimer: organizational practices and idioms should be taken into account. A few examples where these points would need some adjustment in my org: We're not crazy about irr
17.
by jroseattle 2y ago
As April Fools jokes go, this is really well done. On one hand, this could easily be read as the musings of some overzealous, re-awakened and re-charged techbro/middle-manager who has tried and failed a few times. But this time, things
18.
by jroseattle 3y ago
Yes, we had some "stakeholder training" that was necessary. The biggest complaint: "I don't understand why this takes so long." Our stakeholders were mostly plant operations people -- users, not engineers. We re-fra
19.
by jroseattle 3y ago
I recently inherited a project that was "late". The team and project were 6 months into execution, and had nothing to show for it. The status on my Day 1 was "estimates were missed -- now what?" On appearances, everythin
20.
by jroseattle 3y ago
I make my own pasta when the sauce warrants it. In my experience, homemade noodles will absorb sauce much better than the store-bought version. And, with a good sauce, the result is just _so much better_. You won't find me making my ow
21.
by jroseattle 3y ago
I'm not sure if this was intended to "flip the script" on the talented & smart, as this is sage advice for any entrepreneur. It wouldn't surprise me if the author was trying to give the "T&S" permission
22.
by jroseattle 3y ago
> let’s just consider it an expensive learning opportunity to redesign the system so it can’t happen again. Also, Zuck: but hey everyone, keep on moving fast and breaking things!
23.
by jroseattle 3y ago
Well-executed RCAs are just so satisfying to me. Blameless culture is absolutely critical to getting to the "right answers". Across the teams in my company, I hit nirvana when reviewing something like a major/impactful outage
24.
by jroseattle 3y ago
This book is still on my shelf. When I first ordered and received it, I sat down and read it cover to cover. One of the things I really enjoyed was seeing how differently all of the interviewees worked and went about their business. They di
25.
by jroseattle 3y ago
I was thinking you were asking questions and/or engaging to understand, of which I've made an incorrect assumption.
26.
by jroseattle 3y ago
Allow me to clarify a few things: - Format: we don't dictate format on docs. In terms of sharing important information, it's irrelevant. Dealer's choice. - Audience: we are writing documents that are internal to our team, but
27.
by jroseattle 3y ago
I'm a documentation zealot. My eng teams understand we treat docs as products; they are project deliverables, and we allocate time to ensure we produce and maintain concise, clear and unambiguous content about the services we operate.
28.
by jroseattle 3y ago
I used to run a fairly good-sized light show, until it became too much work (job change, kids/family, etc.) xlights powered my shows and taught me a lot about the protocols and hardware and everything else that comes with it. It's
29.
by jroseattle 3y ago
It's been 20+ years but I loved this shirt for it's SQL agnostic-ity: https://www.pinterest.com/pin/lol-code-geek-select-from-user... (This shows the shirt you could buy once-upon-a-time from thinkgeek, which
30.
by jroseattle 3y ago
That's right. It's all part of the back-and-forth of good faith.

More ›