Even though I may not be writing about it, I am continuing my deep-dive into the word of Ruby. At work I am mostly focused on Rails. My app is Rails, and the tickets I am working on are Rails (with some haml and scss thrown in, yay for learning some front-end development!). Currently I have been able to be become semi-productive, but haven’t been able to complete a ticket on my own, which is a humbling experience. We are doing one week sprints, so I do try to muddle my way through on an assigned ticket. But since time is short, you need to just women up and ask for help sooner then later. When time allows, I am still working through a Rails Tutorial.
At night, I have still been working through Ruby the Hard Way and have made it up to exercise 15 or so. These have been very easy so far, but I have a feeling that it will pick up speed soon and I don’t want to skip something that might be important. Got derailed this week because one of the lessons is working on accepting user input, and suggested looking up Zork, so the rest of my evening was playing that. It kinda reminds me of Vim, if you can remember the keywords it can be fun, but if not you are just kinda stuck in a dark room (terminal).
In other fun news, I actually have people visiting my website! Um thanks, I really didn’t know that anyone would read this, and with my handy dashboard on Flyweel I can see that I have visitors. Now what percentage of those are spam bots, who knows ¯_(ツ)_/¯
Side note: if anyone knows why when I run my rails server I get “MiniProfiler storage failure: Connection lost (ECONNRESET)” every once in awhile, could they share, that would be awesome. Everything starts up and runs, but I just see that pop up pretty often.
Top comments (6)
Hi Christine, thanks for the update!
I think being derailed is perfectly normal, one can't be in the zone constantly :-D
I googled the error a bit but I didn't find a clear answer, I have a question though: why are you using a profiler on production :) ?
This is just my local dev environment that is running into the issue. I believe the profiler is just used in my local procfile for foreman.
Oh! Sorry I thought you had the issue on your actual blog :-)
The fact is not an error you can generate on command makes it harder to debug but you should probably wait for the next crash (I know :D) and then open an issue to rack-mini-profiler with the traceback, which I assume is logged on the console.
Does it make sense?
Yep, thanks to the advice.
As a Java developer learning Ruby and Rails, I really enjoy your updates! I went through Learn Ruby the Hard Way for a bit, but I was kind of impatient with it. I started doing the Ruby courses on The Odin Project, which led me to Codecademy. I found that interactive style of learning really fun and effective.
Soon I'm going to be in the same boat of muddling through tasks I only partially know how to complete. It'll get a little bit easier every sprint I bet! :)
I totally get being impatient with Learn Ruby the Hard Way, I am on exercise 18 and am starting to feel that way. But I do also like how small each to the lessons are, and I can decide to do 1-3 at night, depending on how motivated I am. I'll have to check out Odin Project, and Codeacdamy.