morgante

12 ms·

121.
by morgante 3y ago
Thank you! We definitely want to give useful value to everyone. To expand more on our business model, we see GritQL as a powerful but also relatively low-level tool. It can speed up your migration, but writing the query and generating/
122.
by morgante 3y ago
We don't have semantic information yet (it's on the roadmap), but in many cases it's sufficient to get that information from the AST by looking where the variable was originally defined. For example: https://app.gr
123.
by morgante 3y ago
In theory, you could write a full transpiler in GritQL. In practice, it's not really the ideal tool for translating between languages. It does work well for cases where the differences are minor (ex. converting from JavaScript to TypeS
124.
by morgante 3y ago
Makes sense, we internally use GritQL as a super linter for some codebase-specific patterns. It's pretty easy to set up: https://docs.grit.io/guides/ci We've looked at both LSIF and SCIP from SourceGraph, tho
125.
by morgante 3y ago
One of the specific design goals we had was to make sure that the query engine isn't tightly coupled to AST nodes. We started with the AST, since that's ultimately the foundation for code but the goal is to add more graphs on top.
126.
by morgante 3y ago
The C is all generated parsers, all our actual coding is done in Rust.
127.
by morgante 3y ago
ast-grep is great too, we've learned a lot from it. If you like yaml, you should definitely try ast-grep. The main area GritQL shines is in taking simpler transformation patterns and composing them into complex migrations. For example,
128.
by morgante 3y ago
Thanks Alex! Your feedback has been super helpful. Your suggestion to add the `--interactive` flag was hugely helpful, it's become very commonly used.
129.
by morgante 3y ago
Thanks Paul! It's been great getting your feedback as we've evolved Grit over time.
130.
Show HN: GritQL, a Rust CLI for rewriting source code(github.com)
280 points by morgante 3y ago|54 comments
131.
by morgante 3y ago
Their beds are also great. It's the only solid, high-quality furniture I've ever owned. It's not cheap, but easily much higher quality than anything else in the same price point.
132.
by morgante 3y ago
It's unfortunately terrible wording from GitHub for any app install: https://github.com/orgs/community/discussions/37117 Despite the scary warning, you're only granting the listed permissions.
133.
by morgante 3y ago
i don't think deterministic programming languages are going away. Even if code is AI-generated, critical systems need to behave consistently and be available for introspection/editing.
134.
by morgante 3y ago
The early stages of many companies are pretty nebulous as you're exploring different ideas/positioning and building the basics. It's reasonable that someone joining <1 year in would be considered a co-founder if they had f
135.
by morgante 3y ago
The company was burning money and growing slowly. Most of the original investment was likely based on the strong founding team. In that situation, they'd probably just want their money back.
136.
by morgante 3y ago
Cryptocurrency has basically completely inverted the trust issue it's meant to solve (at least for many developers). In theory, a decentralized ledger of project contributions / owners is a good idea for distributing sponsorship d
137.
by morgante 3y ago
> This isn't about memorizing jargon. It's about understanding the basics of enterprise software development. Google3 is one of the biggest repositories of enterprise software in the world. I've been in dozens of engineeri
138.
by morgante 3y ago
> You don't need to memorize the acronym, but saying you've "never used SOLID" isn't the brag you think it is. You said that if "they don't know what SOLID, KISS, and DRY are, are the same candidates wh
139.
by morgante 3y ago
I wouldn't put SOLID in the same category as KISS/DRY. The latter are pretty universally understood principles, but I've never used SOLID despite passing dozens of challenging technical interviews and leading teams across sta
140.
by morgante 3y ago
> ... or I could do what I'm doing, and sit in my bedroom on my butt, mostly coding up a prototype, relying on being well-known enough to bring in money based on my personal brand, collecting a reasonable salary. That's fine? I
141.
by morgante 3y ago
Sorry, but if your ambition is to start a $1B company, 3 months in SF is a relatively small sacrifice no matter your age.
142.
by morgante 3y ago
YC effectively already is that global program. There are YC startups from all over—spending 3 months in SFO does not require you to move there forever, and many do return to other markets/locations.
143.
by morgante 3y ago
At some point they simply stopped trying to compete with YC (probably because they can't). The terms are worse, the program is worse, and the only differentiation is not being in the Bay Area (which YC moved away from anyways). The end
144.
by morgante 3y ago
Fired employees are much more likely to do something malicious, either by sabotaging systems or stealing proprietary data. The incentives are totally different.
145.
by morgante 3y ago
It has nothing to do with being "people-first" or not. Leaving terminated employees with access to sensitive systems is poor security practice.
146.
by morgante 3y ago
> Fly.io is not comparable to Kubernetes. The Fly team has worked on solving similar problems to Kubernetes. Ex://fly.io/blog/carving-the-scheduler-out-of-our-orchestrator/ Of course, Fly also provides the unde
147.
by morgante 3y ago
Unfortunately this is a pretty common story. Half the people I know who adopted Fly migrated off it. I was very excited about Fly originally, and built an entire orchestrator on top of Fly machines—until they had a multi-day outage where it
148.
by morgante 3y ago
It's not just that people get pushed out of IC work, but everyone tends to have less energy as they get older + other life demands accumulate. The combination of 10-15 years of experience and the energy/time of 20s is very powerfu
149.
by morgante 3y ago
Yes, everyone should respond. From the hiring manager side, it's sometimes hard (especially when people argue with you) but I still think it's worth doing. I'm sorry you're having a hard time. I'm sure it's ver
150.
by morgante 3y ago
I'm not sure why you think companies have an obligation to talk to every candidate that applies. It's pretty common to get hundreds of applications for any open role now, and the most visible companies get thousands of application

More ›