I will say my first reaction to seeing "I'm a rails developer" was to tell you I'm sorry for your loss.
This sort of mindset is something I'm trying to avoid, because at the end of the day the only thing that matters is this.
Does your software solve a problem?
I think we all have some sort of ego when it comes to the software WE use and tend to think of others as not as good, or subpar, it's almost human instinct. The reality is that we should choose whatever makes the most sense for the problem your trying to solve.
This article hits the nail on the head. Software choice is irrelevant if you can't solve a problem with it, and the needs for many startups is quick development and ability to change ships fast. You can worry about things like scalability, testing, etc.. once your business is proven and it is more important for your software to be stable than adding new features.
Hard to tell exactly what your point is, and it seems as though you're contradicting yourself?
Like you're saying your stack choice doesn't matter at first, and then you go on to describe how people choose their stack because it helps them develop quickly and ship changes fast?
Choosing the stack that helps them ship fast and they are comfortable with instead of the stack that will provide the most performance, security, or has the most popularity is the point.
Where is the contradiction? The stack choice not mattering is the exact same thing as saying choose what your good with so you can ship fast instead of worrying about details that don't matter early on like scalability.
"I will say my first reaction to seeing "I'm a rails developer" was to tell you I'm sorry for your loss.
This sort of mindset is something I'm trying to avoid, because at the end of the day the only thing that matters is this."
So you're implying that Ben picked Rails because it's trendy? Like you assume that it's "bad" to "pick a framework you like" and you're implying that you look down upon Ben for being so foolish. Then you go on to say "if the software solves your problem then bingo you're golden" as if this isn't exactly what Ben did by choosing Rails?
Like overall, whatever you're saying just sound self contradictory and confusing. It's as if you're saying "ah ha you're such a fool for picking a framework that is simply trendy, as if you didn't pick Rails because it does solve your software problems."
Dude you good? I explicitly said that I am trying to avoid behavior of looking down on others for the technology choices they make just because those choices are different than my preferences. You are trying to argue on a post that is 2 and half years old that you CLEARLY misunderstood.
So you're implying that Ben picked Rails because it's trendy?
Nope never came close to implying this.
Like you assume that it's "bad" to "pick a framework you like" and you're implying that you look down upon Ben for being so foolish.
I literally said the opposite by stating that this was behavior I am trying to avoid.
Then you go on to say "if the software solves your problem then bingo you're golden" as if this isn't exactly what Ben did by choosing Rails?
The whole point of my comment. Software choice is irrelevant as long as it solves your problem. Of course Ruby isn't able to solve every problem because of how high level it is, but that doesn't mean you shouldn't use it if it solves your problem.
It is honestly like your trying to pick a fight and are intentionally reading the words I'm saying with malice.
I will say my first reaction to seeing "I'm a rails developer" was to tell you I'm sorry for your loss.
This sort of mindset is something I'm trying to avoid, because at the end of the day the only thing that matters is this.
Does your software solve a problem?
I think we all have some sort of ego when it comes to the software WE use and tend to think of others as not as good, or subpar, it's almost human instinct. The reality is that we should choose whatever makes the most sense for the problem your trying to solve.
This article hits the nail on the head. Software choice is irrelevant if you can't solve a problem with it, and the needs for many startups is quick development and ability to change ships fast. You can worry about things like scalability, testing, etc.. once your business is proven and it is more important for your software to be stable than adding new features.
Hard to tell exactly what your point is, and it seems as though you're contradicting yourself?
Like you're saying your stack choice doesn't matter at first, and then you go on to describe how people choose their stack because it helps them develop quickly and ship changes fast?
Choosing the stack that helps them ship fast and they are comfortable with instead of the stack that will provide the most performance, security, or has the most popularity is the point.
Where is the contradiction? The stack choice not mattering is the exact same thing as saying choose what your good with so you can ship fast instead of worrying about details that don't matter early on like scalability.
"I will say my first reaction to seeing "I'm a rails developer" was to tell you I'm sorry for your loss.
This sort of mindset is something I'm trying to avoid, because at the end of the day the only thing that matters is this."
So you're implying that Ben picked Rails because it's trendy? Like you assume that it's "bad" to "pick a framework you like" and you're implying that you look down upon Ben for being so foolish. Then you go on to say "if the software solves your problem then bingo you're golden" as if this isn't exactly what Ben did by choosing Rails?
Like overall, whatever you're saying just sound self contradictory and confusing. It's as if you're saying "ah ha you're such a fool for picking a framework that is simply trendy, as if you didn't pick Rails because it does solve your software problems."
Dude you good? I explicitly said that I am trying to avoid behavior of looking down on others for the technology choices they make just because those choices are different than my preferences. You are trying to argue on a post that is 2 and half years old that you CLEARLY misunderstood.
Nope never came close to implying this.
I literally said the opposite by stating that this was behavior I am trying to avoid.
The whole point of my comment. Software choice is irrelevant as long as it solves your problem. Of course Ruby isn't able to solve every problem because of how high level it is, but that doesn't mean you shouldn't use it if it solves your problem.
It is honestly like your trying to pick a fight and are intentionally reading the words I'm saying with malice.
I see your point now, but you didn't state it very clearly at first.
Lol, I'm not trying to start a fight, I'm just trying to understand what you were saying, which was very confusing.