Feb. 8th, 2005 @ 02:42 pm
Ok, I've got a question for all the professionals out there. I've been looking for a while now to get into server-side web programming (PHP, ASP, JSP, SQL) for a little while now. While I do have experience working with these things working on personal projects, I have no professional experience. I was wondering if anyone had any suggestions on what I can do to more effectively represent myself in this way.
In terms of skills, I'm talking a heavy PHP/MySQL background, with a focus on content managers and database served content.
Just hoping someone might have some pointers. Feel free to ask me any questions.
Current Mood: creative
Current Music: Song for the Dead - Queens of the Stone Age.
|Date:||February 8th, 2005 07:47 pm (UTC)|| |
I would suggest, if you're looking for a professional job dealing with databases, that you get some experience working with some more advanced features of SQL.
procedures, triggers, etc.
Unless you're just looking for a data-driven webpage position - then you won't need much but the basics, as far as SQL goes.
I'm not sure what you mean by "represent" yourself, though. How to phrase it on a resume?
|Date:||February 8th, 2005 07:54 pm (UTC)|| |
I guess I just don't know where to start. I finish my degree in about 4 months, but all of my work experience thusfar is as a computer technician. I'm guessing the resume portion is going to be key, but I'm unsure of how to write a resume that can properly represent the fact that I do know what I'm doing.
I guess, what is important to list on a resume when you don't have the job experience to back up your knowledge and skill set?
|Date:||February 8th, 2005 08:10 pm (UTC)|| |
I'll be blunt - listing that you know this or that language are nice, but they don't mean a lot to the person interviewing you. What they look for, at least in my experience, is examples
of when you used this knowledge.
For example, I listed that I knew SQL and PHP and all this, and they were like "ok", but I also listed dynamic website systems and such that I've made with a SQL backend and they were impressed :)
Also don't really list classes unless they're senior classes (but you probably already knew that) that relate to the field you're applying into.
As much work experience that you can list (and as varied as possible), the better. That's what got me my co-op - I'm not into the field for good or anything, so take my advice with a grain of salt I suppose.
Hope that helps ::shrugs::
|Date:||February 8th, 2005 08:13 pm (UTC)|| |
"As much work experience that you can list "
This is my problem. I just don't have anything beyond my few websites I've made over the last few years and the only ones which impresse me are the last two.
Thanks for the suggestions though. They really are helpful.
*goes off to start an Open-Source project on source forge*
Triggers? We're getting them. We have cursors now too:http://dev.mysql.com/doc/mysql/en/roadmap.html
I (respectfully) disagree with the 'more advanced' statement; MySQL is veeeery powerful, and it used widely in the enterprise scale applications.
|Date:||February 8th, 2005 08:06 pm (UTC)|| |
Hey, get recursion and I'll actually respect the DBMS :x
(DB2 for life!)
|Date:||February 8th, 2005 08:21 pm (UTC)|| |
Are there any plans for including 'intersect' and 'except' in addition to union (and union all)?
I couldn't find those in the doc, either.
Can't wait until 5 becomes stable, though. I admit I'm excited to try a lot of stuff out :)
The resume, when it comes to programming, I don't find as important as providing example code... Start a portfolio, or an open source project. Design and develop a personal site using your own code.
Don't me wrong, a resume IS important to list your qualifications, but sometimes providing source code in your portfolio is just as valuable.
|Date:||February 8th, 2005 08:07 pm (UTC)|| |
I've been doing exactly that, with my personal site
. It has a section for showcasing functions I've put together. I'm debating on just making links to the source of the whole site.... minus the database config files that contain passwords and such, of course.
|Date:||February 8th, 2005 08:15 pm (UTC)|| |
and if you don't want to provide the source code, you could also always describe the way that it is structured - i.e. mysql database driven object-oriented php5 backend with xhtml 1.0 strict frontend [which is viewable, of course], and so on.
I don't think they'd have anything against conceptual things like that. Although it depends on the company I'm sure.