epage

36 ms·

391.
by epage 5y ago
To clarify then, the two groups made accusations against different people: - A core team member made an accusation against Amazon - The mods had concerns with the lack of oversight of the core team
392.
by epage 5y ago
He is a current core team member, not former [0]. I'm not too worried about his claims. His claim was about the Foundation being shadow-controlled by Amazon (they employed the board chair who had more influence while they lacked an Exe
393.
by epage 5y ago
From what I've heard, they are still working things through. These things take time and we just had a holiday in the US.
394.
by epage 5y ago
I used to use aliases but got frustrated with them when dealing with PRs depending on PRs, so I wrote git-stack [0]. Thought I'd share in case you'd find it useful [0] https://github.com/epage/git-stack/
395.
by epage 5y ago
In my skimming, it sounds like its mostly targeted at plugin developers. The main directly user-impacting part seems to be the adjustments to defaults.
396.
by epage 5y ago
> They wanted changelogs for everything but as soon as another PR was merged it would result in a merge conflict. I'm tempted to move to fragments that a changelog is generated from to avoid conflicts. I just haven't gotten aro
397.
by epage 5y ago
I've recently left a Rust project and the maintainer's perfectionism was one part. From my observation, the causes tend to be: - Maintainers spread thin, putting more of a burden on contributors - Some projects being critical and
398.
by epage 5y ago
I'm biased as the author of git-stack but struggling with this problem is why I wrote it. When I started it, I didn't know there were so many tools in this space. However, if I knew then what I knew now, I would have still writt
399.
by epage 5y ago
This has come up several times in the past. One name for it was stdx. Some in the ecosystem are very cautious of picking winners and losers, limiting the exposure to new break-out crates. Rarely recommending crates for different problems.
400.
by epage 5y ago
> 2. No multiple package versions. If there is a version conflict between transitive dependencies of a package because of semver, you should not be able to install that package. I am grateful Rust allows this unlike C++ or Python. While
401.
by epage 5y ago
I suspect something missing in pair programming that you get in a code review is someone stepping back and looking at the change as a whole, rather than the incremental bits as you go along. It can be helpful! I know at least when reviewi
402.
by epage 5y ago
My primary experience with pairing was not ideal. It was being used in a mentoring capacity rather than when people are more equal. I also found that the person doing the mentoring usually drove which meant that the mentee just saw things
403.
by epage 5y ago
I feel the hard part is putting automation around this. I loved it when I worked on a small, high trust team where we were comfortable with each person making the decision on whether it was safe to do a post-merge review or that it needed a
404.
by epage 5y ago
Github has been improving on this. I felt like they were rolling out the features I wanted right as I was enumerating them! They have - Auto-assign reviewers - Pings for people (unsure how sophisticated) - Auto-merge The review conversatio
405.
by epage 5y ago
When I was doing product evaluation at my last company, I was torn between AzDO and Github. After being burned by the lack of progress on Phab (before it went away), one of our criteria was what I called a "living platform" meani
406.
by epage 5y ago
At my last job, I found our code review process was terribly slow and set about analyzing it and coming up with solutions. I found a lot of developers were blocked on reviews. They either task switched (expensive) or babysat their review
407.
by epage 5y ago
For anyone interested, I've been collecting notes on various tools in this space: https://github.com/epage/git-stack/blob/main/docs/comparison... (granted the page doesn't mention git-stac
408.
by epage 5y ago
I loved Ann Arbor when I visited when I was hired at Duo and it has raised my interest in moving to Michigan (once a job allows it, my current remote gig has limited locations due to logistics) but I doubt it will be A2 just because of the
409.
by epage 5y ago
For me, its the explicitness in Python that is killer. I can see a name and match that to an import and match that to a package. Grabbing a function pointer works exactly as I would expect. Stealing from Krister Stendahl's laws for r
410.
by epage 5y ago
It can be done well, see Zig's traces [0]. [0] https://ziglang.org/documentation/master/#Error-Return-Trace...
411.
by epage 5y ago
> does that really come up a lot? I have. My middle name is both obscure in its sound and more obscure in its spelling.
412.
by epage 5y ago
Ours was Stardust, tying into part of their name that is a constellation name.
413.
by epage 5y ago
Girl names are been relatively fun but boy names have been a challenge. The options feel limited if you want one that isn't overdone but isn't ... strange.
414.
by epage 5y ago
When I was designing the programmatic API for my programmer's spell checker [0], I found that it was easy to get an exit code from something else in the stack and if they all used 1, there wasn't a way to differentiate. This is t
415.
by epage 5y ago
The main arg parser for Rust (clap) was looking at using sysexits for usage but then got feedback from burntsushi (of ripgrep fame) for how rarely it is used and instead encouraged 2. In looking at it, it seems like 2 is the most consisten
416.
by epage 5y ago
There is sccache ( https://github.com/mozilla/sccache ) so a first step would be looking to see why it isn't used more to see how to lower that barrier. Another idea is crate-build caching so local and CI can pull d
417.
by epage 5y ago
For now, it looks like they are using Gitlab's model where they are speculatively executing items in the merge queue which will push up against max concurrent runner counts (cloud) and run up bills (self-hosted). I hope they add bors-
418.
Pull Request Merge Queue Limited Beta(github.blog)
3 points by epage 5y ago|1 comments
419.
by epage 5y ago
I'd also call out git-stack [0] as an option Visualize current tree: $ git stack Show what the ideal tree will be post-pull: $ git stack --pull --dry-run Perform pull and show the actual tree (e.g. we don't handle merge-conflicts)
420.
by epage 5y ago
git-move and git-branchless do some great stuff, I wish this wasn't focused on the performance side to distract from the real value. What I find useful is not the performance but this line > For example, it can move entire subtrees

More ›