11-16-2012, 01:26 PM | #1 |
Fledgling Demagogue
Posts: 2,384
Karma: 31132263
Join Date: Feb 2011
Location: White Plains
Device: Clara HD; Oasis 2; Aura HD; iPad Air; PRS-350; Galaxy S7.
|
Do Inadequate Writing Skills Engender Bad Coding?
Coder and literary editor Bernard Meisler seems to think so, according to his piece in The Atlantic Monthly:
The Real Reason Silicon Valley Coders Write Bad Software He argues that a greater emphasis on literacy will result in better software -- that, to excel at coding and design, a software programmer must first master the art of writing lucid prose. Last edited by Prestidigitweeze; 11-16-2012 at 01:35 PM. |
11-16-2012, 01:50 PM | #2 |
Wizard
Posts: 1,358
Karma: 5766642
Join Date: Aug 2010
Device: Nook
|
Since code with bad spelling, or bad grammar or syntax doesn't compile and run, I don't really see the connection.
Programmers need to master programming logic, and math certainly helps a lot on that, but writing lucid prose is for the guy who writes the help file (which should not be the programmer anyway). |
Advert | |
|
11-16-2012, 01:58 PM | #3 | |
Fledgling Demagogue
Posts: 2,384
Karma: 31132263
Join Date: Feb 2011
Location: White Plains
Device: Clara HD; Oasis 2; Aura HD; iPad Air; PRS-350; Galaxy S7.
|
Quote:
He's a coder and editor who majored in literature at Brown and and then studied software design at NYU, so I thought the legion of readers, writers and programmers on Mobile Read might be interested in his thoughts. |
|
11-16-2012, 02:18 PM | #4 |
Grand Sorcerer
Posts: 19,226
Karma: 67780237
Join Date: Jul 2011
Device: none
|
I know plenty of bad English writers that are quite good coders and plenty of good English writers that can't write a sniff of code in my experience (I've been a coder off an on for more than a decade). I do believe that the structure invovled in writing good prose could be beneficial to coders in structuring both thought and logic, but I don't believe bad English skills = bad software. Bad software in my experience is based on inadequate business understanding for the problem(s) that need to be solved. I can throw as much talent as I want a business problem, but if it's ill-defined and prone to changes along the development timeline, it will be crappy.
|
11-16-2012, 02:29 PM | #5 | |
Rookie Mucker
Posts: 56
Karma: 568004
Join Date: Mar 2011
Location: NW Montana-near center of universe
Device: Pixel 7. Moto G, Kobo Glo HD, PW2, Linux PCs
|
Quote:
Most of the documentation this self taught programmer did for over 30 years was internal documentation. It was mostly done for my own benefit for maintenance purposes. I would document what in the world I was trying to do since I knew 6 months later it would take me a long time to get my mind back in the same place to change or enhance the code. I was terrible at developing external, end user documentation yet considered myself an expert working one on one with my customers teaching them how to use a system. In my view the ability to write lucid prose may not be a requirement, but it certainly should not be considered a hindrance either. |
|
Advert | |
|
11-16-2012, 02:41 PM | #6 |
Grand Sorcerer
Posts: 27,572
Karma: 193191846
Join Date: Jan 2010
Device: Nexus 7, Kindle Fire HD
|
I can understand where Meisler is coming from. It makes perfect sense to me.
|
11-16-2012, 03:26 PM | #7 |
Wizard
Posts: 2,230
Karma: 7145404
Join Date: Nov 2007
Location: Southern California
Device: Kindle Voyage & iPhone 7+
|
He's right, that most API documentation is total crap. I'd extend that belief to most technical manuals and help files.
|
11-17-2012, 07:26 AM | #8 |
The Dank Side of the Moon
Posts: 35,872
Karma: 118716293
Join Date: Sep 2009
Location: Denver, CO
Device: Kindle2; Kindle Fire
|
I agree - proper commenting, naming of variables, structures, subroutines, and documentation is key to making software useable/reusable.
|
11-17-2012, 07:29 AM | #9 |
eBook Enthusiast
Posts: 85,544
Karma: 93383043
Join Date: Nov 2006
Location: UK
Device: Kindle Oasis 2, iPad Pro 10.5", iPhone 6
|
That's really where the difference lies between professional programmers and amateur hobbyists. Hobbyists may be (and often are) good coders, but coding only forms a small part of what professional programmers actually do.
Last edited by HarryT; 11-17-2012 at 07:31 AM. |
11-17-2012, 08:43 AM | #10 |
Addict
Posts: 239
Karma: 1280000
Join Date: Oct 2010
Location: USA
Device: None
|
People need to express their thoughts clearly in many forms of writing, and in all computer programs. The ability to form clear thoughts and express them is the common denominator between good writers and good coders.
The bit about octaves is absurd. It does give an example of a point: when you are addressing an audience unknowledgeable in the subject matter, if you write or speak well they will often believe almost anything you tell them. |
11-17-2012, 08:49 AM | #11 |
Illiterate newbie
Posts: 661
Karma: 1702090
Join Date: Dec 2011
Location: Finland
Device: Sony PRS-T1
|
Literacy does help, but it's very different for artist one. I'm not sure if such literacy is even teached anywhere. One aim should be clarity and unambiguity... English isn't very good tool for these purposes. It's completely different field for anything else.
|
11-17-2012, 09:36 AM | #12 | |
Autism Spectrum Disorder
Posts: 1,212
Karma: 6244877
Join Date: Sep 2011
Location: Coastal Texas
Device: Android Phone
|
Quote:
Naturally, that means your programmers aren't going to be able to write very well, and your liberal arts majors are going to have difficulty understanding what a given function does to document it. |
|
11-17-2012, 10:22 AM | #13 |
Addict
Posts: 206
Karma: 1683142
Join Date: Nov 2012
Device: Kindle of many shapes, PIPBoy 3000
|
The main in-house programmer at the company I work for is downright terrible at writing, but when he's looking at lines of code... It's quite the opposite.
I'm sure that anyone could have a similar anecdote for and against the argument, but the plural of "anecdote" isn't "data." |
11-19-2012, 01:51 PM | #14 |
Wizard
Posts: 2,230
Karma: 7145404
Join Date: Nov 2007
Location: Southern California
Device: Kindle Voyage & iPhone 7+
|
teh, I think the disconnect is more universal than that. I think it it more like valuing the difficult tasks you know well (e.g. programming) and devaluing the tasks whose difficulty you don't understand as deeply (e.g. technical writing).
We see this all the time with artists in various media who want their works photographed. They will often use a digicam and take the image themselves, right? They value their own work but won't pay for someone else's skill. Pet peeve of mine. I imagine many software/hardware groups are like that. We did the hard thing. Now who's got a spare five minutes to write the manual? |
11-19-2012, 02:46 PM | #15 |
The Dank Side of the Moon
Posts: 35,872
Karma: 118716293
Join Date: Sep 2009
Location: Denver, CO
Device: Kindle2; Kindle Fire
|
Oh I've seen a good portion of so-called professional programmers that couldn't code their way out of a paper bag. I've worked both with them and for them over the last 30 years.
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Troubleshooting screen is bad | anywho | Amazon Kindle | 8 | 09-10-2012 11:28 AM |
I've done a very bad thing... | jlmwrite | Amazon Kindle | 29 | 01-07-2011 06:11 AM |
Is this a bad battery or what? | Dave W | Sony Reader | 9 | 01-24-2010 06:19 AM |
link bad? | sassanik | Feedback | 1 | 04-13-2009 12:25 PM |
bad card, or bad card reader, or... ? | zelda_pinwheel | Fictionwise eBookwise | 5 | 02-08-2008 10:32 AM |