5 things every developer should learn from Rails

I spent the last few weeks working on a Rails project. Although there was a lot to learn, I feel as though I have a decent understanding of Ruby and Rails at this point. I am by no means an expert, but I can do the basics without googling. I figured I would document my thoughts on what every developer should learn from the Rails framework. Gems - Having a package manager to to handle dependencies rocks. »

A better Start-Job cmdlet

With Powershell 2, the Start-Job command was added, which allows statements to be executed in the background. There are a few oddities regarding script blocks that need to be understood first though. Powershell doesn’t support closures The current working directory isn’t preserved I confronted these issues first hand today while working with a Rails app. I wanted to execute ruby script\server in a job, but it wasn’t working. PS C:\Users\Brian\workspace\myapp> start-job { ruby script\server } Id Name State HasMoreData Location Command -- ---- ----- ----------- -------- ------- 3 Job3 Running True localhost ruby script\server PS C:\Users\Brian\workspace\myapp> receive-job 3 C:\Ruby19\bin\ruby.exe: No such file or directory -- script/server (LoadError) + CategoryInfo : NotSpecified: (C:\Ruby19\bin\r...ver (LoadError):String) [], RemoteException + FullyQualifiedErrorId : NativeCommandError For some reason, when executing the job, it is executing in a different working directory. »