@JimmyCsaid

Ok, here’s a noob problem that no one has really explained clearly online. Those of you who are configuring your Selenium webdriver to test Angular apps using Protractor the first time will run into this issue.

You have a config.js file which contains your configuration. It looks like this according to Protractor Setup.

// conf.js exports.config = { framework: 'jasmine', seleniumAddress: 'http://localhost:4444/wd/hub', specs: ['spec.js'] baseUrl: 'http://example.com', }

Here, the baseUrl sets the base URL to use in your tests so that you may just write something like this in your tests.

`browser.driver.get(browser.baseUrl + '/')

or

`browser.driver.get(browser.baseUrl + ’/user’)

One of the new features that Apple briefly mentioned in passing at WWDC 2014 is that Siri can be always listening for commands if plugged in. I find it surprising why this is not talked about more in the blogosphere or in the media. At first glance, it seems trivial to bring this to an iPhone as probably the only place you'll use it is inside a car but this starts to make much more sense if you think of it in terms of Apple TV.

One Month Rails: Learn to Code Rails, in 30 minutes a day.

One month rails profiled me in their blog yesterday. To be honest, I took the online class a bit longer than a year ago.  It also doesn't take a month. I think I did it in less than a week.

Mattan's course was one of the first that gave me a great macro picture of developing a web app from scratch.  I would recommend anyone who's interested in learning rails to check it out.

Aparajita Fishman recently release SublimeLinter 3 which finally brings this fantastic linter to people who were using the old version with Sublime Text 3.  Perviously, you had to manually install SublimeLinter 2, jury-rig it to work.  Even then it was a bit buggy. I’m happy to say, after using it for the past two days, that the new Linter works fantastically with Sublime 3.

The big difference between the new SublimeLinter 3 and the old version is you now have to install the linters you specifically want whereas the old had most of the major ones built-in.

I recently read a blog post by Michael Wolfe which struck me as a fairly accurate description of what happens when you work on software development projects.

For those who are seasoned developers, this is familiar territory, but something you learn to minimize by having detailed build requirements.  Unfortunately, this also happens most often when you speak to non technical people about developing their projects.  They typically focus too much on the end product and not how or what it takes to get there.

What looks simple to implement many times turns out to be really difficult or vice versa. Experience certainly helps in narrowing the margins but more often than not, there will be unforeseen roadblocks that will slow down the project.

Managing non technical people's expectations about their project buildout becomes of paramount importance in maintaining a positive outcome.  It's also important for the developer to know his or her limitations - be honest about what you know how to do vs. what you still need to learn.

All of this leads to the fact that estimating the time required for software development is a nebulous process that is often difficult to accurately predict.

You ever run into problems with your code development that's just a pita to debug?  Well, I ran into a big one yesterday. I spent hours searching for a solution.

It seems that when using Devise with Rails 4, you could run into problems where you get this long error that looks something like this whenever you try to rake:

rake aborted! Rails::Application::RoutesReloader#execute_if_updated delegated to updater.execute_if_updated, but updater is nil: #<Rails::Application::RoutesReloader:0x007f85bd181060 @paths=["/Users/Mac/rails_projects/limolot/config/routes.rb"], @route_sets=[#<ActionDispatch::Routing::RouteSet:0x007f85bd119488>]> /Users/Mac/.rvm/gems/ruby-2.0.0-p247@limolot/gems/railties-4.0.0/lib/rails/application/routes_reloader.rb:10:in `rescue in execute_if_updated' /Users/Mac/.rvm/gems/ruby-2.0.0-p247@limolot/gems/railties-4.0.0/lib/rails/application/routes_reloader.rb:6:in `execute_if_updated' /Users/Mac/.rvm/gems/ruby-2.0.0-p247@limolot/gems/railties-4.0.0/lib/rails/application/finisher.rb:69:in `block in <module:Finisher> ...

So what the heck is that? This is a long running problem that stretches all the way back to earlier this year when Rails 4 was released. It's supposed to be fixed by Devise 3.1.0 but for some reason it still rears its ugly head.

