I see a huge part of the problem coming from a culture of rapidity around new tech adoption. Most craft oriented occupations are able to sit on a very stable base of technique, however the environment and culture among software devs seems to be constant wheel re-invention. This is due in large part to a very real market for novel meta-solutions: a market that is made relevant through the articulation of problems that, while real, are inflated to hype a new product. Enter Twitter and the blogosphere and you have ricochet engine that crowns rising stars and declares viable technology obsolete at a breathless pace.
In many ways we are falling victim to a postmodernist ideology where most of our internally facing energies are dedicating to dismantling and critiquing the existing paradigms. I would challenge that the solution here is to return to the kitsch classics, to exercise the skills we know and love, and to find joy in ancestral craftsmanship (vanilla JS?) rather than cutting our teeth on the newest thing and getting lost in a forest of meta-solutions.
Which is also to say, Ruby on Rails isn't dead like Nietzsche's God.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I see a huge part of the problem coming from a culture of rapidity around new tech adoption. Most craft oriented occupations are able to sit on a very stable base of technique, however the environment and culture among software devs seems to be constant wheel re-invention. This is due in large part to a very real market for novel meta-solutions: a market that is made relevant through the articulation of problems that, while real, are inflated to hype a new product. Enter Twitter and the blogosphere and you have ricochet engine that crowns rising stars and declares viable technology obsolete at a breathless pace.
In many ways we are falling victim to a postmodernist ideology where most of our internally facing energies are dedicating to dismantling and critiquing the existing paradigms. I would challenge that the solution here is to return to the kitsch classics, to exercise the skills we know and love, and to find joy in ancestral craftsmanship (vanilla JS?) rather than cutting our teeth on the newest thing and getting lost in a forest of meta-solutions.
Which is also to say, Ruby on Rails isn't dead like Nietzsche's God.