How do I explain to a client that it will just be cheaper to throw away all of his shitty code and start anew?
How do I explain to a client that it will just be cheaper to throw away all of his shitty code and start anew?
[DATA EXPUNGED]
[DATA EXPUNGED]
Не, правда, рад за мужика, но все же... До чего же ушлый тип. Хорошо, что он за нас. (хотя и не всегда выполняет что наобещал) Я кажется нашел слово, которое описывает сети, подобные Fediverse. Почему бы нам не назвать это "Экосистемой"? Вроде подходит.
Show previous comments
@drq pov: one billionaire buys google and gmaps and people migrate to streetcomplete @drq было бы ещё прикольно выдавать разноеи количество звёздочек за разные квесты. Например за актуализацию данных об организации побольше, потому что они на OSM в крайне печальном состоянии, но при этом ойей как востребованы :blobcatgooglyholdingitsheadinitshands:
Show previous comments
Snaps are the Mir display server in the world of software packaging formats. It literally has no real reason to exist other than "it's not Wayland or Flatpak and it's Canonical's own, so suck it". By the way, what I respect about Go - is that it strives to exclude the situation where you have unreferenced entities. If you're gonna import a lib, or declare a variable, or whatever else, you MUST use it somewhere down the line, otherwise the project just wouldn't build. I love it when the tools are built in such ways that they shape good habits. Mandatory indentation is one of the reasons I loved Python so much. I'm picking apart my client's codebase for refactoring. As expected, there's a lot of duplicates. But duplicates are easy. fdupes lists them quick. The real, actual problem is near-duplicates! The files that differ by couple of lines, but otherwise are identical. How do I find them? Is there any tool for that? У моего клиента - синдром Плюшкина. Он _НАСТАИВАЕТ_ на сохранении каждого куска говна в репозитории, не важно, связан он с проектом или нет. |
He has spent 15 years writing the shittiest PHP in the entire existence thinking he's doing development and puts a lot of sentimental value on it. He gets very emotional when I tell him that at this point the project is unmanageable, a lot of it has enormously stupid security issues like unescaped SQL queries, entire parts of it are physically unable to run because they are ridddled with errors, that copying and pasting stuff 16 times is not how you do programming, the structure is nonexistent, and with this level and amount of problems we'll spend more time fixing all this crap than rewrite this from the ground-up.
Talk about sunk cost fallacy.
He has spent 15 years writing the shittiest PHP in the entire existence thinking he's doing development and puts a lot of sentimental value on it. He gets very emotional when I tell him that at this point the project is unmanageable, a lot of it has enormously stupid security issues like unescaped SQL queries, entire parts of it are physically unable to run because they are ridddled with errors, that copying and pasting stuff 16 times is not how you do programming, the structure is nonexistent, and...
@drq showcase the difference on a small sample?