4 ms·

I didn't know that all these new Javascript frameworks were making me smart.

by singham 10y ago

SNvD7vEJ 10y ago
So that's why webdevs are so smart!
unusximmortalis 10y ago
Not necessarily smart but trained. Yes, many times I thought about the problems I am solving, and new things I learn from the last 20 something years since I am in love with IT world. There are times when the problems repeat but many times problems are different so my approach and solution is different. Also new tech waves keep me trained cause I want to stay up to date and I want to learn what the new tech is solving or improving.
savanaly 10y ago
You joke, but honestly all the web devs that learn a new framework annually will be pretty good at picking up new frameworks after five or ten years. Of course, most of the people who fret about the state of the javascript ecosystem are doing it needlessly from the sidelines and don't themselves ever learn any of the new stuff.
- dualogy 10y ago
  > will be pretty good at picking up new frameworks after five or ten years ..or however long until the concept in question becomes irrelevant..
  - deleted 10y ago
    [deleted]
- jbeja 10y ago
  Yeah, I only limit myself to learn stuff that have proven to be useful to me in the js world. For example: Reactjs is the only framework I use because it actually abstract away a lot of recurring patterns and boilerplate that would proliferate without it. TypeScript is another one, since already improved my workflow given the IDE capabilities it provides and having a type system to automatically self document my code is really usefull.
- mattmanser 10y ago
  Do your clients all have projects that shut down after a year then? One of my clients has 2 projects in durandal that I've picked up. No-one uses it any more, the documentation sucks ass, there's sod all on SO, the original devs had only done data access pages, super easy, not the data editing pages, absolute nightmare, so you can't even copy what they did before. It's a bloody nightmare to work in. Pages which would take me an hour or two in an older tech are taking me days in this half-baked SPA. I'm not on the sidelines because I'm fretting mate, I'm on the sidelines because the messes left behind are a fucking nightmare for those afterwards and an absolute disgrace to the profession. It feels like the framework switchers rip off their clients by giving them code in an untested tech, the code is almost instantly obsolete while claiming to be cutting edge, and then run away when the flaws in the new framework they've chosen becomes obvious and they can't handle it and the complexity is too much to deal with and they run off and start a new project in the latest koolaid tech, pretending it's not history repeating itself, ad nauseum. Or perhaps, not everyone on the sideline is a Luddite and not everyone jumping from js framework to js framework each year has chronic ADHD that can't see a project through.

I didn't know that all these new Javascript frameworks were making me smart.

by singham 10y ago

I didn't know that all these new Javascript frameworks were making me smart.

SNvD7vEJ 10y ago

So that's why webdevs are so smart!

unusximmortalis 10y ago

Not necessarily smart but trained. Yes, many times I thought about the problems I am solving, and new things I learn from the last 20 something years since I am in love with IT world. There are times when the problems repeat but many times problems are different so my approach and solution is different. Also new tech waves keep me trained cause I want to stay up to date and I want to learn what the new tech is solving or improving.

savanaly 10y ago

You joke, but honestly all the web devs that learn a new framework annually will be pretty good at picking up new frameworks after five or ten years. Of course, most of the people who fret about the state of the javascript ecosystem are doing it needlessly from the sidelines and don't themselves ever learn any of the new stuff.

dualogy 10y ago
> will be pretty good at picking up new frameworks after five or ten years ..or however long until the concept in question becomes irrelevant..
- deleted 10y ago
  [deleted]
jbeja 10y ago
Yeah, I only limit myself to learn stuff that have proven to be useful to me in the js world. For example: Reactjs is the only framework I use because it actually abstract away a lot of recurring patterns and boilerplate that would proliferate without it. TypeScript is another one, since already improved my workflow given the IDE capabilities it provides and having a type system to automatically self document my code is really usefull.
mattmanser 10y ago
Do your clients all have projects that shut down after a year then? One of my clients has 2 projects in durandal that I've picked up. No-one uses it any more, the documentation sucks ass, there's sod all on SO, the original devs had only done data access pages, super easy, not the data editing pages, absolute nightmare, so you can't even copy what they did before. It's a bloody nightmare to work in. Pages which would take me an hour or two in an older tech are taking me days in this half-baked SPA. I'm not on the sidelines because I'm fretting mate, I'm on the sidelines because the messes left behind are a fucking nightmare for those afterwards and an absolute disgrace to the profession. It feels like the framework switchers rip off their clients by giving them code in an untested tech, the code is almost instantly obsolete while claiming to be cutting edge, and then run away when the flaws in the new framework they've chosen becomes obvious and they can't handle it and the complexity is too much to deal with and they run off and start a new project in the latest koolaid tech, pretending it's not history repeating itself, ad nauseum. Or perhaps, not everyone on the sideline is a Luddite and not everyone jumping from js framework to js framework each year has chronic ADHD that can't see a project through.