Recent submissions

Comment · 4 days ago
Yes, unfortunately
Comment · 1 year ago
I actually laughed out loud at how different this is to the usual "be yourself and to hell with what people think" advice. Can you elaborate on why it's so important to care if people like you?
Comment · 1 year ago
Hopefully stupid question but were you replacing the pen nibs? My screen has been solidly responsive for several years of heavy usage, but the fiber nibs do get worn down and need replacing every few weeks/months (by design) or the pen starts exhibiting this behaviour.

I have to admit I have also switched back to real paper for a lot of tasks but I still like the remarkable as an e-reader, and enjoy writing on it occasionally, so I wouldn't say it's a big regret.

Comment · 2 years ago
Thanks! Gippity did suggest the xargs approach as an alternative, but I found that

find [...] - exec [...] {} +

as opposed to

find [...] - exec [...] {} \;

worked fine and was performant enough for my use-case. An example command was

find . -type f -name "*.html" -exec sed -i '' -e 's/\.\.\/\.\.\/\.\.\//\.\.\/\.\.\/\.\.\/source\//g' {} +

which took about 20s to run

Comment · 2 years ago
It's a case of convergent evolution - I don't know where I heard it first, but I asked GPT if it minded and it said "Of course, you can call me Gippity!", so I do, because it's more fun.
Comment · 2 years ago
Primeagen is some kind of Youtuber? I am not familiar and don't understand what you are trying to convey here.
Comment · 2 years ago
There's undoubtedly a setting but if you don't want it on all the time you can always add \c at the end of the search term, like /foo\c to denote case insensitivity
Comment · 2 years ago
100% agree. I'm currently preparing several 10s of GBs of HTML in nested directories for static hosting via S3 and was floundering until Gippity recommended find + exec sed to me. I'm now batch fixing issues (think 'not enough "../" in 60000 relative hrefs in nested directories') with a single command rather than writing scripts and feel like a wizard.

These tools are things I've used before but always found painful and confusing. Being able to ask Gippity for detailed explanations of what is happening, in particular being able to paste a failing command and have it explain what the problem is, has been a game changer.

In general, for those of us who never had a command line wizard colleague or mentor to show what is possible, LLMs are an absolute game changer both in terms of recommending tools and showing how to use them.

Comment · 2 years ago
Also just realised while looking at the docs it works for search as well as replacement, with:

:S/textToFind

matching all of textToFind TextToFind texttofind TEXTTOFIND

But not TeXttOfFiND.

Golly!

Comment · 2 years ago
This reminds me of the substitution mode of Tim Pope's amazing vim plugin [abolish](https://github.com/tpope/vim-abolish?tab=readme-ov-file#subs...)

Basically in vim to substitute text you'd usually do something with :substitute (or :s), like:

:%s/textToSubstitute/replacementText/g

...and have to add a pattern for each differently-cased version of the text.

With the :Subvert command (or :S) you can do all three at once, while maintaining the casing for each replacement. So this:

textToSubstitute

TextToSubstitute

texttosubstitute

:%S/textToSubstitute/replacementText/g

...results in:

replacementText

ReplacementText

replacementtext

Comment · 2 years ago
Curious if you have any examples of these pains? I'm not familiar with the late Python 2 era but I've been writing Ruby for a long time and wonder if I'm doing some of these as well.
Comment · 2 years ago
"Nice" is a very subjective concept and can be used to describe people in both complimentary and derogatory ways. In my experience niceness and competence are in no way correlated – I have known nice people who were good at their jobs and assholes who were good at their jobs, as well as some of both who were terrible at their jobs. It is perfectly possible to be both competent and nice.

Given the choice between two persons of equal competence, where one is nice and one is not, I would be surprised if anybody chose the less nice one, all other things being equal.

I suggest continuing to be genuine, rather than focusing on "niceness", and not allowing a single comment on the internet to make you feel self-conscious about your character.

Comment · 2 years ago
Comment · 2 years ago
I not infrequently find myself prefixing my own code review comments with some variant of "I'm mostly asking this to make myself sound smart, but..." and then usually (not always) I delete the comment. But it's not a high proportion of my total review output, assuming I'm impartial enough to tell the difference.

My point is, it definitely happens, but if it applies to _most_ PR comments I think the code review practices of your project may need improving. My experience has been that most code review comments are either seeking to impart or gain knowledge that the commenter genuinely finds useful.

Comment · 2 years ago
Pacifiers.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton