Showing posts from January, 2014

RIF Notes #25

“Most managers want good code, even when they are obsessing about the schedule. They may defend the schedule and requirements with passion; but that’s their job. It’s your job to defend the code with equal passion” – Bob Martin IE -Tracking Protection Lists - IE has the a bunch of tracking prevention providers. What’s the Problem with Mobile HTML5 -“A recent research concludes that contrary to the general belief performance is not the main problem with HTML5 but rather the missing of profiling and debugging tools and the lack of certain APIs” Organization Antipattern: Project Teams – This post explored the “No Project” movement and compares the Project team vs. Product Team construction. Is College Worth It? The New Turbo Button - Balancing Power Management and Performance on Windows Servers -“Recently Mike Harder, a development manager, noticed that stuff he does every day was taking longer on the "Balanced" power option than the "High Performance" option”

RIF Notes #24

-“The best way to motivate geeks is to not demotivate them” BoundedContext -Martin Fowler explains the concept of the Bounded Context. Clean Code Cheet Sheet - A cheat sheet for all of the principles and guidance for righting Clean Code. Applying the 80:20 Rule in Software Development - Various ways the 80/20 rule applies to software development. Technical Disobedience – “In software, it is far to easy to accept the system around you as status quo. It is harder to realize that software is soft, and that systems can be soft as well. There are many small rules you can try and hack around to get things done.” The future of the business desktop - Rocky’s thoughts on the desktop PC and its position within the enterprise and what that means as a platform for enterprise developers. Why teams don't work - Harvard Business journal about team dynamics. Victory Lap for Ask Patents – Joel Spolsky’s anti patent troll effort. Singing the Password Blues -“Passwords are so 1999, and dua

RIF Notes #23

“There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult.” - C.A.R. Hoare (British computer scientist, winner of the 1980 Turing Award) On Types – Ted Neward makes in interesting suggestion about how types should be handled. As a suggestion, then, I throw out this idea: Ensure that all of your domain classes never expose primitive types to the user of the system. In other words, Name never exposes an “int” for Age, but only an “Age” type. C# makes this easy via “using” declarations, like so: using FirstName = System.String; using LastName = System.String; Web Developer Checklist – This is a very handy and thorough checklist of items to be checked on you website for quality, security, usability, etc. ';--have i been pwned? – Troy Hunt has set up a sight that allows you to see