.NET Productivity Sucks

I am being deliberately provocative in my headline, but a co-worker and I were commenting to each other that we felt that we were becoming less productive in .NET. On the whole, we do not think it is our fault.

Our current project uses the Prism framework. Only one member of our team can claim to be extremely versatile using this framework – the promise is that it allows developers to build applications that are easier to maintain.

Some members of the team are on a learning curve, but it seems to be a challenge for them. I experience the same thing a year ago on another project that was using Model-View-Presenter. In theory, the benefits are clear. In practice, not so clear yet. I find that I spend a lot of time learning and/or teaching, and I wonder what it will be like when we add new or different developers to the team.

I get tired of type errors in .NET – I have felt for a long time that the compiler is trying to protect me from making errors I would never make. But, I do not have have anything coherent to say about that right now. I just want to cite an interesting article that states that developers are more productive using Django than they are using .NET.

I have nothing to add – just want to say: I am feeling less productive in .NET than I used to. I like Python – I used it on a project over the summer. It felt great to deliver working code every day. Is it just me?

Syllables Matter

The software I am writing for Dr. Kelly calculates a Flesch-Kincaid grade level for every assignment he grades. The formula is straight forward enough.

However, I was surprised to find that different implementations of this formula diverge dramatically from each other. The same text can have wildly different grade levels depending on the software you use.

For example, Microsoft word says that this blog entry reads at the grade 7  level, but another implementation says that it reads at a grade 9 level. Who is right? How does this happen?

It turns out that writing code to count the syllables in a word is not an easy thing. Early this summer, I tried to use the natural language toolkit to count the syllables in a word, but the code did not work. I threw the problem into the too-hard-basket for a while, and came back to it last week. A new version has been posted, and it works. It was patched by Alex Rudnick.

Here are two lines of code that show you how easy it is to count syllables in a word using the NLTK:

>>> from nltk_contrib.readability.textanalyzer import syllables_en
>>> print syllables_en.count("hello")

If you get the latest version of nltk_contrib, you will have no problems. However, I did find one small problem. This code insists that the word ‘the’ has zero syllables. The fix was easy enough, but I am not sure this how the maintainers would fix it:

Edit the file called syllables_en.py. It contains a list of so-called special syllables called specialSyllables_en. Add ‘the’ to the list, and specify that it has one syllable.

It is easy to see how this list works. For example “Mr.” has two syllables, but there is no easy way to figure out that “Mr.” is pronounced as “mister.” I may find other exceptions as I go.

However, having fussed with code, and having downloaded the latest version, I am pleased to report that the flesch-kincaid score I generate matches the score that is generated by Microsoft Word. My syllable count is correct, and the rest just follows.

My code will probably never agree perfectly with the score that is generated with Microsoft Word. It turns out that some English words are pronounced with a different number of syllables by English speakers from different parts of the world. Also, the code in the natural language toolkit is sometimes wrong. For example, it says that the word ‘calculates’ has four syllables. However, it is close enough in a great majority of cases. You should give it a try.

Writing to Be Understood

Since early June, a professor from Carleton University and I have been designing and building software to help people write more clearly. Professor John Medicine Horse Kelly is a journalism professor who won a teaching award for a system of instruction he developed during his twenty years of teaching.

He is an interesting man, humble and soft-spoken. He is a natural listener, and he will listen to almost anything you have to say with a gentle and sympathetic smile. But, if you can stop talking and start listening, he will fill any silence you create with lovely stories about his grandfather, Peter Kelly, or Bill Reid, or any of his Haida relatives and friends. His soft-spokeness masks deep passions. One is teaching.

He has developed a system for teaching students to write well by identifying patterns that students can edit to improve their writing. I have written code that uses the natural language toolkit to read student’s assignments and to identify these patterns. Even I have learned to apply Dr. Kelly’s principles to create writing that is clear, lively and easy to understand. Here are things to watch for:

1. If you use Microsoft Word, use the grammar and style tools to check the Flesch Kincaid grade level.
2. Use the grammar and style tools to find and eliminate passive sentences.
3. Ensure that your writing is composed of words that have an average of about 4.5 characters.
4. Write paragraphs that have an average of about 2.5 to 3.5 sentences.
5. Write sentences that have an average of between 12 and 15 words per sentences.
6. Avoid using too many prepositions. Prepositions cause writing to become complex and hard to read.

I was able to improve this article by using our tool. The first draft of this blog entry read at the grade 10.5 level, and it contained several complexifiers. I was able to eliminate these words, and my writing improved. The draft you are now reading reads at a grade 8.6 level. As I use Dr. Kelly’s system, I see that it works.

Plain writing is important. People can find it hard to understand medical consent forms, legal documents, and privacy policies. Is it ethical to write important documents that ordinary people cannot understand? Is it smart?

In the next few weeks, I am going write about our tool. We call it WISE – Writing Instruction Software for Educators. Recently, we realized that we may have to call it Writing Instruction Software for Everyone. Who knows, if the code is easy to use, and if the principles can be easily explained, we may share the code with anybody who wants to try it. We have to get some legal advice first, but we hope to make a file available for download some time between now and Christmas.

« Previous Entries