tomasreimers

10 ms·

61.
by tomasreimers 4y ago
I am one of the authors of the tool Graphite ( https://graphite.dev ). We built Graphite because we missed the stack diff workflow we knew from previous job experiences at larger companies, happy to answer any questions (and if yo
62.
Ship it: our $20M bet on developer productivity(graphite.dev)
46 points by tomasreimers 4y ago|3 comments
63.
by tomasreimers 4y ago
In case anyone wants to throw it into GPT-3: Blunt: You are overcomplicating this Polite: Being mindful of timelines. Let’s concentrate on the initial scope. Blunt: That meeting sounds like a waste of my time Polite: I’m unable to add value
64.
by tomasreimers 4y ago
The history of GitHub statuses on HN is getting scarier and scarier: https://news.ycombinator.com/from?site=githubstatus.com
65.
by tomasreimers 5y ago
Can't tell if sarcasm. If not, do you believe there is value in education beyond optimizing TC?
66.
by tomasreimers 5y ago
++ to this, beyond committing frequently for your own sanity, doing so in a way that: 1. Runs CI 2. Can be merged independently (to reduce the chance of merge conflicts by preventing drift from master/main) 3. Can be reviewed i
67.
by tomasreimers 5y ago
https://tomasreimers.com I know I barely have time to maintain it :laugh-cry emoji: so minimal seemed like the right design. Probably overdue for an update.
68.
by tomasreimers 5y ago
If anyone wants a GUI version of this dashboard, check out Graphite: https://graphite.dev
69.
by tomasreimers 5y ago
Totally agree! Re an easier tool, I'm one of the co-founders of Graphite ( https://graphite.dev ), we built this tool literally to help you stack PRs on GitHub (former FB'ers who missed a stack-based workflow). It does n
70.
by tomasreimers 5y ago
Hi! I am one of the authors of https://graphite.dev , we are basically a really fancy client to GH that lets you review others PRs without making them change their workflow at all (posts everything to GH etc) We've had a fil
71.
Building Wordle with React (and Stacked PRs)(graphite.dev)
17 points by tomasreimers 5y ago|0 comments
72.
by tomasreimers 5y ago
I'm aware this isn't their primary use case, but the biggest feature missing from GDocs that moves me to notion / etc. is the lack of built in support for codeblocks. If they had that I really feel I would move most of my doc
73.
by tomasreimers 5y ago
Hi, the company I'm working on tries to solve exactly this problem: https://graphite.dev (you can read our writing on stacked branches here: https://graphite.dev/blog/post/DThX8ffP1gmxWJChEv0y ) An
74.
Evolution of the Alphabet(twitter.com)
1 points by tomasreimers 5y ago|0 comments
75.
by tomasreimers 5y ago
From the top: "FBIs ability to legally access..." Implying there are illegal ways to access?
76.
Euclidea: A game where you complete/unlock basic geometric proofs(euclidea.xyz)
2 points by tomasreimers 5y ago|1 comments
77.
by tomasreimers 5y ago
"A fairer test on this point would have compared Rust on Compute@Edge with JavaScript on Cloudflare Workers, which are at more comparable stages of the product lifecycle." Are there any widely agreed upon benchmarks on how emscri
78.
by tomasreimers 5y ago
Ah, I'm sorry you didn't find it a good explanation! I Can try and update that; in the meanwhile, maybe you would find the explanation of what the workflow is and how to do it in our docs helpful? https://docs.graphite.
79.
by tomasreimers 5y ago
This is awesome! We should add support for this to the CLI, I took a note
80.
by tomasreimers 5y ago
Totally totally totally agree. I think a lot of the slow down comes from not understanding when the ball is in your court. And Github doesn't prioritize this b/c I think this problem is less prevalent in open source, where there i
81.
by tomasreimers 5y ago
Hi! We love ghstack here and used it for a while before building this. There are a bunch of small differences between this and the various open source projects that support this workflow (ghstack, git town, spr, etc.), but the biggest reaso
82.
by tomasreimers 5y ago
A bunch of small things, but the biggest change is we also have a website to help with the authoring/review of PRs experience :)
83.
by tomasreimers 5y ago
Oh hey, I'm sorry! :( That sincerely was not my intention, and a lot of context and playfulness can get lost in comments. For what it's worth, I was simply trying to make a joke about why our marketing materials may not be as good
84.
by tomasreimers 5y ago
Hi, sadly no marketing people at this company. Just engineers and product people. We were trying to get this to work on Github for almost a year before we decided to just build this ourselves https://twitter.com/TomasReimers
85.
by tomasreimers 5y ago
So merge queue, while cool - is slightly different than Stacked changes. Stacked changes are a better client-side git workflow for dealing with branches on top of branches.
86.
by tomasreimers 5y ago
The CLI does not require any access to Github, and if you want to start doing code review on the platform, we ask for write access just so we can post comments and reviews :) Gitlab is actively on our roadmap; we currently have a few CLI us
87.
by tomasreimers 5y ago
Probably because you're trying to break up your changes. Two good blog posts that talk about this workflow are: https://jg.gg/2018/09/29/stacked-diffs-versus-pull-requests/ and https://ku
88.
by tomasreimers 5y ago
How do you deal with rebases when you have to?
89.
Stacked changes: how FB and Google engineers stay unblocked and ship faster(graphite.dev)
467 points by tomasreimers 5y ago|279 comments
90.
by tomasreimers 5y ago
Understanding how Git internals can actually be useful as more than just to build intuition or as an academic exercise! For example, where I work ( https://graphite.dev ) we use some of these plumbing commands to extend git to sto

More ›