I don't consider it weird at all, as all sorts of crazy stuff happens with code. Some bugs appear very rarely because their trigger conditions occur very infrequently. Depending on the application, there are often notable sections of dormant or unused code, especially for old projects. ๐๐๐โจ๐ค
!INDEED
!WEIRD
!ZOMBIE
Those "dormant or unused" code or "old" code likely cause intermittent problems which are usually hard to catch and fix, where rebasing code often helps fix them (even if doing so takes a lot of time) !INDEED. ๐งโโ๏ธ๐ค
!WEIRD !HOPE !PIZZA !WINEX !ALIVE
Exactly, completely rewriting or rebasing older code is usually a very good idea. ๐๐๐โจ๐ค
!ALIVE
!BBH
!HOPE
!INDEED
!PIZZA
!WEIRD
I think that most dev teams just have the right number of team members to finish whatever is on the project plan, so when an unexpected problem pops up during development, delays occur !INDEED. ๐งโโ๏ธ๐คฏ๐ค
!WEIRD !HOPE !PIZZA !WINEX !ALIVE
Most dev teams that I know usually don't have sufficient people to do everything that needs doing, so when issues arise, it definitely throws a wrench in the plans. ๐๐๐โจ๐ค
!ALIVE
!HOPE
!INDEED
!PIZZA
!WINE
!WEIRD
I think that's the case here on Hive, but not on "real-life" software companies. ๐คฏ๐
!PIZZA
!LOLZ
It's true of every blockchain of which I'm a part, and many other open-source projects. It's really only in a company or corporation where this would not so often be the case. I'm not interested in software from most of those. ๐๐๐โจ๐ค
!LOLZ
!PIZZA
Nearly all of the FOSS dev teams (such as those on blockchains) that I found online are made up only of volunteer devs !INDEED. ๐ค
!LOLZ
View or trade BEER.
Hey @savvyplayer, here is a little bit of BEER from @tydynrain for you. Enjoy it!
Learn how to earn FREE BEER each day by staking your BEER.