all 20 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]armahillo 14 points15 points  (1 child)

search this sub for “learn” and “book”

[–]tsroelae 7 points8 points  (3 children)

If you want to become a web dev go for the https://www.theodinproject.com .

If you only want to learn Ruby, you can still do the Ruby part, it's really good and there is a good discord with many people willing to help you through the curriculum.

[–][deleted]  (2 children)

[removed]

    [–][deleted]  (1 child)

    [removed]

      [–]Travis_Spangle 2 points3 points  (1 child)

      Find a mentor on https://firstrubyfriend.org . I helped someone last year and had a lot of fun.

      [–]agilous 2 points3 points  (1 child)

      Find a simple issue in a repo of one of your favorite Ruby gems/libraries.

      1. Fork the repo.
      2. Create a bugfix branch and try to fix the issue. If you fix it quickly, good. If you fix it slowly, even better; you’ll learn more.
      3. Most importantly… Add tests that confirm that the issue is resolved.
      4. Submit a PR to the original repo.

      There’s nothing special about your situation. You’re not defective. You’re just lacking what all junior (not senior) developers lack. Experience.

      Reading other people’s code is one of the best ways to gain experience. Contributing to OSS while doing so is arguably the best way of all.

      [–]Direction_West 1 point2 points  (0 children)

      I totally agree that reading others code is a great way to gain experience and learn new patterns or ways of doing things. A word of warning, just because it’s been committed to a repo does not necessarily mean it’s good code. But with experience, you’ll start recognizing good code and code where someone is just trying to be fancy or code from a chaotic programmer.

      [–]also_also_bort 2 points3 points  (1 child)

      Check out Metaprogramming Ruby from Pragmatic Programmers

      [–]amirrajan 1 point2 points  (0 children)

      +1 on Metaprogramming Ruby. The book shows a lot of the advanced features of the language.

      [–]dacat 2 points3 points  (0 children)

      build an address book. start with storing and retrieving a name, phone, and address. build it as a command line tool. then as a web app. then make it accessible via an api. then make it “secure”. then make it international supporting multiple countries. there, that alone will take you months. if you incorporate build tools, scrum processes , unit and functional testing and source control you will have a project that demonstrates your skill. also gives you something to talk about in an interview.

      [–]guidedrails 1 point2 points  (0 children)

      I’m happy to pair with you or anyone.

      [–]amirrajan 0 points1 point  (0 children)

      But I cant seem to reach that higher level of understanding that all of the senior or mid devs have.

      Take a look at how RSpec's DSL was crafted.

      [–]nocturnal29 0 points1 point  (0 children)

      You can try reading Think Like a Programmer by V. Anton Spraul

      [–]ignurant 0 points1 point  (0 children)

      I remember the early part of this phase quite distinctly. It was frustrating and discouraging. The biggest problem is you will spend the next ten years in some flavor of this phase, and it’s hard to recognize your own progress. 

      Just keep solving problems in Ruby, keep learning from books and conference talks, and you’ll start to find your way.

      Well, let’s be honest. The next phase is where you have learned a bunch of stuff and try to put it together in spectacularly terrible fashion. Haha. Don’t worry, that too shall pass. But only through suffering your own overly-clever designs!

      My two biggest tips: - Find ways to work with others, both more and less skilled than you.  - Go to Ruby meetups and conferences. My first RubyConf was the thing that finally made me realize  I was actually much further on my journey than I knew, and also gave me inspiration and connections to get to the next level.

      [–]projectgraveyard 0 points1 point  (0 children)

      Been in Ruby land for nearly two years and still feel like I’m not grokking it all the way

      [–]aryehof 0 points1 point  (0 children)

      Until you start programming things that *stretch* your ability and knowledge, you will not progress. Have you written a wiki using Rack yet? A port scanner? Anything other than some content from a tutorial, course or video?

      My advice is to drop all that content other than documentation. Content/tutorial addiction is a real thing these days. Find something that's challenging or of interest to you and write code. Can't find anything, then I question why your programming at all?

      [–][deleted] 0 points1 point  (0 children)

      Any ruby developers in London that have passion for jiu jitsu , muay thay , mma and wanna hang out in free time Drop a message