mooted1

8 ms·

1.
by mooted1 6y ago
as someone that has complained about a lot of uber's resume driven development (see comments), I can attest that this system is a.) necessary, and saves the company millions b.) a simplification over the ... unusually ... architected s
2.
by mooted1 6y ago
This is the rare actually funny comment on hn.
3.
by mooted1 6y ago
> I'm going to assume you're a developer? No, but thanks for explaining my career to me and helping me empathize with toxic people.
4.
by mooted1 6y ago
bai
5.
by mooted1 6y ago
I appreciate so many of you are willing to crusade for free speech. But the reality is that platforming isn't free, and the process of deciding who gets platforms is political. The first amendment doesn't govern this process, nor
6.
by mooted1 6y ago
Oftentimes, these tools are developed for much more complex sites than the people who author these rants have ever maintained. Of course it doesn't solve meaningful problems for sites that can be maintained by a handful of developers a
7.
by mooted1 6y ago
Your suggestion for the problems with this project is "Why don't you just fork it and maintain your own?"
8.
by mooted1 6y ago
Get off your high horse. It doesn't matter what it was originally intended for if hospitals are over capacity, and opening up the ship will save hundreds, maybe thousands.
9.
by mooted1 7y ago
I think you make some good points here, and RLS is an ideal data security model in many respects. The parent's point is that tooling around this is weak, which undermines its value. Not being able to review and easily test authz change
10.
by mooted1 7y ago
Having a JWT or whatever authn is irrelevant. The problem is an insufficient authz model. Exposing databases through APIs is not the problem. Exposing relations without authorization is. Under these frameworks, you can add an innocuous
11.
by mooted1 7y ago
For the love of god, this is never how GraphQL was intended to be used. The official graphql website is very clear: https://graphql.org/learn/authorization/ > Delegate authorization logic to the business logic
12.
by mooted1 7y ago
Did you actually read the post? > The case for big tech today is still the economy of scale and not network effects (maybe facebook have those, but it exists only if the interface to facebook does not change). This is only true if you be
13.
by mooted1 7y ago
If you read more of Ben's writing, he talks extensively about how software companies dominate market share through network effects and vertical integration. You don't hear him talk about economies of scale because marginal costs a
14.
by mooted1 7y ago
Disappointed to see the usual onslaught of HN cynicism. "Product doesn't meet my narrow expectations; is bad product." 1. We use Slab. It's a fairly ok product in a crowded space. Needs maturity. Far better than confluen
15.
by mooted1 7y ago
I think it's tempting to attribute to structure what can be better explained by accident. You obviously have more context, but from my experience developing product, there are almost always ways to change direction incrementally and in
16.
by mooted1 7y ago
Have you ever worked in a polyglot ecosystem with rapidly evolving schemas? Tools like protobuf and thrift were designed to facilitate schema evolution since interfaces in these ecosystems evolve quickly and independently. Generics undermin
17.
by mooted1 7y ago
Security isn't black and white. SMS doesn't neutralize the value of 2FA since the effort required to compromise it are still considerable, such that the highest risk methods outlined by NIST require physical proximity to the phone
18.
by mooted1 7y ago
+1 that the code is, unfortunately, most likely worthless. My company has one chief competitor. If that competitor went out of business and offered me their source code, I'm unlikely to pay for it. Code tends to be highly coupled to th
19.
by mooted1 7y ago
What middleman do you want to cut out? My proposal doesn't add any dependencies. It's also not possible to prevent duplicate charges if a user POSTs a form twice without idempotency keys, so idempotency is necessary. I'm real
20.
by mooted1 7y ago
Also, I think the answers you're getting keep telling you to build distributed transactions because a.) they didn't read your post and are overindexing on "microservices" b.) this isn't an atomicity problem, it&#x27
21.
by mooted1 7y ago
That's not what the OP is asking--they're using external services like Stripe. Creating a Stripe charge isn't something you can roll back.
22.
by mooted1 7y ago
Having built similar applications in microservice environments, I think there are usually simpler answers than distributed transactions. And if you do need distributed transactions, this is often a sign that your service boundaries are too
23.
by mooted1 7y ago
This was under consideration at one time by the Seattle build team and was a recurring point of discussion during infra summits. Unclear if we actually broke ground.
24.
by mooted1 7y ago
I worked at Uber from 2014-2018. Can confirm this. It was a very poorly managed org because it was extremely grassroots driven—leadership was underempowered to say no to front line teams or hold groups accountable. The overlaps and poorly c
25.
by mooted1 9y ago
No. He wasn't. He was /a/ product manager. There are various other leads in the area, all of which had higher rank than this dude.
26.
by mooted1 10y ago
This kind of analysis nearly always fails to account for why these businesses aren't able to recoup expenses. While many startups are will never find a large enough market to be profitable, many others choose to invest earnings and t
27.
by mooted1 10y ago
I work at Uber. I was on the wifi yesterday. I was successfully using blind. If business insider would like video evidence, I'm happy to work with their reporters 1:1. There's a lot of problems at the company and it's been a
28.
by mooted1 10y ago
Most of the comments here are missing the point. The functionality and architecture of git aren't what's being criticized, but the way this functionality is presented. In fact, gitless if built on top of git's architecture. A
29.
by mooted1 10y ago
Sharding your application geographically is a quite a bit of complexity and requires a lot of work developing support infrastructure to manage load balancing, failover, and placement. One of the advantages of SOA is that different services
30.
by mooted1 10y ago
When I first started interviewing, I got turned down at a lot of companies because they were concerned about my self taught background, often in spite of strong project work and interviews. In spite of so many rejections (2 offers after 17+

More ›