Skip to main content

Speedie Memories:: Rest in Peace, Drew and Brent --

A variety of memories of Drew and Brent have been filling the web the past few days.

I often think of Drew when I think of frameworks and approaches, not just because of MaxFrame but because he had a great way of completely disagreeing with someone without making it personal - instead he made it humourous.

I remember he joked about possibly being put on a "do not invite" list for an Advisor conference after making negative comments about the Fox team's updates for the grid. His actual sessions were always packed with both attendees and information, and he was always there at other sessions, showing how much he was willing to give and still willing to learn more from others.

I appreciated so much when he would come into one of my sessions and participate through questions and comments, envigorating a room. It amazed me that even when at the back of a room, writing notes for his next session or supporting other users on new features in FoxPro, he was always aware of what was going on and participated.

And by his side, almost always, was Brent, watching, learning, coding and with them both, just as often, Irene. I first met him at the International Database Interchange in 1993 and looked forward to seeing them at every conference I attended.

Anyone who met Drew knew almost instinctively, he was more than just a great speaker and amazing developer, who loved his work, he was a great father, husband, and human being, who loved life.

Tamar marked a valuable sentiment in her tribute that I share wholeheartedly:
Drew has been one of the cornerstones of the FoxPro community for more than a decade. His family has been part of our family. It's hard to imagine our little corner of the world without Drew and Brent.

I am a richer person for having known them and send my deepest sympathies to Irene and his entire family.


Popular posts from this blog

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator)

So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinctions I…

Security in Windows 10

 discusses some Windows 10 privacy settings and their implications.

"Finally, we will access, disclose and preserve personal data, including your content (such as the content of your emails, other private communications or files in private folders), when we have a good faith belief that doing so is necessary." "In other words, Microsoft won't treat your local data with any more privacy than it treats your data on its servers and may upload your local data to its servers arbitrarily"
I did a quick install on a VM choosing the Express settings. When I fully deploy this on a real workstation, I will likely choose to wade through all of the individual pages, as David recommends.

Of course, losing one's privacy is nothing new - it's happening all over the place (despite Santa Ana's police force's lawsu…


I'm not TRYING to be "fanboy-flame bait" but what I saw yesterday was a typical "Do it this way, now do it this way and then we'll go back to this way" all over again.... a move similar to what Microsoft does to developers on an ongoing basis.

Remember the first iPhone? Smooth and curved, at least as far as it could be back then. I still pull out my 3G and can see the curves on it.

Then the 4 came out and "boxy" was all the rage. Everything should be "tight with corners"

Now iPhone 6.... smooth and curvy is back. Granted I don't have the actual device yet, but that's the message.

Guess that means the iPhone 8 will be back to boxy.

And honestly, Apple Watch is not worth "one more thing" --- especially when everyone knows it's going to be shown. "One more thing" would be something no one saw coming.  The device itself ? Very interesting and yes, definitely lots of potential but "one more thing" wor…