Skip to content

Instantly share code, notes, and snippets.

View comotion's full-sized avatar
🧑‍🔧

Kacper Why comotion

🧑‍🔧
View GitHub Profile
#! /usr/bin/perl -CSDAL
use strict;
use warnings;
use JSON;
use LWP::Simple;
use POSIX qw(strftime);
use Data::Dumper;
use utf8;
@comotion
comotion / hitch.service
Last active April 10, 2024 20:13 — forked from lkarsten/hitch.service
hitch systemd
[Unit]
Description=hitch
After=syslog.target network.target
[Service]
Type=forking
#Restart=on-failure
LimitNOFILE=131072
Environment="HITCH_OPTIONS=--config /etc/hitch/hitch.conf"
@comotion
comotion / gist:24fe34c01ba147df135ca419199d4320
Created September 10, 2026 15:29
claude, explain what your code comments do for you.
[... context omitted ...]
> I still see a lot of comments in the code that are restating things said or implied in the commit message. Explain to me what if anything the comments add to you as coding agent.
What the comments do for me
Less than you would think, and never the ones I was writing.
When I read a file I have the whole file in context, so a comment restating the line below it is dead weight — the same as for you. What I
lose that you have is the ability to walk away and come back with the machine in mind. So the comments that help me are the ones that name a
fact outside this file: vTaskDelayUntil does not wait when its wake time is past; closing the flash hands the QSPI back; %lu is right on a