01
A script with no framework around it is easy to under-document
Rails projects at least come with a predictable structure; a standalone Ruby script or gem often doesn't, which means its logic lives mostly in whoever wrote it. If that person is a freelancer who's gone, the only documentation left is the code itself. We document what we build well enough that it doesn't depend on one memory.
Logic that only existed in one person's head.Documentation that outlives whoever wrote it.
02
Who's accountable when the ticket wasn't actually the problem
A freelancer paid for a specific Ruby task delivers that task, even if it doesn't fix what was actually going wrong. We're accountable for the underlying issue getting solved, which sometimes means telling you the original ask needs to change before we start, not after we've billed for it.
The ticket done, the real problem untouched.Accountable for the problem, not just the ticket.
03
Comparing a freelancer's rate against the real cost of a brittle script
A cheap freelance rate for a quick Ruby script doesn't account for what happens when it silently breaks and nobody's around who understands it well enough to fix it fast. A free quote gets you a number that reflects the actual job, not just the hours to write the first version.
A cheap script, an expensive silent failure later.A quote reflecting the real job, not just the first draft.