4 ms·
For some reason, Rails is the only framework I’ve worked with that seems to require constant discussions about design patterns and best practices. I don’t know
by devoutsalsa 3y ago
For some reason, Rails is the only framework I’ve worked with that seems to require constant discussions about design patterns and best practices. I don’t know why.
- notjoemama 3y agoInteresting. I worked on a team for several years and our discussions were completely absent of design patterns and best practices. I'm older. Do you think age/experience plays into it? I only ask because I'm not interested in those discussions anymore because I feel like I've already had them all.
- devoutsalsa 3y agoI did an interview not to long ago where the hiring manager was asking me all about Rails best practices, design patterns, and other Ruby-isms. Spent very little time talking about the actual problems he was trying to solve. Also spent a lot of time asking me how I’d fix an 1100 line controller with no tests and many code paths. He also talked a lot about how he had fired all of the developers that made this mess, and also needed to hire senior developers that could move quickly. It was a very strange interview.
- notjoemama 3y agoJeez. I'm sorry you had to endure that. In case no one mentioned it, you can wrap up the interview yourself. I know its uncomfortable to do but some places need to grow up more than they need to hire a developer. Good luck in the future!
- winrid 3y agoSounds like you never worked on a large NodeJS project. That's all they do, at every company I worked at, when using Node. :P