3 ms·
100% worthy observation from my career experience. Choice of a framework both attracts a certain type/subculture, and repels another. Example: You have an old
by a4isms 4y ago
100% worthy observation from my career experience.
Choice of a framework both attracts a certain type/subculture, and repels another.
Example: You have an old app that uses Backbone+CoffeeScript for the front end. If you stick with that, it will absolutely impact your hiring. But what about switching?
If you pick React, that will have one impact. If you pick Ember, that will have a different impact. And so forth…
- a4isms 4y agoAlso, speaking very specifically about Rails, every architecture is composed of design choices that make some things easy, and other things hard. The default "Rails Way" has a particular dynamic around REST and CRUD that makes it very easy to "Extrude the implementation into the interface," and, "Extrude the implementation into the API." It's what accelerates building a thing the first time, but later on it can work against you. JM2C about this, but it's what I have observed and have lived through refactoring on multiple occasions...