Twitter | Pretraživanje | |
Slava Pestov
Strong type systems, memory safety, automatic memory management and so on have had zero effect on software quality, because all the extra slack was consumed by new features instead
Reply Retweet Označi sa "sviđa mi se" More
Renaud.lienhart(_:) 1. velj
Odgovor korisniku/ci @slava_pestov
From experience, these make a significant difference in medium to large teams, where juniors / newcomers feel more confident working a codebase without the fear that they’ll trigger a chain reaction of load-bearing tech debt bugs.
Reply Retweet Označi sa "sviđa mi se"
🌌🧠 as a service 1. velj
Odgovor korisniku/ci @slava_pestov
Think of all the promotions though
Reply Retweet Označi sa "sviđa mi se"
Ben Pious 1. velj
Odgovor korisniku/ci @slava_pestov
Generic monomorphization and type inference can prevent this by increasing code size and compile times until it is impossible to add new features 🙃
Reply Retweet Označi sa "sviđa mi se"
Paul Cantrell 1. velj
Odgovor korisniku/ci @slava_pestov
I’m reminded of some (I heard about it so perhaps apocryphal) finding that drivers compensate for safety features on cars by driving faster, intuitively gravitating toward a more or less fixed nonzero accident rate no matter how safe their vehicles.
Reply Retweet Označi sa "sviđa mi se"
Adam Zethraeus 1. velj
Odgovor korisniku/ci @slava_pestov
Don’t be so cynical! It allowed companies to lower their hiring bar and pay less too!
Reply Retweet Označi sa "sviđa mi se"
Marcel Weiher 🇪🇺 1. velj
Odgovor korisniku/ci @slava_pestov
And the higher productivity of dynamic languages also goes towards more features. 🤷‍♂️
Reply Retweet Označi sa "sviđa mi se"
BobArmstrong 1. velj
Odgovor korisniku/ci @slava_pestov @CoherentSystems
So get CoSy . Go straight to APL level expressive power in open to the chip Forth to make what you need as lean as you need . At the APL level CoSy's modulo indexing makes memory errors something you almost have to work at .
Reply Retweet Označi sa "sviđa mi se"