piscator

4 ms·

1.
by piscator 6mo ago
They will definitely not be able to debug what they built at a certain point. I think their strategy will be to delete parts of the application, and rebuild them, but this will not be sustainable. This comment (and similar ones) helped me t
2.
by piscator 6mo ago
Great to hear this, it is reassuring I am not the only one currently with a similar case, and I will try to give an update when there are significant developments.
3.
by piscator 6mo ago
Thanks, yes it is saddening in a way. That was my first reaction combined with disbelief. I am reasonably successful now in letting that feeling go, and I try to look for the best outcome, also from a professional perspective. At the same t
4.
by piscator 6mo ago
The project is deployed to a test and "live" environment, but since it is a rebuilt of a very old project that is currently running their business, we don't have to build in production. They needed the rebuilt because the pro
5.
by piscator 6mo ago
If another capable dev was brought in to work on it independently, I think I would help to transfer it to them, and quit afterwards. When the dev would not be capable, I would advise against it. But in this case, it is the decision of the c
6.
by piscator 6mo ago
Thanks for the suggestions. I've considered to protect some branches, but in the end decided against it. I was not looking forward to review all their huge amounts of slop code. It would also be different from reviewing code of a &quot
7.
Ask HN: Client took over development by vibe coding. What to do?
63 points by piscator 6mo ago|42 comments
8.
Use Elasticsearch as a Driver for Laravel Scout on macOS(arievisser.com)
1 points by piscator 7y ago|0 comments
9.
Show HN: Cryptoboard – Altcoin dashboard showing trends from Twitter and Google(cryptoboard.tech)
7 points by piscator 8y ago|0 comments