HTML5 Shiv

HTML5 has all sorts of great new elements such as <header>, <nav>, etc.  We can finally build pages without having tons of <div class=”header”> etc, and have the terms standardized across websites.

Internet Explorer will not recognize these unofficial elements.  Unlike Chrome, Firefox, Opera, and the rest of the browser world who will gladly assume the element is acceptable, and render / CSS just like any other element — Internet Explorer ignores them.  If you used <header> tags on your site, Internet Explorer (yes, even 8 ) will just ignore the existence of the code.

To use this script, it must be included before the <body> element (i.e. in the <head>) but doesn’t matter if it appears before or after the CSS – but for the sake of performance, it would make better sense to include the CSS first then this script.

<!--[if lt IE 9]><script src="//html5shiv.googlecode.com/svn/trunk/html5.js"></script><![endif]-->

Note that the protocol has been removed so you don’t have to when including on an http or https page

Common question: what’s the difference between the html5shim and the html5shiv? Answer: nothing, one has an m and one has a v – that’s it.

BV Engineering, Agile

But why?  Two reasons.
First, Scrum is a framework, and purposefully does not attempt to define the engineering practices that the team should use in building the product.   Scrum assumes that these engineering practices are not perfect.  And assumes that the imperfections will show up in the Impediments List.  And, when an impediment rises to the top, it will be fixed.
So, I want all the stuff around Business Value to be treated the same way. All the ideas, all the people, all the tools, all the process.  It needs to be continuously improved.  And items need to go on the Impediments List. And then get fixed!  So, I want BV Engineering to be amongst the engineering practices we are continuously improving.
Second, I have colleagues that have some wonderful ideas about Business Value.  Good, big concepts. Or other ideas.

Preview Tab in Visual Studio 11

How many times have you found that your document tab well overflows with open documents?  Every time you “Go To Definition” or open a search result in another file, that file will be opened.   And that file will remain open until it’s explicitly closed in the editor by the developer.  This is true even when the need for that file was temporary, when it was only needed in order to preview the target content.

Enter the Visual Studio 11 Preview Tab.  The Preview Tab sits on the right-hand side of the document window and is used over and over again anytime such a preview is needed:

This greatly helps to reduce the clutter we’ve all experienced in the Visual Studio document windows.  If you do want previewed content to be more permanent, with a single click you can “promote” the current file from the preview tab into a full-fledged code window.

About Sina App Engine

Sina App Engine(以下简称SAE)是新浪研发中心于2009年8月开始内部开发,并在2009年11月3日正式推出第一个Alpha版本的国内首个公有云计算平台(http://sae.sina.com.cn),SAE是新浪云计算战略的核心组成部分。     

    SAE作为国内的公有云计算,从开发伊始借鉴吸纳Google、Amazon等国外公司的公有云计算的成功技术经验,并很快推出不同于他们的具有自身特色的云计算平台。SAE选择在国内流行最广的Web开发语言PHP作为首选的支持语言,Web开发者可以在Linux/Mac/Windows上通过SVN、SDK或者Web版在线代码编辑器进行开发、部署、调试,团队开发时还可以进行成员协作,不同的角色将对代码、项目拥有不同的权限;SAE提供了一系列分布式计算、存储服务供开发者使用,包括分布式文件存储、分布式数据库集群、分布式缓存、分布式定时服务等,这些服务将大大降低开发者的开发成本。同时又由于SAE整体架构的高可靠性和新浪的品牌保证,大大降低了开发者的运营风险。另外,作为典型的云计算,SAE采用“所付即所用,所付仅所用”的计费理念,通过日志和统计中心精确的计算每个应用的资源消耗(包括CPU、内存、磁盘等)。     

    总之,SAE就是简单高效的分布式Web服务开发、运行平台。