You're Probably Using the Wrong Dictionary An Essay by James Somers jsomers.net As if a word were no more than coordinatesAnother mind as alive as yoursA soft and fitful lusterPathosAn affection for words Webster's Dictionary, 1913 Edition languagewriting
A brief foray into vectorial semantics An Article by James Somers jsomers.net One of the best (and easiest) ways to start making sense of a document is to highlight its “important” words, or the words that appear within that document more often than chance would predict. That’s the idea behind Amazon.com’s “Statistically Improbable Phrases”: Amazon.com’s Statistically Improbable Phrases, or “SIPs”, are the most distinctive phrases in the text of books in the Search Inside!™ program. To identify SIPs, our computers scan the text of all books in the Search Inside! program. If they find a phrase that occurs a large number of times in a particular book relative to all Search Inside! books, that phrase is a SIP in that book. mathmeaningwordsnotetakingsearchchance
Learning About Work Ethic From My High School Driving Instructor An Essay by James Somers www.theatlantic.com Should we really demand that the guy who checks ticket stubs at the movie theater hones his craft? Well, yes. No job is too low to not warrant care, because no job exists in isolation. Carelessness ripples. It adds friction to the working of the world. To phone it in or run out the clock, regardless of how alone and impotent you might feel in your work, is to commit an especially tragic—for being so preventable—brand of public sin. Bob [the driving instructor] oozes concern; he wants to infect the state of New Jersey with good driving habits. He respects his public role, the fact that the minute he's done with these kids they head straight for their parents' car keys and out onto the roads we share. When I asked him what he likes to do outside of work, he laughed: "This is my life." His reward is the pleasure of depth itself. craftworkethics
Feature parity An Article martinfowler.com Whilst Feature Parity often sounds like a reasonable proposition, we have learnt the hard way that people greatly underestimate the effort required, and thus misjudge the choice between this and the other alternatives. For example even just defining the 'as is' scope can be a huge effort, especially for legacy systems that have become core to the business. Most legacy systems have 'bloated' over time, with many features unused by users (50% according to a 2014 Standish Group report) as new features have been added without the old ones being removed. Workarounds for past bugs and limitations have become 'must have' requirements for current business processes, with the way users work defined as much by the limitations of legacy as anything else. Rebuilding these features is not only waste it also represents a missed opportunity to build what is actually needed today. These systems were often defined 10 or 20 years ago within the constraints of previous generations of technology, it very rarely makes sense to replicate them 'as is'. softwarefeaturesrepair