greg0ire

A blog post I wrote a while ago about testing in Go. Got filtered on Reddit because apparently, people posting on dev.to often generate their posts with AI. This one is 100% organic, but the code it talks about was initially vibe coded. Writing this blog post allowed me to review it more carefully, and to understand it better.

5. git revert is tedious When one commit turns out to be bad, you can't revert it cleanly because your "Fix linting issues" builds upon it.

In https://howhttps.works/the-keys/

The public key is represented by a blue key but… wouldn't it be more simple to say the public key is an open padlock the sender closes on the box after putting their message in it? Padlocks can only be open by one key, the private one.

It's equally frustrating to have cs commits fixed up with a meaningful commit, making the diff of the meaningful commit ugly.

This is wrong at so many levels. Of course we don't care about "progress" or "woops I fucked up" commits, but people also do commits for things like coding style, and these commits should be keep separated from the others, and DO NOT warrant a separate PR. If it is about changing all tabs to space in a file, for instance, different PRs will be hard to work with, because of conflicts. Also, people who write WIP commits should learn how to squash them themselves, and give them a meaningful commit message.

Yeah, plus, the fact that you fix something is the "why" part of your commit message, it should go in the body. The result could look like this :

> Reduce overlaying div element width > > This caused a bug on some devices : the div would overlay the close button, causing it to be unreachable.

I think that commit message that begin with "fix" are often not very good. Basically, you're saying "It was broken, this commit fixes it", not what was broken nor how your commit is supposed to fix it (yeah because sometimes, people think they are fixing something and actually create another bug in another part of the thing).

It also works with reset and checkout, BTW.

> It is an utter waste of time compared to point-click-go-go-go.

Clicking = moving your hand from the keyboard to the mouse. So it's actually point-click-go-back-to-keyboard-go-go-go when it could be type-go-go-go (or go-go-go-go, if you prefer) . I use vim and when I help colleagues that use phpStorm, they seem slow as fuck. Since they have a sidebarmenu, they don't think about their fuzzy matcher, they don't split their display to show 4 files instead of just one and keep navigating through tabs they did not really mean to open.

Maybe you could run these Adobe tools in a Virtual Machine ?