@mattzcarey There is definitely a good range for companies that went all into microservices with hundreds of repos that can be consolidated into multiple monorepos for related functions but the single monorepo to conquer them all approach is whack. It doesn’t have to be one or the other.
@zeeg I agree with the sentiment, but it seems you’re judging systems design expertise via code? You can def tell within 15m if the person knows architecture or not.
Pseudo code/diagrams are helpful as a tool to communicate ideas but not required.
Green Day’s Brain Stew version from the 98 Godzilla movie is WAY better than the original but it’s greyed out in Spotify… boo!
Give me that reverb snare drum, timpani drums, orchestral strings and Godzilla roars ANY day of the week!
Don't assume bad intentions. It's like healthcare in the US. Doctors will prescribe what they think is objectively the best solution, without being biased by your specific situation.
Take all the advice from frontier labs with a huge grain of salt. By design or not, their workflows assume you're ok spending a ton of tokens.
Having a 24/7 always-on agent sounds great in practice. Look ma! I pushed a bajillion PRs today!
Don't lose track of your outcomes.
@jaredpalmer@github Oh boy, SO many but first:
- Don’t hide update with rebase,& don’t make force pushes look like the worst thing ever in the UI.
- “warning” as result for PR Checks.
- Custom merge templates like Gitlab, where you can use macro variables e.g %{commit_sha}
https://t.co/eAplQQrwqB
I'm fully aware that there are probably edge cases for both of these, but it's so great that custom-ish features can be done now. Codex did both of these in a few hours.
Can you imagine if things like this could have been supported near launch? Emotion just works. 🫳🎤
The Bun rewrite and TanStack inspired me to do what I've been waiting for, literally years, in Next/React.
In Next, the lifecycle hooks of _document in App Router. i.e., let me hook up RSC + server rendering before flushing the initial chunk. 🙌
In React, unlock RSC context! 🙏
To support the RSC context, all React needs to do is allow exporting getServerTreePath, and the rest can be done in userland.
React already has `currentlyRenderingTask` internally. Can't fit the whole patch in a screenshot, but you get the gist.
@bstaples Right. My point is ship some adapter/codemod that does this. Make it a no-brainer.
Also gitlab-ci.yml is one file. Modularizing with include is not great.
.gitlab/*.yml is the way to go.
@Steve8708 This is timely! I’m basically building this in-house. Do you support bringing our own agents and hook to other sources like Microsoft Teams?
@ScriptedAlchemy Ah got it, so technically it’s all bc they bundled webpack? If I were to patch Next to remove that and the require hooks, it would work?
I’m already patching Next for other things so I’d be highly interested in that.
@Kpaxs The biggest nuance here, when you fix something, you want to be the "Glue" and not the "Gap Filler".
You can fix/do something while bringing people together (even if it isn't really required), and it makes a world of difference.