I would think just starting out is the perfect time to switch over to Python / Node / whatever... you've got your head around the concepts of MVC, object-oriented programming, etc, but haven't settled into a routine about how to use your particular language and framework. Once you're specialized, switching costs only grow.

Plus, if you hire a bootcamp grad, you're probably going to have to do lots of on-the-job training anyway. Good time to indoctrinate the candidate with the "right" way to do things in your particular codebase.

Maybe.. I only have the "Worked with one language for a couple years before switching" experience, and not the other. I feel like when I learn other languages having had a strong fundamental in other ones is what makes it possible for me to know what I'm looking for and get up to speed. I worry that switching super early in your learning process would make learning the fundamentals slower, but I'm probably not qualified to say.

All of that said, I think there are plenty of rails shops and if you're from one of these camps you'll likely feel more confident & productive right away and your confidence and ability to ask the right questions will be paramount in your success in a first-coding position I think... so my advice would likely be to still maximize for your current strengths and try to stay in your burgeoning wheelhouse.

How is this different from Raptr.com ?

I came here to ask the same thing.

I wrote my own, and opened it for other people to use.

https://jekyllhub.com

Can you email me? I'd like to chat about blogging. andrew@atevans.com

Cheers,

Developer of https://jekyllhub.com here. I think Jekyll might be over-complicated for what Ghost is going for. WordPress and the hypothetical Ghost seem to target the mass-market; Jekyll is mostly about power features. Easy integration with git via the filesystem, code highlighting with pygments, configuration with yaml... most people really wouldn't care about that kind of stuff.

Hey - I'm making a thing called https://jekyllhub.com - it's designed to take the pain our of Jekyll and get you blogging quickly and easily. I'd love to get your feedback on it. If you send me your email, I can make you a free lifetime account: andrew@atevans.com

Cheers!

Sorry about that! Looks like there was a hole in our Github auth flow if you don't have an email set. Should be fixed now. Or if it's something else, at least it should show you an error message.

Happy blogging!

Developer of Jekyllhub here: we're giving out free lifetime accounts in exchange for some feedback on the site. Bug reports, praise, hate, anything (though preferably something constructive). Once you're signed in, just hit the "feedback" form on the left and send something my way.

Happy Blogging!

Cross-posted from our Facebook Timeline:

Jekyllhub is based on Jekyll, which is a static site generator. The idea is that you have 100% control over the blog just by editing files - you can see all the raw files used to make your site under the "files" section of the sidebar. You can read more about how to use Jekyll here: (https://github.com/mojombo/jekyll/wiki/Usage)

If you're using one of the default templates, all the navigation links are in the file "_includes/links" - there's an example link provided, and you can add any other links you want (or nested links, or images, or anything else via HTML).

I'm still considering the right way to automatically add links, comment systems, or other add-ons like Google Analytics while still giving users all the code to their sites, but rest assured it's on the roadmap. Thanks for the feedback and suggestions, and happy blogging!

Thanks for the quick response. This has tons of potential and I'm real happy things are on the roadmap. Can't wait!

As I mentioned, and I may be wrong, but people interested in this service will most likely be people like me: They're aware of Jekyll but aren't familiar with it. They want the clean post syntax, syntax highlighting and light footprint, but they also want the comfort of managed hosting for it.

That link you provided for Jekyll usage is key, I'll have to read it. Maybe you can show it to new users so they too can easily find it.

Developer of Jekyllhub here: our SSL cert is trusted by every other browser; only Mozilla seems to have a problem with them. I'm working it out with my provider, and if nothing else I'll get a new cert this weekend.

Thanks for your feedback!

Thx for the reply. I've seen the warning on Chrome for Android. On Win there was no problem.

Chrome on an iPad is also showing the red SSL warning page.

Both Chrome and the native browser balk at it on Android.

script/runner does not have the app.get facility. That's only available in script/console.

app.get is using the same facility as integration testing (https://github.com/rails/rails/blob/master/actionpack/lib/ac...).

Check out the code that instantiates it at https://github.com/rails/rails/blob/master/railties/lib/rail...

I needed this in a rake task under Rails 2 a while back; I ended up doing the following:

  require 'action_controller/integration'
  app = ActionController::Integration::Session.new

  module CurrentUserHack
    def current_user 
      @user ||= User.look_up_my_user_here
    end
  end
  ApplicationController.send :include, CurrentUserHack

Now you can make authenticated requests in rake tasks and presumably in script/runner.