3 ms·
This part puzzles me: > "Put yourself in the shoes of a junior-to-mid-level JavaScript developer, writing a new application for the first time. > "It starts i
by pavlov 8y ago
This part puzzles me:
> "Put yourself in the shoes of a junior-to-mid-level JavaScript developer, writing a new application for the first time.
> "It starts innocently enough. You have a completely clean slate and want to keep things simple. You are a devout Agilist and YAGNI is your watchword. So you begin with a ‘simple, barbones framework’. That sounds good, doesn’t it? (Even if it did not, that’s often the only choice you’ve got).
> "Being barebones it does little, so the task falls on your shoulders to choose some helper libraries. If you are doing frontend work, it might be helpers for Redux for forms and API requests. If backend, it might be middlewares for Express."
Why is the default answer to the problem of "it does little" to "choose some helper libraries"? Shouldn't it be: "I'll write some code to make it do more"?
Why does this first-time app developer need Redux? Why would she need a helper for Redux to do API requests? These days you can just call fetch() — it really doesn't get any easier.
All the APIs that one gets in the browser or in Node.js are already very high-level and easily understandable by entry-level developers. If anything, piling more leaky abstractions on top will just make things more complex. How did it happen that junior JavaScript developers feel so insecure about using the standard stuff?
Maybe it's because more senior developers have spent two decades crapping on the standard stuff. Therefore, as a self-appointed spokesperson for the veterans, I hereby grant all junior JavaScript developers full permission to just go ahead and program whatever they want without having to look for a single library or creaky build tool — and they shouldn't feel bad about it in the least.
- Omnius 8y ago> How did it happen that junior JavaScript developers feel so insecure about using the standard stuff? I know a lot of "developers" that are learning frameworks and not javascript. When you start in a black box then you look for other black boxes to fill in the gaps you need. I am not even opposed to that. I strongly believe in never re-inventing (unless its academic) what can be used and has been tested, but when the developers are not javascript developers but react, vue, angular developers. Then you get this gap where the inexperienced are afraid to outside of what others have built.
- pavlov 8y agoOne has to learn somehow, and reinventing is an important part of that. Aspiring artists will paint nude figures and flower arrangements and white cubes on draperies, even though these subjects were done to death centuries ago. Junior programmers should feel the same way about doing things that have already been done: someone probably has done it better, but I still have to do it for myself, maybe a few times over to get the hang of what's the point.
- Omnius 8y agoI don't disagree its why i said unless its academic.
- Retra 8y ago>How did it happen that junior JavaScript developers feel so insecure about using the standard stuff? Because job postings don't say "Wanted: Junior developer with standard stuff JavaScript experience."
- pavlov 8y agoSomeone writing their first app shouldn’t be worrying about that.