@dark_coderz It was never a deep issue for me because I properly orchestrated my usage. Acquire context, plan, refine, implement. That core loop is built into the harnesses now.
@babayagatwt I don't want to maintain and be responsible for some clone of something just because I can. Developers have never had a question of whether they could build something. The question has always been: What does it cost and what do you get?
@tanujDE3180 Always merge, any other option is a response to how well that goes. In a properly tasked team the edit overlap should be minimal. Commits behind should be nearly irrelevant.
@icanvardar Define "exact same thing". Also, tell me you don't understand the actual economics of SaaS without telling me you don't understand the economics of SaaS.
@ATBFooty@AntonioTweets2 More or less. They are exceedingly rare. Overstated by stat methods (drug deals gone bad at midnight in a parking lot are counted) and by nonstop national media coverage. Also never covered with any proportionality, like compared to heat deaths in Europe.
@LUvish_@arpit_bhayani I just wrap it. Deal with the error or pass it. There are ways to create error types I use them. It's not bloat, it's actual error handling.