When it comes to finding freelance development work, Freelancer.com seems to be the best choice out there. I have had pretty good success with it, despite the fact I keep getting undercut by outsource operations willing to build whole websites for $100.
One thing that really bothers me about Freelancer.com is the fact withdrawals are broken.
The first frustrating thing for new time users is the fact your first withdrawal is held for two weeks. This is presumably a security thing and subsequent withdrawals you do not have to wait to be processed. I can kind of understand this, but wouldn’t it be easier and more secure to ask users to just confirm their identities instead of holding the funds for a made-up period of time?
This is something I have been wanting to do for a while now, but like many, have not had the time. Someone has created a WordPress Plugin boilerplate which gives you a nice little start when creating a WordPress plugin.
As anyone who has modified an existing plugin or created their own plugin for WordPress knows, there is no right or wrong way to do it. You can write it solely procedurally, object oriented or you can intertwine and mix both. The result is never pretty and I have seen a lot of bad plugins out there.
I wouldn’t really call them proper PSD’s, but Apple has released a Photoshop PSD files for its latest models of iPhone, the iPhone 6 and iPhone 6 Plus.
If you just need some simplistic images of the devices to add in marketing shots, that is all you will be able to do with them. They’re more for mockups than they are proper development as Apple doesn’t want people moving other elements around, presumably to keep integrity in the design intact or something like that.
This is an interesting question I have been asked about a few times now and it appears many developers are confused what the answer is. Long story short: Yes, you should commit your composer.lock file.
The composer.lock file is a build metadata file that specifies exact versions of dependencies in your Composer project. It means if someone else in the team pulls down your code, they will get the exact same versions specified.
I recently moved to a Mac and one of the first things I did was install Homebrew, then setup all of my PHP projects, one of them being a Laravel project which uses Composer for dependencies.
Then I hit a snag telling my I had exhausted my allowed memory allocation in my php.ini file. Well, shit.
The exact message I got was:
Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 32 bytes) in phar:///usr/local/Cellar/composer/1.0.0-alpha8/libexec/composer.phar/src/Composer/DependencyResolver/RuleWatchNode.php on line 40
There are very few fonts in existence that incite rage and make you appear unprofessional in any creative industry than Comic Sans. You hear of the hate quite regularly, but is the hate justified? What is it about Comic Sans that people hate so much?
Like all fonts, each one has a purpose. Originally Comic Sans was commissioned for use in Microsoft Bob, an early 90’s application for showing people how to use Windows applications. It’s specific use was for comic book style speech bubbles. It’s quite a fascinating and quick story behind one of the most notoriously known fonts in history.
As a front-ender developer I am often tasked with helping solve user interface and accessibility issues in liaison with designers. Headings, body copy and even image placement is a pretty tried and tested thing, however where do you put the social buttons?
Do you put them above your content headings? Do you put them below your content headings? Do you put them at the end of your content? Do you put them in the middle of your content? There are some rules of thumb you should abide by when deciding where to place social media buttons:
I am most certainly not a Javascript purist, I love jQuery just as much as the next developer does, but that doesn’t mean I use it for everything. One thing that really gets under my skin is when jQuery is used to unnecessarily loop through and array or object.
It’s 2014, not 2008, we no longer have to use library methods because of browser API constraints like we once did for older versions of IE. Using jQuery.each() for looping through an array or object is quite an expensive operation and poor in terms of performance, this is one of those situations where native methods and conditions which are well supported eclipse jQuery 1000:1.
If you’re new to MongoDB and coming from a primarily RDBMS background like MySQL, getting your head around the queries can be difficult at first. This handy tool allows you to convert simple SQL queries to MongoDB, it allows you to get an easy understanding of how queries work without needing to know what to search in the documentation.
There is also another tool that works well if one or the other doesn’t and is usually my first choice which is this tool called Query Mongo. Both tools are invaluable if you’re starting out with the language, the benefit of this second one is it supports more advanced queries. I’ve added both in, in-case one or the other goes down for whatever reason.
In this world there are two different kinds of people: Android people and Apple people. After revealing the latest additions to their sought-after and some would say overhyped phones, Apple’s latest iPhone 6 and iPhone 6 Plus models have yielded the question: should you buy an iPhone 6 or Samsung Galaxy S5 and if it even matters.
It’s worth pointing out Apple’s genius strategy of releasing two different sized phones. A 4.7" inch iPhone 6 base model for those who don’t care for oversized miniature tablet screens and a 5.5" iPhone 6 Plus for those tired of being bashed by their Samsung phablet owning friends remarking over how small their screen is.