maybe look at it this way: follow their rules for awhile, making
improvements in the process where possible, especially with completely
new projects. Someday when they see the value in your approach and your
in charge, then you can have good software architecture practices
again.HTH -Eric
On Fri, 2003-08-15 at 08:12, Russ Wright wrote:
> Hello SLUGgers!
>
> I'm having a bit of a problem with my new employer. I've spent many years
> developing software for some bigger development houses that follow structured
> development processes and created some high quality, stable, and maintainable
> software. I recently took a job with a small three developer shop.
>
> Here is my problem. Their code is crap. I mean lousy, patched togeher and
> undocumented. I've been assigned to fix some bugs in the app and I took the
> time to analyze and document the proper solution. It seems that my method of
> analysis was and I quote "a waste of time... if we all took that much time to
> look at the problem we would go out of business"
>
> My boss further explained that I should just find a quick solution, patch it,
> slam it out and let the user community test it in production. To say the
> least I'm perplexed. My years of development experience tells me this is a
> BAD trend that will come back to bite me in the arse later. I understand
> being nimble and staying profitable. I've tired to explain that good code
> takes some time and fast code cost more money later but he will not listen.
>
> I need the income, but should I compromise my standards?
>
> Any advice?
> Russ
>
>
> -----------------------------------------------------------------------
> This list is provided as an unmoderated internet service by Networked
> Knowledge Systems (NKS). Views and opinions expressed in messages
> posted are those of the author and do not necessarily reflect the
> official policy or position of NKS or any of its employees.
-----------------------------------------------------------------------
This list is provided as an unmoderated internet service by Networked
Knowledge Systems (NKS). Views and opinions expressed in messages
posted are those of the author and do not necessarily reflect the
official policy or position of NKS or any of its employees.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:08:30 EDT