3 ms·
For me, at this point, using exciting technology is like writing a book on exciting paper. I'm not interested in any framework with a philosophy, any language
by rogual 6y ago
For me, at this point, using exciting technology is like writing a book on exciting paper.
I'm not interested in any framework with a philosophy, any language with a fan club, or any library with an opinion of how I should be doing my job.
I want to use "technology" that works and stays out of the way so I can build useful things. That's where the excitement is -- in the stuff I'm building.
- mattgreenrocks 6y agoThis reason is why I don’t get along well with most frameworks. Most frameworks are infuriatingly self-interested. They’re so intent on telling me that their imposed architecture is superior, despite knowing nothing about how I’m using it. And then there’s the social pressure to use tech that specifically aims to make devs interchangeable.
- ghaff 6y ago>And then there’s the social pressure to use tech that specifically aims to make devs interchangeable. Everyone has an interest in a degree of interchangeability. How mobile do you think developers would be in a world where it took them a year to get up to speed on a new set of tooling, languages, frameworks, etc. every time they switched jobs?
- mattgreenrocks 6y agoNot sure who is arguing that. I have problems with the idea that devs really should spend most of their time coloring by number rather than amassing domain knowledge and expertise in the craft of development.