Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"
 
PerlMonks  

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Applying a trick I learned from Edward de Bono, create a good idea out of an absurd one, namely become a time traveller...

Although design including code design moves forward in time, as soon as those are complete, you should ideally jump mentally into the future, starting with how the system will be supported and maintained after it is live and work backwards to the last relevant task which might be deployment of a given release into production. Does git cover it or do you need additional tools such as puppet? Will there be configuration files and installation scripts? What will the UAT and test environments be like and how will they be provisioned from your repository? How will you create the configuration data that distinguishes between say production, test and development environments and what tools will use that data? Only when you know that can you wind the clock back to the end of the development cycle where you can now make a list of deliverables by type, from your code design and implementation plan. After that you can jump back to where you are now in reality, design your git repository using your own correct rule (only push what is custom-built otherwise configure it to be installed wherever its needed) and you are good to go forward.

One world, one people


In reply to Re: Catalyst versionning by anonymized user 468275
in thread Catalyst versionning by QuillMeantTen

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others lurking in the Monastery: (2)
As of 2022-07-04 14:28 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found

    Notices?