We used to have tools that could be used to build a CRUD application from scratch in a few hours (minutes for a trivial one). Delphi and Visual Basic 6 were widely used by domain experts to hammer out a workable tool. Then Microsoft got obsessed with .NET because they thought everyone was going to bail on the X86, and used it as an excuse to kill off VB6. The shift to "professional" programming tools really just adde…
Ask HN: What are the “lost arts” of our field?
21–24 of 24 posts
Re: Ask HN: What are the “lost arts” of our field?
#22Re: Ask HN: What are the “lost arts” of our field?
#23Back in my day... probably not technically a lost art, but an interesting lesson in math. I remember I was in computer science class. I was 17 years old. And the teacher taught us how to read binary and how to calculate it. He said binary was math which is a universal language that even aliens could understand and would allow us to communicate though we'd still run into the struggle of converting that binary to actua…
Tangentially related: storing a bitmask in your database (as a single 32-bit value) to track many flags, and using bitwise math to manipulate/interpret it. Much more space efficient than what everyone would do now (a bunch of tinyints, enums, or booleans) but obviously you’d be rightly fired out of a cannon now for introducing something so difficult to grasp for young devs, just to save “cheap” memory and storage.
They are also very fragile
Far better to have some maintainable and extendable (what happens when you exceed 32 binary flags?) than being overly clever for the sake of saving a couple bytes of storage
Re: Ask HN: What are the “lost arts” of our field?
#24Earlier quoted context omitted.
Tangentially related: storing a bitmask in your database (as a single 32-bit value) to track many flags, and using bitwise math to manipulate/interpret it. Much more space efficient than what everyone would do now (a bunch of tinyints, enums, or booleans) but obviously you’d be rightly fired out of a cannon now for introducing something so difficult to grasp for young devs, just to save “cheap” memory and storage.
Bit masks are cool They are also very fragile Far better to have some maintainable and extendable (what happens when you exceed 32 binary flags?) than being overly clever for the sake of saving a couple bytes of storage