One of the great things about going to camps is getting exposed to new technologies and to what the others are using. I have never been to a camp where I don't walk away with some new tool for my toolbelt. Whether it's perfomance, coding, front end or backend tips and tricks, there is always something new to be learned at camps, which is why I am always motivated to go.
I love technology. I love keeping up with the latest trends out there and staying as close as possible to the bleeding edge, but how often do you find yourself working on a project that is UX rich and heavy on new technologies. Let's face it a project that needs Parallax, Responsive Web Design, Isotopes, FlexSlide slideshows, jQuery scripts, jCarousel sliders all while maintaining a minimalistic corporate look?
Well think of it as the Canadian alternative to http://openpublicapp.com/
I stumbled upon it about 6 weeks ago, give or take. It sounded cool so I added it to my "Things to investigate when time allows" list.
Boy do I regret not having the time to do this sooner. It was such a rewarding experience.
If you develop locally, like I do, chances are you need multiple virtual hosts running on your stack. There are a number of options out there. Some are elegant and advanced like Puppet + Vagrant, other are simple and quick like XAMPP. I use XAMPP whenever I can't or won't do native LAMPP stacks (or MAMPP) if nothing else for it's versatility and consistency across platforms.
As professional developers, quality is one of our prime directives. In order to assure quality, developers need to run through a list of checkpoints, some of which we tend to forget or ignore because of time constraints. In order to avoid forgetting these items I have written them out in this quick blog post.
I had a lot of trouble upgrading my XAMPP to run the latest PHP. So much so, that I decided to document what I did.
First off, I downloaded the Mac version of XAMPP available from Apache Friends. I probably could use OS X’s built-in Apache server, but XAMPP is portable and in order to keep things consistent from platform to platform I tend to like it better. Make sure you disable Apache by unchecking the “Web Sharing” option of the “Sharing” system preference pane.
I keep forgetting about this so I will make a post and hope I don't forget anymore.
I had a new client who wanted to host with GoDaddy.com
I tried to tweak the php.ini settings but it wasn't working. After banging my head against the desk for a couple of minutes I recalled that what they call root folder is actually that html folder on your root.
So if your account name is boombastic your php.ini file should be located at /home/content/b/o/o/boombastic/html/php5.ini
php.ini and php5.ini will both work, but if you're using php5 you should specify php5.ini