samwgoldman

8 ms·

1. 1.▲
   by samwgoldman 1y ago

   (Pyrefly dev here) As another commenter mentioned, Pyrefly is still in alpha. Sorry we don't make that more clear! While we are in alpha, and there are plenty of open issues we are still working through, I think Pyrefly is actually pre
2. 2.▲
   by samwgoldman 1y ago

   (Pyrefly dev here) Thanks for trying it out! If you have any feedback or bug reports, please don't hesitate to file issues on GitHub or find us on Discord. We have some open issues for SQLAlchemy (like [1]). I'm definitely curious
3. 3.▲
   by samwgoldman 1y ago

   Thanks for trying it out! If you run into any blockers, please let us know by filing a GitHub issue or sending us a message on Discord. Pyrefly is still alpha software, so bugs are expected, but your feedback is extremely valuable as we wor
4. 4.▲
   by samwgoldman 1y ago

   Hack is quite a bit more optimized than Pyre was, but Pyrefly is at least 10x faster than Pyre on the IG codebase. I didn’t know about the Rust-based Hack checker— that’s really cool!
5. 5.▲
   by samwgoldman 1y ago

   Hey Kevin, we overlapped for a bit during your time at FB when I was working on Flow. Nice to hear from you! I’m working on Pyrefly now, but worked on Flow for many years before. For what it’s worth, we are taking a different approach compa
6. 6.▲
   by samwgoldman 11y ago

   I don't think that's what was meant, but rather that ocamlbuild sucks. It's not the best.
7. 7.▲
   by samwgoldman 11y ago

   I think the calculus changes when you consider teams with 1000s of programmers committing 100s of changes per day. Keeping feature branches up-to-date can pretty quickly adds up to a lot of time and creates a lot of friction for refactoring
8. 8.▲
   by samwgoldman 11y ago

   I haven't taken many online courses, but here are my favorites (notice a trend): Andrew Ng's ML Class - This makes the list because it is incredibly useful. I didn't have much background in the field and this class is a pract
9. 9.▲
   by samwgoldman 11y ago

   The link you provided doesn't seem to show disjoint union support. I'm talking about this: http://flowtype.org/blog/2015/07/03/Disjoint-Unions.html
10. 10.▲
    by samwgoldman 11y ago

    While the type annotation syntax between Flow and Typescript are mostly identical (this is intentional), there are a bunch of differences between them: * TypeScript allows unsound casting, Flow doesn't. These casts are very practical,
11. 11.▲
    by samwgoldman 11y ago

    One particularly relevant feature of Flow is that it does its type checking in a server. It watches the file system and incrementally rechecks automatically when files change. With this setup, "running" the type checker is actuall
12. 12.▲
    by samwgoldman 11y ago

    My approach to tight budgets is simple. There are just two rules: 1. Get to something that works ASAP 2. Always work on the most important thing Once you have something that works, you can run out of money and still have created value. I do
13. 13.▲
    by samwgoldman 11y ago

    This is bound to be a controversial opinion, but I fall down strongly on the side of time and materials billing, as opposed to fixed budget (FB). I don't hold this opinion as a way to cover my own ass, but I actually think it's th
14. 14.▲
    by samwgoldman 11y ago

    I have quite a lot of experience using migrations in Rails, and over time I've become just incredibly suspicious of "down migrations." I have never once been in a situation where I needed to use one, and even if I did, I&#x27
15. 15.▲
    by samwgoldman 11y ago

    I really admire Netflix's ability to put together developer documentation for their open source projects. I think it reflects well on their engineering culture. I was similarly impressed when I was reading the documentation for Hystrix
16. 16.▲
    by samwgoldman 11y ago

    I've been really interested in this architecture since Jay Kreps' blog post on it. One part that I'm less clear on is how this fits in with request-response style communication between, say, a Web browser and a Web server. In
17. 17.▲
    by samwgoldman 11y ago

    Basho has experienced some MAJOR brain drain in the last year. I wonder if this re-positioning is related to that.
18. 18.▲
    by samwgoldman 11y ago

    For sure, tooling is an area that will get better over time. I am quite happy with the very simple vim-flow, but TypeScript's tooling and overall ecosystem (tsd/definitelytyped) is a lot more mature.
19. 19.▲
    by samwgoldman 11y ago

    TypeScript is great, but you might look again at flow. ES6 features are being added (I'm adding let/const support) and many already exist. Import/export (incl. types) are in, fat arrow syntax, destructuring, shorthand syntax