In my case, it was when I was transferring some code from one app to another.  I tried all sorts of things to try to fix the problem. This included reinstalling Devise and regenerating the User class. But what I discovered to be a simple fix was to leave whatever devise generated code in the user.rb alone, undisturbed, on the top of the page and to write your code below it.  That seems to have worked in my case.  Just to clear, here's what the user.rb file in your model folder should look like:

class User < ActiveRecord::Base # Include default devise modules. Others available are: # :confirmable, :lockable, :timeoutable and :omniauthable devise :database_authenticatable, :registerable, :recoverable, :rememberable, :trackable, :validatable ^^^LEAVE THAT JUNK ABOVE ALONE^^^ ***PUT YOUR CODE HERE*** end

Unlike many developers I upgraded my Mac as soon as Mavericks came out.  I also went ahead and updated Xcode to 5.0.1 and installed the current Command Line Tool using the command

$ Xcode-select --install

Even though before these updates my development environment was operating perfectly, updating broke my Git and Homebrew.  Mostly it's permissions that gets changed so that you're no longer able to make the necessary changes to your Homebrew formulas especially Git.

When I tried,

$ brew upgrade git

I would get a bunch of error messages and then something about brew not being able to symlink the Git.

Normally, Homebrew installs it's symlinks in the folder

/usr/local/opt

and the actual Git in the folder.

/usr/local/Cellar/git/

But after the upgrade, my Git was no longer symlinked to the correct folder.

If I run

$ which git

it would point to

/usr/bin/git

and if I run

$ git --version

it would tell me 

$ git version 1.8.3.4 (Apple Git-47)

This clearly is NOT Homebrew's version.  This is Xcode and CLT version. So, what to do?

First, I checked the Git symlink in the folder

/usr/local/opt

by typing

$ cd /usr/local/opt

Then typing the command

$ git

I see that it's no longer a symlink but a folder. Somehow, the upgrade has turned my symlink into a folder. Trying to delete this Git folder would only return Permission Denied. So I used

$ sudo rm -rf git

to forcibly remove the folder.

I then tried to 

$ brew rm git

and again it returned an error:

Uninstalling /usr/local/Cellar/git/1.8.4... Error: Permission denied - /usr/local/Cellar/git/1.8.4/share/git-gui/lib/Git Gui.app

It seems that the permissions for that

/usr/local/Cellar/git

folder was changed as well with the upgrade. I then tried to forcibly delete that folder  by running

$ sudo rm -rf /usr/local/Cellar/git

That will then free up that space for brew to reinstall git.  Now, running

$ brew install git

I still get permission denied in the folder 

/usr/local/share/git-gui/lib/

So run

$ sudo chmod 775 /usr/local/share/git-gui/lib

That will change the permission so that Homebrew can finally install git. Finally,

$ brew install git

That should do it. Now when you run

$ which git

it should show git installed in the correct Homebrew directory 

/usr/local/bin/git

and checking on the version

$ git --version

should show the current version

$ git version 1.8.4.2

The big announcement yesterday was that after many years of complaints from users, they finally brought IMAP support for Outlook and Hotmail accounts.

However, there's been some confusion as to how best to set it up. I've looked at quite a few versions of how to get Mac Mail set up to work with the new IMAP.  Here's how I did it.

Open Mac Mail

From the File menu, chose Preferences, then click on Accounts

Click on the + on the lower left to add a new account

Type in what you want your emails to show as your name

Type in your full email address, example@hotmail or example@outlook

This next step is important.  Leave the password field blank and click Continue, the mail program will try to log into your POP account but will fail.  Just click Continue again.

Now you get to configure the incoming server.

Account Type: IMAP

Description: Outlook, or whatever you want

Incoming Mail Server: imap-mail.outlook.com

User Name: your full email address, i.e. [email protected]

Password: your password for the account

Click Continue

For Incoming Mail Security make sure to check on the Use SSL

Authentication: Password

Click Continue

Now to configure the outgoing server.

Description: Outlook, or whatever you want

Outgoing Mail Server: smtp-mail.outlook.com

Check on Use only this server

Check on Use Authentication

User Name: your full email address, i.e. [email protected]

Password: your password for the account

Click Continue

You'll now see an account summary of the above settings. Make sure it's correct.  If not you can click Go Back to any of the proceeding pages and adjust.  When you're done click on Take account online and Create.