3 ms·

Bypassing visual builders in favor of code is not a new idea! It happened as well with .Net and VisualStudio; I used to be a heavy WinForm developer (including

Bypassing visual builders in favor of code is not a new idea! It happened as well with .Net and VisualStudio; I used to be a heavy WinForm developer (including visual tools). At some point being able to do everything programmatically proved to be really interesting in my use cases (and on other people projects, too). Not everyone is going to adopt CSS and Pixate, and people are using RubyMotion without Pixate, too. As for the Rails community, pure iOS people are also interested in RubyMotion (based on my exchanges with developers, that is). In the end, there is no such thing as lack of respect or bad influence. New tools get created, people pick what works for them. People using Rails used other platforms before and will use other platforms later. I'll end with an advice to (new?) programmers: don't let fear (of being replaced) choose your skills and tools for you.

flatline3 14y ago
> I'll end with an advice to (new?) programmers: don't let fear (of being replaced) choose your skills and tools for you. I'm more concerned about propagation of bad ideas. The current job market and VC climate has given extremely junior engineers a voice grossly disproportionate to their skill, wisdom, or experience. In a more healthy job market, those engineers would be hired into junior positions apprenticed to senior engineers. In the current job market, inexperienced engineers are given carte blanche, and this shifts the industry. Not all shifts are a net positive. It was with great dismay that I observed the rise of the Rails community, and I find it exceedingly disturbing to see their anti-intellectual, anti-experience, anti-computer-science approaches extending outside their initial realm of influence.