morgante

10 ms·

61.
by morgante 2y ago
Line by line is infeasible, which is precisely why you need to use AI to make larger semantic inferences. You also don't have to one-shot translate everything. One of the valuable things about the Rust compiler is it gives lots of spec
62.
by morgante 2y ago
> Nat Friedman and Daniel Gross own a cluster of GPUs that they rent back to their startups for below market rates. Not just their startups btw.
63.
by morgante 2y ago
Certifications and compliance regimes are what got us into this mess in the first place.
64.
by morgante 2y ago
> ask to see their certificate and (if you're being particularly diligent) contact the school to verify it. Certificates are ~useless in tech. I've encountered way too many candidates who have a bunch of certificates but don&#x
65.
by morgante 2y ago
His resume leaves 0 doubts on why nobody wants to hire him.
66.
by morgante 2y ago
> 4-5 hours is pretty excessive for an interview process actually. That's preposterous. You're going to spend hundreds of hours working together. 4-5 hours is extremely reasonable to make sure it's a good mutual fit. Of co
67.
by morgante 2y ago
Still, L10 is patently ridiculous. He is not L10.
68.
by morgante 2y ago
Not even that makes sense because a "tractor company or heavy manufacturing company just churning out results for years" (that supposedly pays $10k/day) doesn't have exponential stock growth. The entire article is just t
69.
by morgante 2y ago
L5 is correct, but you should be looking at total comp (not just base). L5 at Google is $372k which is enough to get to CoastFIRE after a decade.
70.
by morgante 2y ago
He's looked at levels.fyi. He even links to it from his resume. His problem is that he thinks L10 is the benchmark to compare against, when the vast, vast majority of engineers (including many with decades of experience) would never ma
71.
by morgante 2y ago
It's absurd. He has no concept of market rates (and frankly I'm unsurprised that he's not getting hired if his expectations are this out of whack). His resume even confirms this[0], because he seemingly thinks the appropriate
72.
by morgante 2y ago
I don't think bankruptcy is the norm, since most startups don't fail with outstanding debt.
73.
by morgante 2y ago
> everyone Are you really so self-centered that you can't imagine anyone doesn't care? I'll raise my hand and say I personally am happy to trust Zed and am fine with auto-installing whatever binaries they propose. I do t
74.
by morgante 2y ago
It's obvious/quantifiable once you are in the role. I don't understand the obsession with calling all skills "technical" though. Why do you feel that need?
75.
by morgante 2y ago
This article starts with a false premise that non-technical skills are undervalued then works backwards to try to defend them. > We often dismiss skills that are not societally valued by pretending they are not skills. The truth is that
76.
by morgante 2y ago
You seem to have misunderstood, I'm not referring to the hyperscaler spending money themselves . If you don't think any ISVs are making millions through the marketplace you're simply mistaken. I worked at Google Cloud and pe
77.
by morgante 2y ago
> Almost all enterprises have pre-committed budgets for cloud which means unless your product is FOSS it's going to be hard to convince someone to bet their business on it. This isn't a death knell. 1. If you get into the marke
78.
by morgante 2y ago
> bundling an 80MB+ SQLite file to our codebase slowed down the entire Github repository and hindered us from considering more robust hosting platforms This seems like a decent reason to stop committing the database to GitHub, but not a
79.
by morgante 2y ago
Sorry, but I just don't see the "bad behavior" in polling a URL you purposefully requested it to retrieve. URLs are not secrets. Don't treat them as such.
80.
by morgante 2y ago
Interesting article, but the approach still seems like the opposite of how language server sync usually works. Typically, the LSP is notified on any file change and is responsible for keeping its own copy of the files. This way it doesn&#x2
81.
by morgante 2y ago
You certainly can make money from a user-friendly group platform. It's just not enough money to sustain a VC-backed model or a large sales/support staff. If OP is careful about managing expenses and doesn't set outlandish exp
82.
by morgante 2y ago
I think you're significantly underestimating the complexity of automatic transforms. It's not like they didn't try writing codemods first, and vim macros aren't more powerful than codemods.
83.
by morgante 2y ago
The Slack engineering blog[0] is more pragmatic, and shows more about how the approaches were actually combined. This is basically our whole business at grit.io and we also take a hybrid approach. We've learned a fair amount from build
84.
by morgante 2y ago
If you read the source article[0], they tried a rule-based approach first and the complexity exploded. [0] https://slack.engineering/balancing-old-tricks-with-new-feat...
85.
by morgante 2y ago
Completely incorrect, as Sourcegraph has not historically trained models and Cody swaps between many open source and 3rd party models.
86.
by morgante 2y ago
Do you have an example of doing this?
87.
by morgante 2y ago
It does. Just put ignored commits in a file: https://docs.github.com/en/repositories/working-with-files/u...
88.
by morgante 2y ago
> I guess they do it for the glory of having their handle next to the answer? Yes, it's hardly surprising that people find upvotes and direct social rewards more exciting than being slurped somewhere into GPT-4's weights.
89.
by morgante 2y ago
Agreed that I wouldn’t refactor this for no reason. That being said, the first time I had to edit this (even just do change the base string) I’d make the change.
90.
by morgante 2y ago
I can't believe this "refactoring" is actually presented as good—creating unnecessary abstractions for a simple function. If anything, I would go in the opposite direction. There's no need to use parameterized variables

More ›