3
points
tomasreimers
Joined 1,013 karma
- tomasreimersLove JJ and think you should learn it because it's fun - but Graphite's not going anywhere
- Any ways I could convince you to?
- Don't worry - we're not going anywhere. The goal is to continue building and maintaining the product.
- No concerns! The plan is to maintain and improve both
- Not immediately - but I'm sure we'll find ways to bring the two products closer together over time :)
- Hi! One of the Graphite co-founders here. Happy to answer any questions :)
- Hi! Another one of the Graphite co-founders here. Alongside Greg, happy to answer any questions :)
- We've talked about a "safe mode" where we initialize it similar to JJ - such that you can no longer directly run git commands without funneling them thru graphite, but which would make it bulletproof. Would that be interesting?
- Just taking a step back, it is SO COOL to me to be reading about stacked pull requests on HN.
When we started graphite.dev years ago that was a workflow most developers had never heard of unless they had previously been at FB / Google.
Fun to see how fast code review can change over 3-4yrs :)
- 68 points
- Certainly! A lot less proof reading and pair programming and a lot more architecture / "hey should we be going in this direction" / sharing tribal knowledge
Also hi Peter! Long time :)
- This.
- I've felt like a broken record the past few weeks, but this.
Authoring has never been the bottle neck, the same way my typing speed has never been the bottle neck.
The bottle neck has been, and continues to be, code review. It was in our pitch deck 4 years ago; it's still there.
For most companies, by default, it's a process that's synchronously blocked on another human. We need to either make it async (stacking) or automate it (better, more intelligent CI), or--ideally---both.
The tools we have are outdated, and if you're a team with more than 50 eng you've already spun up a sub team (devx, dev velocity, or dev productivity) whose job is to address this. Despite that, industry wide, we've still done very little because it's a philosophically poorly understood part of the process (why do we do code review? Like seriously, in three bullet points what's the purpose - most developers realize they haven't thought that deeply here).
- 36 points
- The opening animation is so so so good.
- You can check if a number is using Twilio via a special number: https://www.twilio.com/en-us/blog/lookup-phone-carrier-recor....
- I remember when I was working on https://medium.com/@tomasreimers/compiling-tensorflow-for-th... I thanked my lucky stars that TF used Eigen and not one of the popular math libraries (BLAS, Lapack) written in fortran b/c that would have been A LOT more work...
- Reminds me of a sidechannel attack I demo'd in college:
https://medium.com/@tomasreimers/axolotl-a-keylogger-for-iph...