Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:106758
MIME-Version: 1.0
References: <CAF+90c9Kc6m_bv=aJxbD3-RmnNXXLqv6mPjHp7U7qxX_ck27qw@mail.gmail.com>
 <CAF+90c_94zAj-7XW+=YtZ2VsZEshd4DvNY8_17PyiBXvYR1gdw@mail.gmail.com>
 <CAJHtznw5wOTMA-BUO6hOARxSie75+PwccSocVapHi4k02Z+x0A@mail.gmail.com>
 <CAPKYkKzc37d52ZjHy0ht6Oc_HgoBq4+DandNW1Hk-+x5NnUS7Q@mail.gmail.com>
 <CAPKYkKwhUmq40yGta3+ERfcDOOrkPi5Db6-i7pPMRmV4CrQRTQ@mail.gmail.com>
 <7ddbae5c-7451-4094-8b32-19676128054b@thelounge.net> <CAPKYkKyYvqW9Hm-nae0CXJ98XxRzt7XRpe_+FzeqiJME3K4jug@mail.gmail.com>
 <CAPKYkKw5vxgeM+vq_z9YhNYEMuPodCjfGNv6BRFS+bg0BG-Q0w@mail.gmail.com>
 <CAOkcCt_xsP1AOwB0-nuY4_qwxSc3h8mns_Yax9UnrLzFCN-m+g@mail.gmail.com>
 <CAPKYkKxAkowF_H9gDZg2pDVdUyftJz0b2LAE08jW8jjA6Nq-uw@mail.gmail.com>
 <CADyq6sJd6=2UEXXrad2heYw4Mp876rSQ9ZcKeuXOKEWO8F2saA@mail.gmail.com>
 <CAPKYkKw7Q7A4Z5TkgNX-=LPZZy7_orCRUsULBA7j=wZgKU-VuQ@mail.gmail.com>
 <5d6699ce.1c69fb81.e9b71.2525SMTPIN_ADDED_MISSING@mx.google.com>
 <CAPKYkKwkyXh64fyTeZeLrZR_kXQ9w9d=skFmqcdWpk=z0HSMxQ@mail.gmail.com> <5d66a7f0.1c69fb81.b3ab4.6463SMTPIN_ADDED_MISSING@mx.google.com>
In-Reply-To: <5d66a7f0.1c69fb81.b3ab4.6463SMTPIN_ADDED_MISSING@mx.google.com>
Date: Wed, 28 Aug 2019 18:46:18 +0100
Message-ID: <CAAwbVudegJPCyaVdF9X4tLO=aLHi8zFBaYKMcqik66dhnmiPnw@mail.gmail.com>
To: Mark Randall <markyr@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000003f0ce1059130fbd7"
Subject: Re: [PHP-DEV] [RFC] Reclassifying engine warnings
From: oludonsexy@gmail.com (Olumide Samson)

--0000000000003f0ce1059130fbd7
Content-Type: text/plain; charset="UTF-8"

On Wed, Aug 28, 2019, 5:12 PM Mark Randall <markyr@gmail.com> wrote:

> On 28/08/2019 16:37, Chase Peeler wrote:
> > I'm also not the one that built it on the eggshells - I'm just the one
> that
> > is now in charge of developing the system that someone else left sitting
> > eggshells.
>
> That's a challenge which at some point or another will face all
> technical leads.
>
> You have to go to the people making the decisions and say:
>
> "Okay, look, we've got ourselves a problem here. We've dug ourselves
> into a hole by cutting corners, building up debt, and we've never made
> it a priority to fix it, and now it's causing us problems. It's not one
> person's fault, it's something that has collectively developed over
> time, but the reality is, the problem is there and needs fixing."
>
> And when the manager asks "What problems?" you say something like:
>
> "The language we use is moving towards a much stricter approach to
> handling ambiguous or error prone code. This can only be considered a
> good thing, but it is going to mean that a lot of our technical debt is
> going to manifest as errors that will stop our site from function..."
>
> Then the manager will go "Can't we just keep using the version we are on?"
>
> You reply:
>
> "We can for a short period, perhaps an extra year or two, but the
> reality is that PHP is moving forward, and the current version won't be
> supported forever, and even if it were, we would be missing out on major
> performance enhancements and new features that could help us to build
> new features".
>
> The manager says: "Lay this out to me"
>
> You reply:
>
> "It's like our company car still works, but it no longer tighter meets
> emissions standards so they won't let us take it into the city any more"
>
> "Crap", the boss replies "Okay, we had best fix that"
>
> --
> Mark Randall
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php


This is the best reply with all possible good reasons laid out in few
sentences per line ever I've seen on this mailing list.


>

--0000000000003f0ce1059130fbd7--