What difference has your service made in the local community? Can you cite specific instances where your service impacted the lives of others, for good or for, uh, not so good?
I second the use of siege. I've found it to be easy to use, very fast, and customizable. There is another piece of siege called 'scout' which is used to scout out a website and return page entries for later load testing by siege. Scout is also customizable.
Using scout and siege, with even a simple shell script, you can blast the bejezus out of a web site.
(Oops, may not want to say that on slashdot...)
in having a bozo for a PM. You have plenty of company- just look at most any large organization and you will find the same thing.
The Trick (TM) is to get you and your PM (even the whole company) to work on improving it's underlying processes and procedures.
You need a clear Statement Of Work (hopefully up front), and clear procedures on how the entire project plan, development, testing, and delivery should work. It takes time, effort and sometimes blood, sweat, and tears, but it's worth it. You'll be more focused, more productive, and there will be fewer problems from start to finish.
I'm personally of the opinion that good technical people do make good project managers, but only when they are not working as a developer on the same project. Mixing the two usually doesn't work.
Slashdot Mirror
What difference has your service made in the local community? Can you cite specific instances where your service impacted the lives of others, for good or for, uh, not so good?
Using scout and siege, with even a simple shell script, you can blast the bejezus out of a web site. (Oops, may not want to say that on slashdot...)
And something about 'harvesting minerals for the benefit of all mankind'.
Personally, I hope they set up the first take-out on the moon.
Can't they be put up online and let the people decide?
If not, why not?
The Trick (TM) is to get you and your PM (even the whole company) to work on improving it's underlying processes and procedures.
You need a clear Statement Of Work (hopefully up front), and clear procedures on how the entire project plan, development, testing, and delivery should work. It takes time, effort and sometimes blood, sweat, and tears, but it's worth it. You'll be more focused, more productive, and there will be fewer problems from start to finish.
I'm personally of the opinion that good technical people do make good project managers, but only when they are not working as a developer on the same project. Mixing the two usually doesn't work.
You're full of shit.