Include Python USB code.

The Software Design Group does research in many areas of software engineering, including: design languages and analysis, extraction of designs from code, checking conformance of code to designs, and automatic test case generation.

Dr W Edwards Deming, 1982 & 1986, Out of the crisis: quality, productivity and competitive position , Cambridge University Press, Cambridge.

The 14 points are a basis for transformation of [American] industry. Adoption and action on the 14 points are a signal that management intend to stay in business and aim to protect investors and jobs. Such a system formed the basis for lessons for top management in Japan in 1950 and in subsequent years.

The 14 points apply anywhere, to small organisations as well as to large ones, to the service industry as well as to manufacturing. They apply to a division within a company.

Vankatesh Rao

Jim Gray

Device-based approach to hypertension.

By Vankatesh Rao

How to make a baseball cap for your banana...

I really love @oatmeal's ode to Tesla: "Why Nikola Tesla was the greatest geek who ever lived"

A good reminder on intellectual snobbery

Vankatesh Rao in Forbes

John Birmingham

What you’ve stumbled upon here is a project that intends to make retrieving, massaging, populating, viewing, and editing data in JavaFX UI controls easier. It’s all that boring kludge work you have to do between getting user requirements and delivering a rich user experience. We hope that this project helps primarily in two separate areas.

Hilarious.

All of Earth's Water in a Single Sphere

Article on Bloomington life science industry, including Cook Medical.

Your life does not begin when...

ai-class prereq video playlists

Two things have happened recently that are linked. One very small and insignificant and the other momentous, and a great loss to New Zealand. First, the small thing. We were asked, via this blog, “will straight As get me a job?”. The other: at at his home on Saturday, 24 March 2012, Sir Paul Callaghan died.

Thirty years after its creation, C remains one of the most widely used systems programming languages. Unfortunately, the power of C has become a liability for large systems projects, which are now focusing on security and reliability. Modern languages and static analyses provide an opportunity to improve the quality of systems software, and yet adoption of these tools has been slow.

To address this problem, we propose a new language called Ivy that has an evolutionary path from C. The mechanism for this evolutionary path is a system of extensions and refactorings: extensions augment the language with new features, and refactorings assist the programmer in updating their code to use these new features. Extensions and refactorings have a wide variety of applications, from enforcing memory safety to detecting user/kernel pointer errors. We also demonstrate Macroscope, a tool we have built to enable refactoring of existing C code.

David Dobbs' 'Orchid Hypothesis'

There have been major advances in programming languages over the last 20 years. Given this, it seems appropriate to ask why systems programmers continue to largely ignore these languages. What are the deficiencies in the eyes of the systems programmers? How have the efforts of the programming language community been misdirected (from their perspective)? What can/should the PL community do address this?

As someone whose research straddles these areas, I was asked to give a talk at this year's PLOS workshop. What follows are my thoughts on this subject, which may or not represent those of other systems programmers.

Just came across this great P.P.S. in a Hemingway letter: