A while ago, I read an article, about a company (Storage Technology), that in the 80′s had a very expensive problem that resulted in one of their systems continually crashing. The solution of course was simple and probably not that expensive.
In the fast paced world of application development we deal with many things. Software limitations, lack of standardization in the industry, lack of time, resources, and/or quality. These things (and more) lead to bugged, erroneous or just plain bad applications…
I was on the struggle bus and noticed that E_STRICT errors were plaguing my WordPress install. Regardless of all the usual php.ini configuration stuff, virtualhost configuration stuff and .htaccess hacks — this was becoming a real headache.
TL;DR: SarpSTA asked about style.css and index.php — I responded that they are the minimum requirements to create a functioning Theme and explained their roles in WordPress.
I was recently interviewed by James Ball, a Creative Copywriter at Noble Studios. Being the Lead Developer over there is a constantly changing and challenging role. Agency life, as many will tell you, is not for the faint of heart. The interview allowed for some serious and some not so serious dialogue to happen and the value that provided was insight into the company and how it works.
I needed to add custom fields to the post type: Post within WordPress. That’s not problematic, in fact it’s rather quite easy. But, ordering Posts based on the assigned value of my custom field… that isn’t super straight forward.