The other day while going through my rss feeds, I came across 56 Experts reveal 3 beloved front-end development tools. For some reason I found this really interesting. The premise was that 56 of some of the top names in front-end development were asked:

If you could only use 3 front-end development tools, which 3 tools would you choose?

That's a really great question with all of the vast amounts of front-end tools available today, which ones can't you live without?

If I had to choose just 3 I'd go with:

jQuery

I don't think I'd want to do front-end development without jQuery. It just does so much for me to make my life easier. I know a lot of developers are going vanilla JavaScript as the browsers have advanced a lot over the years. But for me the ease and simplicity of the API is to much not to ignore.

jQuery Home page


Developer Tools

I don't care which browser either because they all have the basics that I need. A element inspector, JS debugger and a console are probably the bare minimum needed to develop on the front end. Chrome Developer Tools, IE F12 Dev Tools, FireBug are all really good in my opinion. I've been really surprised to at the new FireFox and Safari Tools.

IE F12 Developer Tools


Git

It's funny how you don't think of a version control system is needed in a front-end project but I can't think of a time I didn't use Git with a remote to Github to start a project. Git with github allows for so many possibilities. Obviously it makes collaboration much easier, but if you have it configured correctly you can deploy by just pushing your master branch up to github. It makes deploying super simple to do.

Git

So what are your 3 front-end development tools you'd choose if you could only have 3?

Camille Fournier Velocity NY 2014 Keynote: "Cloning Yourself Isn't an Option..."

Published: September 16, 2014

Originally linked from Lindsay Holmwood's blog post "It's not a promotion - it's a career change"

I've been having this problem for a couple of months everytime I went to https://github.com I would get a SSL Certificate was expired error. I only encountered this error in Google Chrome on a Mac. I did not have this problem in any other browser like Firefox or Safari.

I could not figure how to fix it. I tried uninstalling/reinstalling Chrome. Uninstalling all extensions. Nothing worked.

I started to notice the problem on more and more sites since the initial github issue surfaced. So I finally had to do some research.

I finally found a blog post on the Digicert website that acknowledges the problem:

On July 26,2014 at 12:15 PM, some customers and users on sites secured by DigiCert reported that they were getting an untrusted certificate error.

The problem is related to a locally installed legacy intermediate certificate that is no longer used and no longer required for the certificate installation. The problem can affect any client platform with a locally cached or installed intermediate certificate.

Digicert confirmed the problem existed in:

  • Clients (mainly OS X) with the expired intermediate installed in their local keychain.
  • Server-to-server connections on Windows environments, where one server still has the legacy certificate installed.

Here is a description of the problem:

Expired Legacy Intermediate Certificate

The expired certificate in question is the “DigiCert High Assurance EV Root CA” [Expiration July 26, 2014] certificate. This temporary intermediate certificate was used in years past as part of a compatibility chain for older devices.

This certificate has not been used for over three years and is unnecessary for installations.

For instructions on removing the expired certification go to the digicert blog post and follow the instructions. Once I removed the certificate from the Keychain access I was able to go to sites normally again.