Mine are fairly small, single-person projects. I’m not part of a team. The stakes are small. I’m sure it's much different on larger team projects

The project that prompted the question is a single-person project...

Historically, my company has relied on Online Travel Agents (OTAs) - Airbnb, Booking.com, etc - for finding guests for our Furnished Holiday Lets. It was always part of the plan to have our own booking platform but it was on the list of things to do 'one day'. And then the Pesky Pandemic arrived and the OTAs basically cancelled all booking and wouldn't take new ones. Although people couldn't stay with us for leisure, there were plenty of valid reasons for people staying. So, suddenly the booking platform became very, very urgent.

I created a fully functional booking platform from the ground up in a little over a week. On the backend there is a basic CMS to allow other team members to upload and change pictures and text.

Last year when I created the booking platform, I knew of the Monastery but hadn't created an account and knew absolutely nothing about templating or separating logic from display or anything like that. So the whole system is very badly written but it does what it needed to do. Now, whilst I am quite proud of my achievement, I want to refactor the site to use Template along with use strict; and use *::*; instead of require */*.pl; and all sorts of other good practices that I have learnt in the Monastery. The reasons for refactoring are so that we can make incremental A-B testing changes much easier and so that someone else can take over the display and design at some time in the future; not to mention making maintenance easier!

So, like you Radiola, this is a small, single person project in many ways. I am not part of a team although the stakes are probably a bit higher!
Having the wisdom and support of the Monastery to call on makes the prospect of refactoring bearable - otherwise I would approach it as throwing away everything we have except the DB design and starting again from scratch...something that would forever remain on the 'one day' list.

In reply to Re^4: Splitting long text for Template by Bod
in thread Splitting long text for Template by Bod

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


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.