trey
I think linkedin has a resume upload and maybe branchout does as well if you are more of the social networking type.
After looking over it, this is a really framework. There really isn't too much that I would throw out to make it smaller, except maybe the curl wrapping class.
A couple of things that would be nice are:
1) if your Controller classes had some state forcing them to be static like you do means that there could be a lot of duplicated code between similar actions
2) if you had a 'layout' template that could be set that would wrap the results of the actions. Maybe this already exists, I just couldn't find it.
Its very clear that you intend to not do any kinds of magic, so I can see why you left a lot of things out that a lot of other frameworks have. Maybe that is why you don't have a layout wrapper template.
I have yet to see a PM that actually performed PM duties that yielded a net positive for a company.
If the PM doesn't have authority over developers the position devolves to a glorified QA position so that they are actually doing something useful.
If they are given authority over developers they add a level of politics and stratification that ends up being a distraction to a team that otherwise works well together. Software developers have a lot of power to affect change and are generally anti-authority. Keeping an organization structure flatter seems to make software developers more productive.
Given the choice I would avoid having a PM and just hire more intelligent software engineers. A quality QA person can give you the same effect without the mess.
Note that I am separating project manager duties away from product manager duties.
Actually, I disagree with the premise of this statement. I don't want feedback on why I was rejected, I want feedback on my product. Yes, I can see that it is very nuanced and difficult for you to say which idea/product is better than another, and you have your own business reasons for making those decisions. I don't think anyone really expects you to disclose those reasons, and even if you did it would be completely subjective and would just lead to arguments. However, given that, you're only addressing why you don't comment on the relative strengths of the applications and not why you don't give feedback on any individual product/idea.