all of the things you listed are included in the software. and they all serve the same thing. to maintain the software. you should focus on the purpose as much as you focus on the process.
I totally agree with this comment. just such a person was the manager of the team I was on. and it wasn't really possible to argue. The only thing he understands from arguing is that he is right in the end. Imagine this happening even in the smallest of arguments.
tailwind is a library I don't like in many ways, but the criticisms in this post are pretty ridiculous. tailwind is not a library offered with the motto of component driven as the author mentioned. and instead of bloated packages like radix ui I think it's a more sensible solution. at least it gives a chance to follow a more optimal path. I think it is impossible to find an optimal way with the libraries it recommends. you should use everything just as the library intended.
It's an interesting idea to write the app based on the tests instead of writing the test by the app. I don't think it will be very healthy for the overall application, but it's worth a try. Testing with real dependencies without using mock seems better overall, but this brings with it quite a few problems.
Enterprise software is the software that mostly lies and bullshit today. Companies spend a lot of money because at the end of the day, it's working. Who cares how it works.
godaddy and namecheap. If you are using these two sites in some way and paying money, what you need to do as soon as possible is to transfer all your domains to another site and delete your account. As long as you keep using these idiots they will continue to grow more.
The maintenance cost is a debt that must be paid by all means. and microservices may be the cleanest solution if there are teams that develop businesses completely independent of each other.
for most libraries, I think people in core teams cause it. eg react is destroying the potential of hooks more and more with each release. and it's weird that no one of them said, "what are we doing right now, does this stuff really have to be this complicated", but I guess that's exactly what open source development culture is today. we know best and you should use it.
What problem exactly is this app to solve? it looks exactly like a producthunt product. a big landing page with long text but you never understand what it does
This should definitely be implemented in projects where the use of the feature flag is common. When you go with boolean values, after a while you have a pile of data that you don't know what was done and when.
I really respect people who think this is a really good moderation on this site. Your belief that something that does not exist exists is truly astonishing.
If you want to be holy to HN, you have to develop a product with zero modernity, zero responsiveness. It's really interesting to pay for a site that only one man developed for his own pleasure.
I think the most logical solution is to plan your own daily calendar for this. If you are not working in a position like support, you can stay away from slack completely and only check it during break times.
I think for the vast majority the upvote button functions as a highlight. In other words, everyone who says they want to see this post in the front row presses the upvote button. Compared to other platforms, I think this is healthier.
The package you use for testing may cause memory leak problems. The package you use for build may cause memory leak problems. With the new version of the frontend library you use, you can completely change its architecture and decorate it with different nonsense. Welcome to the world of javascript.