TechPulseTechPulse
Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

100% Positive

Analyzed from 253 words in the discussion.

Trending Topics

#run#bin#here#scripts#yeah#post#author#got#project#workflows

Discussion (10 Comments)Read Original on HackerNews

dewey•about 20 hours ago
To the blog post author commenting here: Your comment got flagged / dead, probably because it reads as AI generated so it won't be visible to anyone.
tracker1•about 19 hours ago
I've been doing similar for many scripts within project workflows... I've started calling the directory in question ./run/ by convention, so I type run/scriptname to run stuff... I've got bash (extnsionless) and powershell (ps1) scripts in place on my work project).

I'll also lean into docker+compose usage for any background services, and even development in order to reduce the running footprint switching projects.

grepsedawk•about 17 hours ago
Love it! Same here. bin/ is a convention I picked up from Rails and thoughtbot over the years. I also have bin/staging and bin/prod for data fixes, deploy helpers, and querying the DB, alongside bin/test and bin/dev.
tracker1•about 17 hours ago
Yeah, I've used bin/ and scripts/ in the past as well as _scripts/ ... but I just like the ergonomics of run/foo... run/api, run/ui, run/api-test, ... etc.

I'm usually working in a subproject, so it's usually ../../run/foo in practice, but still.

grepsedawk•about 17 hours ago
Yeah! All the same. I love this pattern.
hmokiguess•about 19 hours ago
How amazing that git launched this way ahead of it becoming the ubiquitous choice for AI native development workflows
grepsedawk•about 17 hours ago
Yeah! Worktrees were already sitting there. Agents just turned them from an occasional convenience into something I use every day.
grepsedawk•about 20 hours ago
Author here. Parallel worktrees showed me where Git’s isolation ends. Files stayed separate; ports, databases, cache keys, queues, and Compose resources did not. We now share compatible services and isolate names per worktree. Which shared resource has been hardest for your team to isolate, and why?
8jy89hui•about 17 hours ago
Did you write your post with AI? It is really painful to read in some parts (mostly because of the cliches of AI)
grepsedawk•about 17 hours ago
Actually no, sat down and wrote it out. Did some AI proofreading but applied the suggestions by hand. Would be interested to hear what parts were painful.