Live data from Hacker News

Show HN: Gitlogue – A terminal tool that replays your Git commits with animation

github.com

11–20 of 21 posts

Re: Show HN: Gitlogue – A terminal tool that replays your Git commits with animation

#13
post #7

is it able to actually discern the order in which the code was written? would be cool if not to augment it or create a parallel to to actually track this in the manner the code author actually did to write the code - I wonder which functions he/she went to, how he/she wrote code, how long they paused to think, and even what they were thinking!

that's a nice idea. i wonder if applying a bit of ai summarization / grouping logic could help present changes in logical sequences regardless of time or file proximity

would probably also make sense to add quick review actions in place - like ask a question to the gitlogue tool or the author during the playback

Re: Show HN: Gitlogue – A terminal tool that replays your Git commits with animation

#14
> Screensaver — Ambient coding display for your workspace

A coworker years ago screen recorded themselves coding something, then made it their screensaver. Then would just let the screensaver make it look like they were working when they wanted to goof off. This would be prefect for them.

Re: Show HN: Gitlogue – A terminal tool that replays your Git commits with animation

#17

> Screensaver — Ambient coding display for your workspace A coworker years ago screen recorded themselves coding something, then made it their screensaver. Then would just let the screensaver make it look like they were working when they wanted to goof off. This would be prefect for them.

Would work nicely as one of the tools called by the hollywood program.

Re: Show HN: Gitlogue – A terminal tool that replays your Git commits with animation

#19
post #5

This is insanely helpful for debugging other people's code or code you've long since forgotten.

How is it more helpful for debugging compared to just looking at the git patch? As far as I can tell, this is meant to be more of a cool presentation type thing, rather than something to assist with development

Because looking at a lot of code at once can be overwhelming, also gokng commit for commit can make it hard to track the flow of everything.
Post reply on HN