Transitioning a Large Rails Codebase into Packages: Seeking Tips and Advice from Experienced Developers

Message originally sent by slack user U7213XMGS3H

this is the part that feels relevant

As software engineers, the things we build are unlike anything else out there. They’re in constant flux and can change drastically over long periods of time. Imagine if the people building an elevator system in a skyscraper found out a decade later that they were actually building a subway system! That’s what it sometimes feels like. The decisions that were made when you were making the elevator don’t always hold up in hindsight. The context has shifted 90 degrees.

Message excluded from import.

Message originally sent by slack user U7213XMGS3H

yeah

Message originally sent by slack user U7213XMGS3H

but sometimes you have an elevator that’s in use as a subway system that 1m people use every day

Message originally sent by slack user U7213XMGS3H

and you can’t just throw it away

Message originally sent by slack user U7213XMGS3H

and you have to figure out what comes next

Message originally sent by slack user U7213XMGS3H

and i think that’s very cool!

Message originally sent by slack user U7213XMGS3H

and an exciting hard problem

Message excluded from import.

Message originally sent by slack user U7213XMGS3H

sometimes the team you’re on is only 5% the same as the team you started the elevator, if that!

Message excluded from import.

Message originally sent by slack user U7213XMGS3H

i just mean i like my job, and this problem space

Message originally sent by slack user U7213XMGS3H

it’s wild that the elevator became a subway…… but it did! now we get to figure it out

Message excluded from import.

Message excluded from import.