The voice of reason speaks ;)
There should be a back-to-school policy for dumbwitted managment. I'm always amazed at the rigorous hiring policies (even worse nowadays) for technists, and the ridiculous hiring policies for project managers and their sort. It seems to me, to work in a certain environment, you atleast have to know something about THAT environment. To me, project managers, more often than not, are like tourist hikers going off into a blizzard wearing only their shorts and some suntan lotion. And then hope that they, in the event of them getting into trouble (no, that would NEVER happen, yeah right), will call rescuers and be helped in a matter of minutes! > I guess I am the one to blame as I was the one creating the release. I > can't personally verify every commited change because I don't have the > time. We have several developers because one single guy ( that's me now, > used to be Robert ) can't keep up with all the coordination work and yet > do some coding at the same time. > > I could cancel all writing permissions but mine, have people use the > patch manager and wait for me to have the time to apply and test > everything. Now that would be great. I would personally ensure that only > code pieces that I like and feel correct make it to a release. I would > enforce everything. > > And then you would have one relase every six months. And you would > complain about some bug not being fixed and general lack of movement. > > Several developers means more confusion and a greater risk of what you ( > sadly ) just experienced with your management, but when we are all busy > it is the only way to get things going. > > --- > > I'll try to generate a new, stable, tested release, soon. I do accept > your criticism but to me your management is part of your job. I too have > a management and they are not keen on DHTML. They are rather > tecnologycally dumb, as well. They are afraid of Mac not supporting > things. In every project I feel the dyanpi should be used, I risk my own > personal credibility and job saying that the project will work and will > work well as they paid for. They thrust me, not the library. They > congratulate me, not the API. They will blame or fire me, not the API. > After all, it is MY job and the tools I use are my decision. > > > _______________________________________________ > Dynapi-Dev mailing list > [EMAIL PROTECTED] > http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/ _______________________________________________ Dynapi-Dev mailing list [EMAIL PROTECTED] http://www.mail-archive.com/dynapi-dev@lists.sourceforge.net/
