Search results for query: *

It is because of this that I never write/send emails when I am upset. I either wait and hour or deal with the problem over the phone. hmmmm

if you really want to quit, at least go out full guns and speak your mind. be honest and objective when you do it. the worst case scenario is you get fired which means you get unemployment checks versus quitting. hmmmm

normally I would say go to HR, but you have no hr. so i would just tell my boss. if you can't be honest to your boss then find another job. hmmmm

Yeah, vanilla means 'common' or 'plain'. I personally prefer rocky road. hmmmm

This is not about throwing money/people at the problem. It is about managing projects and knowing when you need more money and people. And having only one developer is such a big risk for a small company because if that developer leaves the company can be screwed.

I think you are digging yourself into a big hole and eventually your hole will crumble with you in it. IMHO, I say you break down the time it will take to complete each project in working days. In each project show the milestones and the time for each one. You then go to your leaders and say...

I would say some UML and Use Cases would be good to have in Business Requirements, but you would need more then that. UML is definitely something you should have before you start coding though. You first really just need to document what the client says they want into a readable format. After...