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

C[omp]ute

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

Calling C From Fortran 95; Bjork DJ Set; Z3 Example With Python; Week 1; Useful Guide To Starting With IJulia; UK Election + Media; Review: Reinventing Organizations; Inline Assembly With Julia / LLVM; Against the definition of types; Dumb Crypto Paper; The Search For Quasi-Periodicity...; Is There An Alternative To Processing?; CARDIAC (CARDboard Illustrative Aid to Computation); The Bolivian Case Against Chile At The Hague; Clear, Cogent Economic Arguments For Immigration; A Program To Say If I Am Working; Decent Cards For Ill People; New Photo; Luksic And Barrick Gold; President Bachelet's Speech; Baltimore Primer; libxml2 Parsing Stream; configure.ac Recipe For Library Path; The Davalos Affair For Idiots; Not The Onion: Google Fireside Chat w Kissinger; Bicycle Wheels, Inertia, and Energy; Another Tax Fraud; Google's Borg; A Verion That Redirects To Local HTTP Server; Spanish Accents For Idiots; Aluminium Cans; Advice on Spray Painting; Female View of Online Chat From a Male; UX Reading List; S4 Subgroups - Geometric Interpretation; Fucking Email; The SQM Affair For Idiots; Using Kolmogorov Complexity; Oblique Strategies in bash; Curses Tools; Markov Chain Monte Carlo Without all the Bullshit; Email Para Matias Godoy Mercado; The Penta Affair For Idiots; Example Code To Create numpy Array in C; Good Article on Bias in Graphic Design (NYTimes); Do You Backup github?; Data Mining Books; SimpleDateFormat should be synchronized; British Words; Chinese Govt Intercepts External Web To DDOS github; Numbering Permutations; Teenage Engineering - Low Price Synths; GCHQ Can Do Whatever It Wants; Dublinesque; A Cryptographic SAT Solver; Security Challenges; Word Lists for Crosswords; 3D Printing and Speaker Design; Searchable Snowden Archive; XCode Backdoored; Derived Apps Have Malware (CIA); Rowhammer - Hacking Software Via Hardware (DRAM) Bugs; Immutable SQL Database (Kinda); Tor GPS Tracker; That PyCon Dongle Mess...; ASCII Fluid Dynamics; Brandalism; Table of Shifter, Cassette and Derailleur Compatability; Lenovo Demonstrates How Bad HTTPS Is; Telegraph Owned by HSBC; Smaptop - Sunrise (Music); Equation Group (NSA); UK Torture in NI; And - A Natural Extension To Regexps; This Is The Future Of Religion; The Shazam (Music Matching) Algorithm; Tributes To Lesbian Community From AIDS Survivors; Nice Rust Summary; List of Good Fiction Books; Constructing JSON From Postgres (Part 2); Constructing JSON From Postgres (Part 1); Postgres in Docker; Why Poor Places Are More Diverse; Smart Writing on Graceland; Satire in France; Free Speech in France; MTB Cornering - Where Should We Point Our Thrusters?; Secure Secure Shell; Java Generics over Primitives; 2014 (Charlie Brooker); How I am 7; Neural Nets Applied to Go; Programming, Business, Social Contracts; Distributed Systems for Fun and Profit; XML and Scheme; Internet Radio Stations (Curated List); Solid Data About Placebos; Half of Americans Think Climate Change Is a Sign of the Apocalypse; Saturday Surf Sessions With Juvenile Delinquents; Ssh, tty, stdout and stderr; Feathers falling in a vacuum; Santiago 30m Bike Route

© 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

http://buttersafe.com/2008/10/23/the-detour/

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.

Andrew

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
https://github.com/gabrielfalcao/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...)

Sorry,
Andrew

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=
mmer
and output a stub steps.py  implementation

Comment on this post