Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:122345
MIME-Version: 1.0
References: <CAK=iT=UrMCPw5ydCnxa_87ws6xKRO5Y3qJnmchczgDds8u660A@mail.gmail.com>
 <CABigaAUjSx3-vEaQhPk-toJTSg+J3CLrO3otpm1g6hqbYyQKvw@mail.gmail.com>
 <CAK=iT=WgsEZjyu3Y2wTWvycqCsYH7MrLsZgERZK3u75U08ePpA@mail.gmail.com>
 <CAL0xaBHfEMs1BVAMZOuFCUpb9orNSRD0YDhu=3wJAGK7K0_=dg@mail.gmail.com>
 <CAK=iT=XDVcs+y4XDmGu2re137i2yD9LiEj1-HLvyxxxrb8jFUw@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>
In-Reply-To: <CAOyH9yTJNq9Y+OcOGw7bkfU7efxoz+0bUt9iyy949_Zj=1_M1g@mail.gmail.com>
	=?UTF-8?B?Yg==?= <6562680@gmail.com>
Date: Thu, 8 Feb 2024 14:15:48 +0300
Message-ID: <CAK=iT=VzVOTbqh_v4zcu3MjPq+QzWcstMJnz0z1LPZEbJVVAcQ@mail.gmail.com>
To: Alexander Pravdin <alex.pravdin@interi.co>, internals@lists.php.net, 
	Arvids Godjuks <arvids.godjuks@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000002c1e0c0610dcf157"
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==?=)

--0000000000002c1e0c0610dcf157
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Just because PHPStan is a ready solution for design errors that you can
predict.
My case is about errors that you detect later, after the design is
finished, PHPStan shows you that "all done!".

Because it's not \LogicExceptions (types, mappings), it's all
\RuntimeExceptions... You have to implement it after the design is done!
Also writing code comments for PHPStan accidentally increases time of
catching \LogicExceptions that will be autocatched once an exception
happens and is reported. This is necessary work, but it increases the
estimate; the business does not want to hear long deadlines, and considers
you ineffective. But if you say too small, the code will not even pass
PHPStan, it will not even pass visual inspection. Therefore, I say some
magical things, and then I correct them, for some reason they like this
approach better, they are not used to improving until everything works
properly, they even push the word into the lexicon - MVP. This means =E2=80=
=9Cit
doesn=E2=80=99t work well but it works=E2=80=9D, it seems normal to them in=
 order to get
results faster. Because they will receive bonuses for results, but for bad
results you will receive punishment.

A closer solution is "get out from the job where business was built that
way to ignore complainings". I had worked for 12 years. I've changed a lot
of jobs because of that. And any new job is the same. It could be more or
less ready to build the same, but they are working on it. It's not a
solution either. As a result - "you cant rebuild
non-yours successful business that gives you money because you know how
things work", you have to fix or lose your rent home.

=3D=3D=3D

@Arvids Godjuks <arvids.godjuks@gmail.com>

I had to work in such companies, and there were 13 projects at the moment.
But after some time I realized that nothing depends on the number of
projects. All businesses strive to not give away the right to think to
their employees. If this happened, it was more an accident than a goal. If
they are forced to listen to you, you are considered a problem that they do
not yet know how to solve.

Now my company has only one project, which they are leading themselves. But
business and profit dictate the conditions - at first we do a year very
quickly, then we redo it for 3 months, which we will have time, but the
amount of legacy is too large, because the pace is insane, and the tasks
are becoming more and more difficult.

They can't just "wait quietly until you finish." They will ask you when,
and will be disappointed if you suddenly suddenly realized that you need to
move the deadlines, because there are already 5 new ones behind the current
task and they are planned for the quarter. =E2=80=9CRewrite better=E2=80=9D=
 is not included
in them.

Let's stop discussing my personality, I gave a rationale for why languages
should preferably help developers, since such a question arose. Because
there won=E2=80=99t be fewer situations like mine, but there will be more j=
obs. And
there will be a lot more bad companies, and in the end there will be very
bad ones left.

--0000000000002c1e0c0610dcf157--