5 ms·

Could you elaborate more? Your comment doesn't make much sense otherwise - if anything I'd argue that NOT tying yourself to a single framework is what makes you

Could you elaborate more? Your comment doesn't make much sense otherwise - if anything I'd argue that NOT tying yourself to a single framework is what makes you grow into a senior developer. I'd argue that Python (or similar) back-end and JS-flavor front-end is a better path to growing since it's just a much wider area of growth.

revskill 5y ago
Updated my original comment to include my story. Once learning Ruby/RoR techstack, you can jump to all other techstack in NO time as it already taught you everything you need. The rest is ecosystem and syntax. About your concern, other frameworks/languages offer you only part of story, Ruby and RoR offers you complete story in a concise way, it's the difference.
- t-writescode 5y ago
  I would argue that’s anything. I started by web service development career in C# and moved to Python and Rails was easy enough to figure out except for the magic junk. Most systems use similar-enough patterns you can carry them over where-ever. It doesn’t have to be rails, but it was for you.
  - revskill 5y ago
    Because the ease of installation of Ruby, RoR and deployment to Heroku. It's cross-platform. So u can bring your application to production in like 30 mins. In era 2010, .NET stack couldn't offer you that. I wrote about 4 production application in Ruby stack in 6 months, it's super productive and the Ruby language has OOP/FP done right in comparison of other languages, too.
    - t-writescode 5y ago
      I worked in Microsoft shops for the majority of my early career, so cross-platform didn't matter to me. C# had task-based async and a very good, compared to the competition in Java, database framework to work with. Seriously, how doesn't Java have named parameters yet?
    - jeremyjh 5y ago
      The only reason this seems special to you is because its your story. Your story could have happened with a lot of different languages though.
      - regularfry 5y ago
        One part of the story that's probably relevant is that RoR makes getting started with relational databases easy. That can be extremely intimidating otherwise; I meet a lot of juniors who have never touched them and don't know where to start. Because it does cover the full stack, in a way that devs in a conventional enterprise wouldn't ordinarily do, and gives you pretty good hand-holding while you do it, it takes a lot of the fear out of parts that might otherwise look intimidatingly complex.
joelbluminator 5y ago
> if anything I'd argue that NOT tying yourself to a single framework is what makes you grow into a senior developer I disagree. A lot of this discussion is about semantics - what do we mean when we say senior developer? for FAANG they don't really care what languages you know - in fact they don't really seem to care how well you can code, it's all about your ability to solve algorithms under pressure. Is that a senior dev? Guess for them it is. But for smaller startups - where your ability to code well and onboard fast is critical to the team, when they hire a senior they will most often prefer someone familiar with their stack. So to them, a senior (preferably) has deep knowledge in their stack already (or is good enough to get up to speed really quickly).

revskill 5y ago

Updated my original comment to include my story. Once learning Ruby/RoR techstack, you can jump to all other techstack in NO time as it already taught you everything you need. The rest is ecosystem and syntax. About your concern, other frameworks/languages offer you only part of story, Ruby and RoR offers you complete story in a concise way, it's the difference.

t-writescode 5y ago
I would argue that’s anything. I started by web service development career in C# and moved to Python and Rails was easy enough to figure out except for the magic junk. Most systems use similar-enough patterns you can carry them over where-ever. It doesn’t have to be rails, but it was for you.
- revskill 5y ago
  Because the ease of installation of Ruby, RoR and deployment to Heroku. It's cross-platform. So u can bring your application to production in like 30 mins. In era 2010, .NET stack couldn't offer you that. I wrote about 4 production application in Ruby stack in 6 months, it's super productive and the Ruby language has OOP/FP done right in comparison of other languages, too.
  - t-writescode 5y ago
    I worked in Microsoft shops for the majority of my early career, so cross-platform didn't matter to me. C# had task-based async and a very good, compared to the competition in Java, database framework to work with. Seriously, how doesn't Java have named parameters yet?
  - jeremyjh 5y ago
    The only reason this seems special to you is because its your story. Your story could have happened with a lot of different languages though.
    - regularfry 5y ago
      One part of the story that's probably relevant is that RoR makes getting started with relational databases easy. That can be extremely intimidating otherwise; I meet a lot of juniors who have never touched them and don't know where to start. Because it does cover the full stack, in a way that devs in a conventional enterprise wouldn't ordinarily do, and gives you pretty good hand-holding while you do it, it takes a lot of the fear out of parts that might otherwise look intimidatingly complex.

joelbluminator 5y ago

> if anything I'd argue that NOT tying yourself to a single framework is what makes you grow into a senior developer I disagree. A lot of this discussion is about semantics - what do we mean when we say senior developer? for FAANG they don't really care what languages you know - in fact they don't really seem to care how well you can code, it's all about your ability to solve algorithms under pressure. Is that a senior dev? Guess for them it is. But for smaller startups - where your ability to code well and onboard fast is critical to the team, when they hire a senior they will most often prefer someone familiar with their stack. So to them, a senior (preferably) has deep knowledge in their stack already (or is good enough to get up to speed really quickly).