Modern email clients try to safeguard us from malicious code injected in HTML emails. They might help by flagging suspicious looking senders, or hiding embedded images. But getting junk email is like being forced to visit some weird Russian site offering BitCoins. How many of us still maintain “oh but we don’t visit shady sites so there’s no real risk”? And yet, when someone with malicious intent can send this to us directly, we expect the amazingly dated browser in what, Outlook to keep us safe?
Category: Further reading
A modern classic, one could say. Dan McKinley about the perils of early adoption:
One of the most worthwhile exercises I recommend here is to consider how you would solve your immediate problem without adding anything new. First, posing this question should detect the situation where the “problem” is that someone really wants to use the technology. If that is the case, you should immediately abort.
Niche Software writes a blog in defense of the XML format. To be honest, I’m guilty of this. I hate XML documents that are verbose and unsightly.
However, should poor use of XML, even if widespread, be sufficient for us to abandon use completely? Especially when the very flexibility — extensibility — of XML has allowed it to be misused in the first place.
Great talk from Christin Gorman about making code just complex enough. (Her ranting about interfaces reminds of my everyday job.)
Excellent piece, poor title. Curtis Poe writes about the importance of understanding relational databases:
Your application is all about data. For many people in management, they see the app or the web page, but they don’t see the database hidden underneath. They understand that without their data the company is probably in serious trouble, but they don’t give much thought to it. In fact, while total data loss will probably bankrupt your company, few give much thought to the the standard data quality issues that are a constant financial drain because it’s assumed to be part of the cost of doing business. And the developers who don’t understand how to use databases often tell management “that’s just the way this technology works.”
Some good tips on how to do code reviews from Google Testing Blog:
Code reviews can slow down an individual code change, but they’re also an opportunity to improve your code and learn from another intelligent, experienced engineer. How can you get the most out of them?