My configuration for bash, vim, git, tmux and a few other tools can be found on GitHub now.
I have spent a considerable amount of time to get them working on OS X and Linux.
(Tested on Mac OS X Yosemite 10.10.3 and Debian 7.8 – YMMV!)
Whenever I start a new project, I struggle with what to put in the very first commit message. After doing a “git init” there is technically nothing there and no work done yet, so how to describe this initial step?
“Initial commit” always seemed a little futile, so I started gathering some better examples on what to put in the message for the glorious start of a new project and I am sharing them here for all of you to marvel at:
This is where it all begins...
Version control is awful
COMMIT ALL THE FILES!
The same thing we do every night, Pinky - try to take over the world!
Lock S-foils in attack position
This commit is a lie
I'll explain when you're older!
Here be Dragons
Reinventing the wheel. Again.
This is not the commit message you are looking for
Batman! (this commit has no parents)
Or, you know, just use whatthecommit.com.
I’m always happy for comments with further ideas and will be adding to this list constantly.
The year 2014 is almost over, but looking around my developer colleagues, I see that there is still a lot of old knowledge and outdated techniques for using your Mac for (web-) development purposes. To counter this lack of information I will outline the steps I took to lift my two primary OS X systems into the new age. Gone are the days where we need to have a webserver, database system and a plethora of different packages installed on our main operating system and deal with breaking changes whenever a new OS update (Hello Yosemite!) comes along.
I will construct these informations into a series of posts each dealing with an enclosed subset of principles. This is Part 1 and talks about setting up your own private local development server with all the needed software to start developing applications with PHP and MySQL without having to install any server software on your main operating system. The end product will also give you the means to quickly set up an identical virtual machine on any number of additional computers you might want to use for your development.
Disclaimer: As I am a heavy user of Laravel these days, this set-up will mainly center around web development and PHP.
phantsy is all about places.
phollow likeminded people that have the same taste and interests, add new places or rate existing ones in order to create your personal collection of favourite places. also keep in mind: the more places you rate, the more likeminded people and recommendations phantsy can find for you! explore a trusted world. we phantsy that.
Give it a try. I’m happy about any feedback you can offer!
If an object is converted to an array, the result is an array whose elements are the object‘s properties. The keys are the member variable names, with a few notable exceptions: private variables have the class name prepended to the variable name; protected variables have a ‘*’ prepended to the variable name. These prepended values have null bytes on either side. This can result in some unexpected behaviour.
No kidding? This must be one of the most stupid decisions ever in the whole language of PHP. Why pad some array keys with NULL BYTES? I mean, how can anyone ever be expected to find that out, by looking at the data the script writes out? This makes absolutely no sense whatsoever.
Just spent around an hour hunting this down!
I hope this post will save someone else the amount of hassle this has caused me.