dub

7 ms·

1.
by dub 3y ago
Typically the price of not having horizontal scaling is felt more by the engineers than the users, at first: - Data migrations, schema changes, backfills, backups & restores, etc., take so long that they can either cause or risk outages
2.
by dub 3y ago
As the article says, the vulnerability was fixed in April and the people who discovered it have already been rewarded under Google's Vulnerability Reward Program. Google also proactively detected the problem before being notified by th
3.
by dub 3y ago
The reasons Vitess didn't have foreign key support historically actually weren't a bold performance tradeoff or anything like that. It was more of a classic, boring, backlog prioritization thing: everyone heavily using Vitess was
4.
by dub 3y ago
When I worked at Google back in the day, we used to make dollar bets all the time. You'd tape the signed dollars you won to your monitor. A willingness to take pride in your work and to not take it too seriously when smart, well-intent
5.
by dub 3y ago
If you're not even willing to make a bet for a single signed dollar, that doesn't speak highly to your confidence in your work. It's fine to not be confident, but when professional security teams at large companies are afraid
6.
by dub 3y ago
> Obviously not true, in fact none of the companies I worked in that was the case I once offered a bet to the large security team at a well-known decacorn tech company I worked at: I offered to make a personal, reasonable-sized cash bet
7.
by dub 4y ago
> A surprising number of systems exhibit this behavior, sadly. I noticed [0, ∞] delivery semantics in a widely-used, internal/homegrown message delivery system at a big tech company once. The bug was easy to spot in the source code
8.
by dub 4y ago
JSON is the default serialization format that most JS developers use for most things, not because it's good but because it's simple (or at least seems simple until you start running into trouble) and it's readily available. L
9.
by dub 4y ago
While I haven't benchmarked JSON vs protobuf, I've observed that JSON.stringify() can be shockingly inefficient when you have something like a multi-megabyte binary object that's been serialized to a base64 and dropped with a
10.
by dub 4y ago
Open Office losing popularity and having a shortage of developers makes some sense to me given all the progress in web-based document editors. Something I have a harder time understanding is how it came to be that Apache Thrift and Facebook
11.
by dub 4y ago
> What kind of brave soul wants to trudge through and maintain log4j in their spare time for zero compensation? It's not clear to me as an outsider what exactly the Apache foundation is doing for these projects. It feels like Apache
12.
by dub 4y ago
I'd be more excited to use GPT to draft a summary of release notes by scanning all the new PRs in a release, summarizing what they are, and dividing them up into categories (bug fix, feature, breaking changes, etc.)
13.
by dub 4y ago
> Anything that isn't in the "happy path" of the AdsUI probably gets handled by some engineer making some API calls to a prod API Prior to going private, Twitter would have had recurring Sarbanes-Oxley audits. Auditors und
14.
by dub 4y ago
It's been half a year since terra/luna crashed but the name lives on at Nationals Park: https://www.mlb.com/nationals/tickets/premium/nightly/terra-...
15.
by dub 4y ago
With TSLA in the S&P 500 it's difficult to avoid being a shareholder
16.
by dub 4y ago
Class A players don't work for controlling managers who overload them with near impossible targets. Class A players have plenty of options in tech, and have no need to tolerate having their skills called into question or disrespected b
17.
by dub 4y ago
SF was never a late night city, but it's become even sleepier in recent years. Some examples: Orphan Andy's, Safeway on Market, and Pinecrest diner are no longer 24/7. Sparky's closed forever (a 24/7 diner). It&#x27
18.
by dub 4y ago
Figuring out how to reward simplicity, reliability, and maintainability feels like one of the most important unsolved social/human/economic issues in the software industry. Seems there's only incentive to simplify at small co
19.
by dub 4y ago
"It may be proved that no society can make a perpetual constitution, or even a perpetual law.... Every constitution then, & every law, naturally expires at the end of 19 years. If it be enforced longer, it is an act of force, &
20.
by dub 4y ago
Note that the product you linked to is larger, much more expensive (it requires a $20-per-month monthly subscription), and has much shorter battery life
21.
by dub 4y ago
I think what people really want is: - SaaS solution, not just open source (improvements to s3, for example) - A global hierarchy of files rather than an assortment of different buckets like s3 - Per-subdirectory permissions and chargeback s
22.
by dub 4y ago
There's nothing stopping developers from doing server-side validation before sending markup to clients. It seems like the majority of developers have never really wanted to make that cost-benefit tradeoff, though. I ran tons of website
23.
by dub 4y ago
The trouble with the term "technical debt" is that people tend to use it retroactively to describe messes which may not have been necessary or the result of an intentional technical choice. It's uncomfortable to say, "In
24.
by dub 4y ago
I don't particularly want to "mess with sandboxes", but I do want my builds to be relatively fast, correct, reproducible, extendable/customizable, with bonus points for being secure (meaning a compiler shouldn't be
25.
by dub 4y ago
make(1) has no native support for giving each build rule its own sandboxed view of the filesystem like bazel does. If I could have a wish to upgrade file transformation with make(1), I'd probably want a widely-available, standard, simp
26.
by dub 4y ago
Being familiar with npm doesn't save the time it loses you on its clunkiness. I see for myself and other engineers around me that we waste real time every week clearing our yarn caches, waiting for "yarn install", realizing w
27.
by dub 4y ago
Bazel can be clunky, but not having some bazel equivalent can have very significant costs that are easy to get accustomed to or overlook. Things like engineers losing time wondering why their node dependencies weren't correctly install
28.
by dub 4y ago
For those of us stuck on AWS it's sad not having BigQuery, but the thing that really gets me is not having Dataflow Most of industry still seems unaware that no-knobs data query and pipeline systems even exist. If I only had a dollar f
29.
by dub 4y ago
Hypothetically it should be possible to make an entirely new RDS cluster as a replica at a new version and fail over to it, with a similar error rate to a normal replica failover. Setting up the infrastructure to manually manage your own cl
30.
by dub 4y ago
A challenge for the crypto world is that the values of being decentralized and trustworthy seem a bit at odds with the value of rapidly evolving. If you compare the Amazon or Google of 1999 vs today, they're practically different busin

More ›