3 ms·

Personally I would consider any developer that advocates what this "movement" advocates as a developer that should never touch any production code. And this is

by sputr 6y ago

Personally I would consider any developer that advocates what this "movement" advocates as a developer that should never touch any production code. And this is the reason: > Every engineer I've ever talked to or read about going frameworkless says the same thing: we ended up rolling our own. Reading their critiques of frameworks the only thing I could say at every point was "yeah, but not using a framework is even worse". I think this is nothing more than the "I am very smart" sentiment. Well I'm not smarter than (large, respected) framework designers. Most developers aren't. And it's not just a matter of "learning" but a fact that neither I, nor most other developer will ever be. And why should we be - that's just reinventing the wheel, isn't it? We should focus on our own specific domain challenges. And yes, it means doing things "the framework way". Because most of the time it IS the better way, even if I can't realize that yet (oh, but I will in a few months).

deleted 6y ago
[deleted]
omniscient_oce 6y ago
Yeah I caught myself almost doing something similar when I wanted to implement some internal tools with a React webapp and a backend server that I was going to write in Go because I wanted to learn Go and it seemed like it would have better performance, yada yada. Then I came to the (obvious) realisation that the other guys have predominantly experience in JS/TS so it would be kind of irresponsible of me to force anyone else who wants to contribute to this now or in the future to have to do it in a new language, rather than the one that we use in our main project. Ended up going with Typescript and I think it was definitely the right choice. For production code you just gotta go with what A) works. B) the rest of the team is familiar with (or has a reasonable chance of learning enough to read/contribute)
- bckr 6y ago
  Irresponsible or good job security practice?

by sputr 6y ago

deleted 6y ago

[deleted]

omniscient_oce 6y ago

Yeah I caught myself almost doing something similar when I wanted to implement some internal tools with a React webapp and a backend server that I was going to write in Go because I wanted to learn Go and it seemed like it would have better performance, yada yada. Then I came to the (obvious) realisation that the other guys have predominantly experience in JS/TS so it would be kind of irresponsible of me to force anyone else who wants to contribute to this now or in the future to have to do it in a new language, rather than the one that we use in our main project. Ended up going with Typescript and I think it was definitely the right choice. For production code you just gotta go with what A) works. B) the rest of the team is familiar with (or has a reasonable chance of learning enough to read/contribute)

bckr 6y ago
Irresponsible or good job security practice?