There's no "5 or 6 features" that really make a comprehensive target to aim for. WhiteAlbumRegistry hits a lot of high points (though I don't exactly know the best way to "scrub data" without first pulling it from $_POST, but I don't think that's what he meant).
I think the important takeaway is that, as far as hiring is concerned, which means interacting with requirements as submitted to HR, keywords are more important than samples. Odds are if you build a sample, no one would look at the actual code that you built. What's important is that you can work with the keywords (technologies/frameworks/etc) that are important to the company you're aiming to get hired by, and those are so variable that you couldn't hope to build a comprehensive sample that would really encompass everyone.
The best answer is to be and know you are an expert in PHP, which means that if you haven't dealt with a particular problem or requirement, you can immediately formulate an approach to handle it anyway. If you are at that level with PHP, then everything else is just details. If you're not, then know what you can do and know enough to know what you can't do. If you are able to articulate the things that are on your list of things to learn, that's almost as good as already knowing how to do them, because it shows that you have the capacity to identify how and where to grow.--
On Saturday, November 17, 2012 11:47:43 AM UTC-5, Gokemon wrote:If you were building a sample PHP/mySQL web app to show off your skills, what 5 or 6 features would you want to showcase or think you need to have in there, to prove you can do the work?
In my case, so much of my work has been rather simple in design, not fancy, not flashy, and just functional? Like a user register with email activation, log in system with profile editing and password reset, which can show you understand sessions & cookies, and SQL & database connectivity is one, but what else would you build into a showcase?
I can paginate record sets across pages, and do file uploads, which I am working on converting into a photo tool for advanced profiles.
I’ve never done a shopping cart from scratch yet, so that’s on tap for later, but what would convince you that I knew what I was doing, if you were an employer?
You received this message because you are subscribed to the Google Groups "AtlantaPHP Discussions and Job Postings" group.
To post to this group, send email to atlan...@googlegroups.com.
To unsubscribe from this group, send email to atlantaphp+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/atlantaphp/-/fJ3jBlyna4sJ.
For more options, visit https://groups.google.com/groups/opt_out.
If you were building a sample PHP/mySQL web app to show off your skills, what 5 or 6 features would you want to showcase or think you need to have in there, to prove you can do the work?
In my case, so much of my work has been rather simple in design, not fancy, not flashy, and just functional? Like a user register with email activation, log in system with profile editing and password reset, which can show you understand sessions & cookies, and SQL & database connectivity is one, but what else would you build into a showcase?
I can paginate record sets across pages, and do file uploads, which I am working on converting into a photo tool for advanced profiles.
I’ve never done a shopping cart from scratch yet, so that’s on tap for later, but what would convince you that I knew what I was doing, if you were an employer?
--
You received this message because you are subscribed to the Google Groups "AtlantaPHP Discussions and Job Postings" group.
To post to this group, send email to atlan...@googlegroups.com.
To unsubscribe from this group, send email to atlantaphp+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/atlantaphp/-/ZsU78Fkc6t4J.
Everyone has raised some valid points and given great advise, but the most important and impressive skill is communication.
If you can explain your code (why you choose a certain method, process, implementation, etc.) to anyone else and have them understand your logic that alone will prove that you know your stuff.
If you can't explain it then you don't know it, plain and simple.
Creating a website to showcase backend skills won't serve that purpose. It will not show that you have created a killer form handling class or image management class, all it will show is that your login form works or you image does get uploaded or at least the errors are handled properly.
I am assuming that this is for the purpose of interviews; most companies want to see your code and want to know that you can explain and back up your logic whether it is the best way to do it or not.
So all that just to say that there is no backend skill that you can display on a website that will quantify or qualify your skills, you gotta be able to talk that stuff and roll with it.
--
You received this message because you are subscribed to the Google Groups "AtlantaPHP Discussions and Job Postings" group.
To post to this group, send email to atlan...@googlegroups.com.
To unsubscribe from this group, send email to atlantaphp+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg/atlantaphp/-/xRHVWFha1xcJ.

-Mike
I haven't had the problem (though I don't actually have that much "interview experience", and have only once been given any sort of skills test), that said the solution seems straight forward enough: practice, practice, practice. If you find yourself getting stuck on a PHP skills assessment test when you don't have access to your code library, then find some tests online and take them without accessing your code library. If you find a point you get stuck on, study it.It's not exactly easy to find more than basic tests online (at least, not for free). I googled "online php skills test" and came up with a couple potential options that might get you going.If it's more of a "code up an application or function to these specs" type of test, then pick a couple representative projects that you remember from interviews where you got stuck, and just bang it out on your own time without using any external resources. If you get stuck, make a note of where and why, and study up on it.It really doesn't matter what you're getting stuck on in the interview process, the test or some other area, if you find yourself getting stuck, study, practice, and just do it to death before you ever walk through the door.
To view this discussion on the web visit https://groups.google.com/d/msg/atlantaphp/-/r5OdCM3WT8gJ.