ev_rolfe

I don't think that the average person taking an introductory program course has any interest in calculating the sum of squares or fibonacci numbers. May be alright for MIT students in 1986 but in 2017 people want to know how websites and phone apps work.

I don't think this is something which can be solved by some "killer algorithm".

It seems that this whole fake-news thing is largely because of hacker news-ey type people wanting to use algorithms to make everything better and introducing them into as many aspects of our lives as they can.

Maybe then the solution isn't more algorithms to fix what the existing algorithms are doing wrong but changing the culture of news sources to encourage more stringent journalistic standards? This would require a lot of hard work amongst many people in influential position but most problems are not solved by coming up with the right code.

Don't really have anything to add, just wanted to say this is a very good point.

In short, yes its still worth it, Rails is a mature and fully-fledged framework which is not going away anytime soon. From a business perspective there is no shortage of rails work to be had.

Anecdotally, I'm also seeing more and more traditional organisations move from "corporate world" frameworks (Java, .NET etc.) to RoR because they are seeing how fast smaller companies and startups that use RoR are able to get things done. Probably also a side effect of how much people from the startup world like to brag about how much they can "get done".

Though as a result of people seeing how fast you can get things done in rails, I've seen a lot of really poorly coded rails sites which does hinder progress. However I think that is an inevitable outcome of any good framework - if you make it easy to get the boring work done then that will have two effects:

1. it allows good developers to skip over boring or repetitive work and focus their efforts on hard problems.

2. it allows inexperienced or just plain bad developers to churn out applications which may get the job done but the code will be a mess.

So yes if you enjoy coding in RoR then I see no reason not to stick with it. However I'd suggest you pick one language/framework and stick with it. This might not be an opinion appreciated by the hacker news crowd but the reality of getting work as a freelancer is that most managers or potential clients will be more impressed if you can say "5 years experience with Ruby on Rails" rather than "5 years experience as a programmer - working with Go, Rust, Node.JS, Ruby on Rails".

Am I the only one here who thinks that this post was written by somebody < 12 years old?

"matrix way"?

"insert chip and boom you get expert"??

"one of my girlfrieds"

How many girlfriends do you have? ;)

"I start my day at 4am"

What time do you go to sleep at to make starting work a 4am feasible?

While its definitely true that corporate companies and startup-ey companies each have their pros and cons, what really gets me is the holier-than-thou attitude that seems to be at the core of modern startup culture.

I mean how often do you hear somebody saying that you should "quit their startup job to come work in the corporate world"? On HN for example, there is a pervasive view that the ultimate nirvana for anyone's life is to do your own startup or "side-project".

That said I'm not saying you shouldn't do a startup if you want to or that they are even a bad thing. Larger organisations, especially in the IT industry, have definitely benefited from some of the practices made popular by startups. Just don't try and tell me that working in a startup will be in any way more enjoyable than working for a corporation. It will be for some people, but I'd argue not most people and certainly not all.

I think its worth noting that the majority of the people posting their salary here seem to be quite successful so I'd take these response with a grain of salt.

Seems likely that people who are successful will be more willing to post their earnings then people who are not!

This really reminds me of a certain film in which Steve Carell is the main character..

I agree with the reasoning behind this description, but would like to add a couple points:

* Junior developer - Will produce some value with guidance, probably not much if left alone. Code will be terrible if left alone.

* Intermediate developer - Will produce value if left alone, but will write code in a way to just "make it work"

* Senior developer - Will produce value if left alone, but will write code considering the long term implications of whats been done. Is it maintanable? Is it easy to read? Is it easy to extend?