Archives, eh
-
# Links for 2008-07-07
- Worth Enough 2500 (JPEG Image, 2500×3334 pixels)
Wish I knew the story behind this image, if it is standalone or if there is some story/article that goes with it ✴ - Fresh and Illustrative User Interface Design Patterns ✴
- Pretty blocks in Rails views ✴
- Redesign your site in place using Rails custom mime types ✴
- Worth Enough 2500 (JPEG Image, 2500×3334 pixels)
-
# Links for 2008-06-13
- Common REST Design Pattern | Architects Zone ✴
- .NET Naming Conventions and Programming Standards (C#.Net, VB.Net, J#.Net) and Best Practices – irritatedVowel.com Programming ✴
- It’s common sense, stupid: No, OOP doesn’t Fail Us ✴
- Building a Ruby on Rails application in a week « 41 technologies ✴
- Moving Past BlueCloth ✴
- iBanjo » Blog Archive » Programmer Insecurity ✴
- Michael Feathers’ Blog: The Flawed Theory Behind Unit Testing ✴
-
# Links for 2007-08-16
- Instructables Solar Thermal Water Heater For Less Than Five Dollars ✴
- If it has feathers and quacks, is it really a web 2.0 platform? – Project Zero ✴
- ASP.NET without ASP.NET – Writing a full JSON Serializer in 100 lines of C# code ✴
- Long Bets ✴
- WorldChanging: Tools, Models and Ideas for Building a Bright Green Future: Colonizing Planet Earth ✴
-
# Links for 2007-02-26
- Cute little simple scheduling code hack – comp.lang.ruby | Google Groups
Very Rubyesque ✴
- Cute little simple scheduling code hack – comp.lang.ruby | Google Groups
-
# Pick a method and stick to it
new System.Text.UTF8Encoding()).GetBytes( text )Pretty simple snippet of code, neh? Can’t cause too many problems. Except the .NET Framework 1.1 returns a byte array subtly different to the one returned by the same call in the .NET Framework 2.0. Joy!
Even better, because there is no linker for .NET code you cannot simply create an assembly compiled against the 1.1 Framework and reference it in an application compiled against the 2.0 Framework. Your assembly will just use the 2.0 Framework.
Bah! I had to use remoting. Just because the .NET Framework team couldn’t keep a consistent approach to converting strings to byte arrays. Bah!
