Embedded Recipes 2026 Day One – Live
youtube.com1 pointsby rettichschnidi1 comments
- Re-requesting a review once you did implemented proposed changes? Takes a single click on GitHub, but can not be done in Azure DevOps. I need to e.g. send a Slack message to the reviewer or remove and re-add them as reviewer.
- Knowing to what line of code a reviewer was giving feedback to? Not possible after the PR got updated, because the feedback of the reviewer sticks to the original line number, which might now contain something entirely different.
- Reviewing the commit messages in a PR takes way too many clicks. This causes people to not review the commit messages, letting bad commit messages pass and thus making it harder for future developers trying to figure out why something got implemented the way it did. Examples: - Too many clicks to review a commit message: PR -> Commits -> Commit -> Details
- Comments on a specific commit does not shown in the commits PR
- Unreliable servers. E.g. "remote: TF401035: The object '<snip>' does not exist.\nfatal: the remote end hung up unexpectedly" happens too often on git fetch. Usually works on a 2nd try.
And it does not capture the awe when you notice the constant crackling sounds down there. For which, as the tour guide explained to us, nobody knows the root cause, despite bright minds investigating it.
Sadly, I could not find any sources online about this topic.