Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122354
MIME-Version: 1.0
References: <CAK=iT=UrMCPw5ydCnxa_87ws6xKRO5Y3qJnmchczgDds8u660A@mail.gmail.com>
 <CAK=iT=UDUjCZ-25k_MkHFO7uKdWAqoJxdWLVBGM2_SYDk-JyAg@mail.gmail.com>
 <742f202d-7990-4f51-b903-7a15e3fd33c2@app.fastmail.com> <CABigaAW2KeGxf7HnzpcOeS=CL31=UNGZnqpZvoJsJg4miBTBGw@mail.gmail.com>
 <1cd8fa7b-ab62-4563-bf13-bb7801f1ce8d@app.fastmail.com> <CAK=iT=X5XKdSZ1D=+SEU4=12hJK+oPn+XBWxA54yyQsxAixx8A@mail.gmail.com>
 <CAOyH9yT5NQQYgq=5O5q==BaTpm-JJRDUcAsX2Tc36hbXLdH5vw@mail.gmail.com>
 <CAK=iT=W7xzS_9FZj-Cd1uUBaLtX=157t81_KOkr999bRyTcDjw@mail.gmail.com>
 <CAOyH9yQKA+RnhXFHvH=dVHT8UWfyF_A89p_c9wES1k4kKstBtA@mail.gmail.com>
 <CAK=iT=VtOx=dZYNMNnn0iVPm4KUy1BoCr07=WYJFR9HJOOKLPg@mail.gmail.com>
 <CAOyH9yTJNq9Y+OcOGw7bkfU7efxoz+0bUt9iyy949_Zj=1_M1g@mail.gmail.com>
 <CAK=iT=VzVOTbqh_v4zcu3MjPq+QzWcstMJnz0z1LPZEbJVVAcQ@mail.gmail.com>
 <90cc47f7-ba80-4798-8447-2f3bb5734eab@app.fastmail.com> <CAK=iT=XNuJMaUD5bNZKODp+3NfbnvJVWdL24BHc71AWAUkDqKw@mail.gmail.com>
 <eaa32340-af2f-496d-a55c-e84aa222dfc4@varteg.nz> <CAK=iT=U4pw8q=Pvgrf_L16S9y0Q4fvAzBKeBDK+Buw1Y+kOt+A@mail.gmail.com>
 <CAPzBOBMMB9==c4WdSUo2HZCRuvHXb+JXMgcKaOxdEMeMNMOoeA@mail.gmail.com>
In-Reply-To: <CAPzBOBMMB9==c4WdSUo2HZCRuvHXb+JXMgcKaOxdEMeMNMOoeA@mail.gmail.com>
	=?UTF-8?B?Yg==?= <6562680@gmail.com>
Date: Fri, 9 Feb 2024 18:18:12 +0300
Message-ID: <CAK=iT=WuvaXLmn1tkTDDqTiyXrc+0OwY5E2ih6XJ-AeiFaoQng@mail.gmail.com>
To: Robert Landers <landers.robert@gmail.com>, internals@lists.php.net
Content-Type: multipart/alternative; boundary="000000000000d594a00610f4717f"
Subject: Re: [PHP-DEV] Feature request: https://github.com/php/php-src/issues/13301
From: 6562680@gmail.com (=?UTF-8?B?0JPRgNC40LPQvtGA0LjQuSBTZW5pb3IgUEhQIC8g0KDQsNC30YDQsNCx0L7RgtGH0LjQuiBXZQ==?==?UTF-8?B?Yg==?=)

--000000000000d594a00610f4717f
Content-Type: text/plain; charset="UTF-8"

> I've worked on PHP (and non-PHP) applications with (tens of) millions of
lines of code

Grats, you're a hero. Now, you're a hero.

You can solve the application in your paper notebook. That does not explain
why computers should know some correctness and not help you, because you're
a hero.

I now have the legacy of webinars. There's no webinar archives, only
runtime config, blueprints, there's user forms that are only processed in
batches by queue, there's 3 levels of nesting in webinars.

And there's existing code with wordpress repeaters and such stuff that is
working somehow.

So my current task is to multiply non-existing webinars to non-existing
form submissions and multiply that to wordpress and 3 levels of webinar
nesting, and get a solution in a maximum of one week.

Suggested solution - "we know the correctness, so you have to tell your
manager - you need to completely rewrite existing logic with 10000 small
methods with exceptions, then catch it everywhere, then write tests, and
then debug it at runtime" for the future.

That strategy followed by firing out or leaving. It should be fixed in the
shortest possible way without rewriting your code. And, it should work fast
using massive select/insert to reduce page loading time.

If I started to split that 100 repeating fields into simple SOLID methods -
it would take a month. I haven't a month, and nobody can give me a new job.
So I MUST use non-breaking errors to do it faster. And the community
doesn't want to implement handy solutions because they are tired of simple
things (because they guess that simple things are always small instead of
being plain scripts).

Best! Just not enough good words. Thanks for attention.

--000000000000d594a00610f4717f--