RIF Notes #22

“It’s better to be wrong than vague” – Frederick Brooks Jr.

Comments

Post a Comment

Popular posts from this blog

RIF Notes #42

“In practice, problems are delegated but the power to address them is not.” - Maslach & Leiter Building the Object Model You Want with Entity Framework How you can improve your SQL with code analysis in SQL Prompt A growing number of young Americans are leaving desk jobs to farm – This is a head scratcher. Macro trends in the tech industry Technology Radar Vol 17 Essential .NET - C# 7.0: Tuples Explained – “What many folks didn’t realize when it was first introduced is that the new C# 7.0 tuple all but replaces anonymous types—and provides additional functionality.” Editor's Note – Misprint – “Any IT manager can regale you with stories of undiagnosable printer failures, but even at the home-office level printing is an exercise in fail” .NET Standard - Demystifying .NET Core and .NET Standard Devops - Continuous Data Migration Using Visual Studio and TFS
Read more

RIF Notes #4

“It is better to be feared than loved, if you cannot be both” – Machiavelli “A well-stated problem is half-solved” – John Dewey jsFiddle - Cool javascript testing tool Modernizr - Modernizr is a small and simple JavaScript library that helps you take advantage of emerging web technologies (CSS3, HTML 5) while still maintaining a fine level of control over older browsers that may not yet support these new technologies. Why We’re Going With HTML(5) Instead Of Silverlight – More on the debate between Silverlight and HTML5.  A year ago I would have said Silverlight, hands down, for LOB development, now its not quite as clear.  At least not if your users need to access your apps from their iPads and Droids. Bootstrapped, Profitable, & Proud: Braintree – Braintree Payment Technologies was the first company I contacted when I first started investigating credit card tokenization a few years back.  Remote Desktop Protocol (RDP) -- Technical Analysis - Matt found this article, for an
Read more

RIF Notes #1

"If it is fast and ugly, they will use it and curse you; if it is slow, they will not use it." - David Cheriton in _The Art of Computer Systems Performance Analysis “The basic advice regarding response times has been about the same for thirty years [Miller 1968; Card et al. 1991]: •0.1 second is about the limit for having the user feel that the system is reacting instantaneously, meaning that no special feedback is necessary except to display the result. •1.0 second is about the limit for the user's flow of thought to stay uninterrupted, even though the user will notice the delay. Normally, no special feedback is necessary during delays of more than 0.1 but less than 1.0 second, but the user does lose the feeling of operating directly on the data. •10 seconds is about the limit for keeping the user's attention focused on the dialogue. For longer delays, users will want to perform other tasks while waiting for the computer to finish, so they should be given feedback i
Read more