sunwukung

http://wordpress.org/extend/plugins/twitter-tools/ http://www.quickonlinetips.com/archives/2007/04/10-best-twitter-tools-for-wordpress-blogs/

I doubt you're gonna get a stack overflow in an html page...

what was your role in the design - did you do any server side stuff - which system is kicking back the error?

alternatively - you can apply this class ("group") to force divs to self clear their contents: .group:after { content: "."; display: block; height: 0; clear: both; visibility: hidden; } This adds a fullstop to the bottom of the div - which in turn behaves like the classic "cleardiv" - but then hides it.

and on that count I would generally assume you were slightly more professional than an amateur or hobbyist. This is an issue of semantics - 'pro' has slightly different connotations than 'professional' (although, as Zed has noted, this isn't always the case, some amateurs/hobbyists are very talented)

I suspect that the quality of output from the professional community is of an overall higher standard than that from the amateur. The existence of anomalies in this general pattern are the exception and not the rule. I hate to say it but, on balance, the quality of work posted for review on closed sites is generally of a higher standard than that which I have seen elsewhere. You are confusing working in a professional context with the degree of experience acquired in that role. That a person is awarded employment is generally the result of an interview - in which instance their work is deemed of a suitably high quality to be considered "professional" (relative to that organisations standards). http://www.thefreedictionary.com/professional

generally speaking, to do something professionally you need to be relatively good at it, no?

pros by definition do know something... Hey, my apologies - that wasn't my intention* . I spend half my time killing spam on here these days - if the forum was invite only, that wouldn't be the case (but then it would't be WDF any more). It can be a little frustrating to see the same questions come up again and again - but hey, I asked them once too! The unfortunate truth is that in an open skill based forum, you are going to see a stratification of users based on experience. My observation has been that advanced users trickle away (often appearing on closed sites like Dribbbl) - make of that what you will. I'm guessing it might have something to do with trying to filter out some of the content that they now find redundant - so Dribbbl shows work from more experienced designers, and so the work tends to be of a higher quality. Having said that, the work in these communities also tends to be more homogenous and "safe" - design memes propagate rather quickly round the "in" crowd. *well, that's not entirely true, I'm just taking a swipe at people not using the "search" facility, or Google for that matter...

I think it has some distinctly positive benefits. Invite only would do a lot of favours for this forum for example - given that it has been reduced to an endless re-run of the following questions: 1: What's the best editor? 2: Why won't this work in IE? 3: I've learnt HTML, what next? 4: Which CMS is best? which means that a lot of the talent that used to frequent this joint have busted out and gone to places like Dribbbl, Fffound and Forrst* to get away from the noobs. This helps to maintain the quality of contributions, block access to the hordes of spammers/SEO hounds. One of the most basic tasks you encounter as a developer is the eponymous login, which by definition is erecting a fence around 90% of sites anyway. *on a negative note, why do all these sites have this thing about dropping vowels and adding consonants...

It's possible - but for my money the layout is a little overcomplicated - WP isn't ideally suited to it (more of an EE/ModX job IMO) and the biggest issue I can see will be maintaining a consistent vertical rhythm in the middle columns (and the promo boxes)

I wouldn't sweat it re:ORM - although Doctrine is arguably the best ORM for PHP. ORM is a bit of a coding minefield - and there are some strong feelings surrounding the concept of ORM. In general - an ORM is good for those instances when there is a general 1:1 mapping between a Domain Entity and a DB Table (i.e. User class : users table) - but can rapidly fall apart for anything more complex than a 2 or 3 table join. Moreover, ORM's can require a "de-normalised" DB structure to allow for OOP inheritance. There comes a point when the cost of using an ORM outweighs the benefits. There is an analagous concept - DBAL (Database Abstraction Layer) - that has perhaps more practical implications. Ultimately, a DBAL is an OOP wrapper for your most common DB routines (i.e. selectById, selectWhere). Personally, I prefer DBAL to ORM. I think it's a wierd tradeoff to corrupt your data structure and learn a code based non-optimal version of SQL when the whole chuffing thing is meant to hide all that away for you. DBAL just tidies away some of the more tedious details.

Keep em separate during development - push them into one file (and minimise it) for production. A good IDE like Netbeans can reformat minimised JS back into it's original format - but failing that, keep hold of your full fat scripts for later use.

I agree with Jock (an increasingly frequent event...) although I'd remove the need for certain topics - bitwise operations for example. Personally, I'd be looking for someone with some good understanding of design patterns and associated implications (i.e. Dependency Injection, MVC), a competent degree of knowledge in *nix, good understanding of RDBMS - and a better understanding of how ORM features work in relation to Relational Theory (i.e. the implications of Active Record when using libs like Doctrine/Propel). More importantly than all of this - I'd want someone that ENJOYED coding! Plenty of devs out there that just do it for the cash...

After working in this field for a little bit, I have to say I disagree. Web design/development is commonly regarded as a vocation with two paths. This is largely true, the skillset required to be a developer is radically different to that required from a designer. Yet, if we take architecture as an example, if an architect has no concept of engineering - then they will not be a very good architect.

My point is that Smarty is (at best) tangential to MVC - and may confuse the OP