280 karma · joined November 7, 2019
I stand by what I said.
>I’m sure todays engineers do their best with the constraints they have.
There are two real constraints in the software engineering world: time and money (especially when we’re talking about an issue tracker, a wiki and a repo + CI\CD pipeline).
That Jira and confluences performance remains … not very good, suggests that the engineers are unwilling to, or unable to advocate for, spending the time and money to address this.
I said explicitly “path to monetisation” not “assume they’ll pay and stick around”.
I hope you’ll agree that it’s easier to find a subset of users that will pay when your superset of all users is large vs a super(?)set of zero.
I mean, for a single version bump (Google called it Angular 2.0) to render not only the code not migrate-able, but the entire paradigms on which the framework was based on is basically unheard of in an enterprise-targeting framework.
That’s an egg-on-face technical fail.
These two things are not even remotely the same thing.
Having users is a path to monetisation but having a high performant app no one uses is not.
In fact, if you have users despite performance, it suggests you have a home run product that can be optimised for performance.
Again, you can’t optimise your way to user growth.
Busted API deployment?
I’d also love to hear more about the concept.
So, you do do "bullshit" exercise. What a weird hill to die on.
Are you replying to the right comment? I made no such claim.
Describes exactly what I’m talking about.
Uh - what?
>A load balancer balances traffic between servers
Correct.
> of the same service or mononlith
Incorrect.
Load balancers used to work solely at Layer 4, in which case you’d be correct that any 80/443 traffic would be farmed across servers that would necessarily need to run the same code base.
But modern load balancers (NGINX et al) especially in a service mesh / Kubernetes context, balance load at endpoint level. A high traffic endpoint might have dozens of pods running on dozens of K8s hosts having traffic routes to them by their ingress controller. A low traffic endpoint’s pod might only be running on few or one (potentially different) hosts.
The load balancer internally makes these decisions.
I hope this clears up your misunderstanding.
Pointing out that Musk has had his greatest successes working at other peoples companies (with the exception of SpaceX, which I’ll grant you) doesn’t make anyone an “LARPing insecure hater”.
FTFY.
The rest of your comment neither refutes my point nor reinforces the earlier comment that Tesla was nothing but a name, brand and prototype: Chairmen oversee board meetings, not gnarly technical challenges on the production floors. No doubt once he became CEO (after the roadster was shipping) he became more involved in the day to day.
I proposed no such thing. If it’s important to know which client made a particular call, then it’s important to authenticate that client.
An old school CD-key can provide a one time shared secret to bootstrap a client install, or even a PBKDF if matched with a serial number to securely share the client secret.
Most implementations are concerned with AuthN and AuthZ for users and don’t require these extra controls for client security (i.e. you don’t care which client instance a user interacts with) I was responding to erroneous assertions that these controls couldn’t be implemented.
Is chess boring because there’s 20 opening moves? It’s all about the mid-late game.
The Tesla roadster was shipping to customers before Musk became CEO.
Don’t rewrite history… it’s beneath HN. Do better.
PayPal (not founded by Musk) Tesla (not founded by Musk) The Boring Company (only existed to de-rail a planned road development that annoyed Musk) SpaceX (I’ll give you this one)
GP asked how to approach a (presumably) from scratch implementation compliant with OAuth 2.0. I provided him with one.
Please don’t straw man my comments.
AMZN (amongst numerous other household name brands) ships world class products with 2-pizza teams where a dev, a designer and a product manager are having the conversations that need to be had to ship.
Do better.