| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next


Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

C-ORM: docs, API.

Last 100 entries

M John Harrison; Playing Games on a Cloud GPU; China Gamifies Real Life; Can't Help Thinking It's Thoughtcrime; Mefi Quotes; Spray Painting Bike Frame; Weeks 10 + 11; Change: No Longer Possible To Merge Metadata; Books on Old Age; Health Tree Maps; MRA - Men's Rights Activists; Writing Good C++14; Risk Assessment - Fukushima; The Future of Advertising and Surveillance; Travelling With Betaferon; I think I know what I dislike so much about Metafilter; Weeks 8 + 9; More; Pastamore - Bad Italian in Vitacura; History Books; Iraq + The (UK) Governing Elite; Answering Some Hard Questions; Pinochet: The Dictator's Shadow; An Outsider's Guide To Julia Packages; Nobody gives a shit; Lepton Decay Irregularity; An Easier Way; Julia's BinDeps (aka How To Install Cairo); Good Example Of Good Police Work (And Anonymity Being Hard); Best Santiago Burgers; Also; Michael Emmerich (Vibrator Translator) Interview (Japanese Books); Clarice Lispector (Brazillian Writer); Books On Evolution; Looks like Ara (Modular Phone) is dead; Index - Translations From Chile; More Emotion in Chilean Wines; Week 7; Aeon Magazine (Science-ish); QM, Deutsch, Constructor Theory; Interesting Talk Transcripts; Interesting Suggestion Of Election Fraud; "Hard" Books; Articles or Papers on depolarizing the US; Textbook for "QM as complex probabilities"; SFO Get Libor Trader (14 years); Why Are There Still So Many Jobs?; Navier Stokes Incomplete; More on Benford; FBI Claimed Vandalism; Architectural Tessellation; Also: Go, Blake's 7; Delusions of Gender (book); Crypto AG DID work with NSA / GCHQ; UNUMS (Universal Number Format); MOOCs (Massive Open Online Courses); Interesting Looking Game; Euler's Theorem for Polynomials; Weeks 3-6; Reddit Comment; Differential Cryptanalysis For Dummies; Japanese Graphic Design; Books To Be Re-Read; And Today I Learned Bugs Need Clear Examples; Factoring a 67 bit prime in your head; Islamic Geometric Art; Useful Julia Backtraces from Tasks; Nothing, however, is lost with less discomfort than that which, when lost, cannot be missed; Article on Didion; Cost of Living by City; British Slavery; Derrida on Metaphor; African SciFi; Traits in Julia; Alternative Japanese Lit; Pulic Key as Address (Snow); Why Information Grows; The Blindness Of The Chilean Elite; Some Victoriagate Links; This Is Why I Left StackOverflow; New TLS Implementation; Maths for Physicists; How I Am 8; 1000 Word Philosophy; Cyberpunk Reading List; Detailed Discussion of Message Dispatch in ParserCombinator Library for Julia; FizzBuzz in Julia w Dependent Types; kokko - Design Shop in Osaka; Summary of Greece, Currently; LLVM and GPUs; See Also; Schoolgirl Groyps (Maths); Japanese Lit; Another Example - Modular Arithmetic; Music from United; Python 2 and 3 compatible alternative.; Read Agatha Christie for the Plot; A Constructive Look at TempleOS; Music Thread w Many Recommendations; Fixed Version; A Useful Julia Macro To Define Equality And Hash

© 2006-2015 Andrew Cooke (site) / post authors (content).

I Am Not A Clever Man

From: andrew cooke <andrew@...>

Date: Tue, 22 May 2012 18:44:55 -0400


Another project draws to a close at work; here at home Lepl is becoming more
of a burden.

I am not a great programmer.  I'm a pretty good programmer, but I keep making
the same stupid mistake: I rely too much on my ability to code my way out of a
hole.  My code becomes bloated, top-heavy and hard to maintain.

At work I have an excuse - faced with unclear requirements I implement all
possible alternatives.  Recently I deleted a slew of code that provided
synthetic data to replace hardware failures (in software to do calibrations of
said hardware).  OK, so that's not quite as crazy as it sounds (I'll spare you
the details), but in retrospect it was wasted work - we aren't calibrating
synthetic data...

But at home?  What is the excuse for Lepl?  I guess it's just fun - piling
concept on top of concept.  Doing lots of stuff.  Carefully balanced code that
can go this way or that.  Dense, dense, dense.

Neutron star dense.  Tending to gravitational collapse.

How do I fix this?  I don't know.  I just sat down and looked at some recent
code.  A new project.  It's already complex.  It does a lot.  How can I make
it do less?  I guess I don't need an embedded web server in a command line
utility.  There was a reason for that.  I guess it wasn't a good enough one.

I need simplicity.  I need to stop coding like a clever man.


Re: translating lettuce feature files into stub steps files

From: andrew cooke <andrew@...>

Date: Mon, 23 Sep 2013 21:00:47 -0300

I don't know anything about lettuce

If you're asking for advice about what would be a good, simple, pure python
parser, I don't know.  These days I tend to just write what I need as a simple
recursive descent parser.  There's always pyparsing (but I disliked that
enough to write Lepl...)


translating lettuce feature files into stub steps files

From: "Eric Silber (erisilbe)" <erisilbe@...>

Date: Mon, 23 Sep 2013 23:47:01 +0000

The author of Lettuce has it in mind to update lettuce parsing , but there =
is not a schedule for that.
Your Lepl project seemed promising in that regard.  If that is not the way =
to go , do you know of
any currently active project supporting the translation of lettuce feature =
files into steps.py files?
The goal is to be able to read an agile user story authored by a non-progra=
and output a stub steps.py  implementation

Comment on this post