Jimmy Clark wrote:Based on the information that you have provided, I suggest that you do not accept the QA position and keep working as a PHP programmer.
Decline the offer and tell them that you want a 20% increase in the salary they offered. If they accept, then take the QA position.
In terms of career development, you should start looking at graduate programs in Information Systems or Business Administration.
Also consider PMP certification as this will enable you to more easily shift into business/management position in the future.
And finally, your written English is a bit rough, consider taking a couple of courses in English (with focus on writing and grammar.)
Jimmy Clark wrote:Thank you. Two more final questions for you.
When you interviewed for the QA position, did it sound interesting to you?
Do you currently enjoy working with your current company and like creating web applications?
Jimmy Clark wrote:Thanks. Just to clarify, you are currently a PHP programmer with less than 2 years of professional experience and have received an offer for a QA position from a different company.
Just a few more questions for you. If you accept the offer, will your salary increase? Do you have a college degree?
And finally, in your 1+ year of experience, how many web applications have "you" created? And how many web applications have "you" worked on which were created by someone else?
Dieter Quickfend wrote:I doubt any additional info could be detrimental to the answers given. This is not a yes/no question, it's a "what way do you want to go / what job do you prefer / what experience do you have / how valid is your company compared to the new one / etc. etc."
Peter Johnson wrote:1) I assume you are using MS Visio to draw architectural diagrams. When can't you continue to do that in Visio?
2) Not being a database heavyweight I don't know of any tools to do normalization.
3) Have you tried googling this? I doubt that you will find an Eclipse plugin by there must be someone who has come up with such a conversion tool.
Note that I answer your original request only to offer a reason as to why you were not getting an answer, and not because I have answers. (Often I avoid answering a question if I feel it will lead to technical details of other issues that I do not feel qualified to answer without a lot of work on my part.)