What it’s like to come back to a Ruby project after 6 months
The hacker sits down. It’s been a long time since he worked on this project, so he figures he should probably make sure the tests are passing first.
Whoops. Right.
Darn it.
Crap.
The hacker edits the project’s Gemfile to specify the exact patch version of Ruby 2.1 currently installed.
Hell.
Righto, now…
Damn it.
The hacker kicks off the next command and steps away for some coffee and perspective.
TL;DR.
Shit.
The hacker decides to run a spec file directly.
What the shit? I know I have Postgres on this machine.
The hacker realizes that the port number shown in the error message is wrong, and edits the project’s .env file.
Goddammit.
The hacker realizes that the tests need to be run in the “test” environment.
Son of a…
The hacker edits the .env.test file to also have the correct port number.
Seriously?
And now…
Motherfucker.
Fuckity fuckity shit fuck goddammit.
I don’t remember what I was here to fix anymore.
NOTE: Any comments nitpicking particular steps in this timeline will be summarily removed. The details will vary from project to project, but anyone who has returned to a project that has lain fallow for six months or more knows exactly what I’m talking about.
