I'm struggling with a job which grew out of a 1 to a 10+ man project and is in many possible ways misdesigned.
But now I am busy to stop other colleagues "improving" things on the fly.
Changing concepts demands ...
- a clear goal,
- a well thought plan,
- good team communications
- a general agreement
- approved responsibilities
- and last but not least a willing management.
For instance I'm reluctant to let an over-motivated newbie change the data model towards a "better" one, while he doesn't understand other legacy code.
Point is it depends on the dependencies (no pun intended).
A small isolated project is easily changed, starting to "improve" complex stuff most likely ends in worsening the degree of entropy i.e. causing more chaos.
My advice:
Locate the chief architect and suggest your improvements.
He or she is the one who has to take the responsibility and decide about the strategies.
You can't be fired for following orders.
Otherwise take a sleeping pill or change the job.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
