David Acevedo's Blog

As a teen, I used to play Dungeons and Dragons (D&D) with my friends. This started an interest in the medieval period that led to me taking a medieval history class in college just to understand the period more. Over the years I've also read great books like " Dungeon, Fire and Sword " about the crusades (I recommend the book) and yet with all that knowledge it wasn't until recently that it occurred to me I had a completely wrong understanding of economics in the Medieval Period. "Viking helmets, sword and footwear" by eltpics is licensed under CC BY-NC 2.0 In my D&D games, players who are adventures battling monsters and creatures would need equipment and on the trips to town, they'd get resupplied with their adventuring necessities. I'd run these moments referencing my imagination of what it must have been and fantasy books I'd read. There be an inn with a raucous bar, a gruffly black-smith, if a city also a weapon and armor sm

In my time in government, I've worked on modernizing legacy systems. Though not all legacy systems are worth modernizing, I've found a few "classic" languages in the process that are not the ones you'd expect. All these "classic" languages share a few things: They're all proprietary. They all had or have enterprise support They all have outdated UI (user interface) elements reminiscent of the '90s. Microsoft's (Visual) FoxPro    License: Proprietary Latest Release: 2007 Top on these languages I've encountered is FoxPro, a language that is unsupported now, but was back in the '90s a good language. It was bought by Microsoft and that gave it a sense of enterprise support. I encountered this language at the Environmental Quality Board in Puerto Rico, where there were two "programmers" in this language and a system running on it. The environmental complaints/issues ticketing system had been modernized not too lo