I’ve a nagging feeling my coding skills are getting rusty

The Mitochondrion coding process seems to run something like this:

7 pm – 9 pm: Work on the 40 Mb spreadsheet that mangles the data from the patterns into the code that loads the data onto the Picaxe. There are four unevenly asynch counters here to do the mangling. Code from spreadsheet not working.
9 pm: Give up, shower, food, paper, wow.
10.30: Go to bed
10.35: Realise I can concat that chunk and that chunk, making spreadsheet one third the size
10.40: Realise I can autogenerate two of the four counters
10.37: No wait, three of the four. Woo!
10.44: Realise I can put that and that together to generate the constants table as well
10.47: You know, this would be better as a PERL script
10.48: Or maybe Ruby
10.49: I should rewrite the entire system in LISP
10.50: Realise I can’t concat that chunk at all, making entire set of brainwaves irrelevant. Bother.
10.51: Get kicked by for wriggling too much

12 thoughts on “I’ve a nagging feeling my coding skills are getting rusty”

    1. In the light of the morning, it turns out that there are a few simple things I can do to both the spreadsheet and the memory loader that should make the spreadsheet approach lots easier. Of course, I’m too busy to test this until the weekend, so may have thought of an entirely different way to do it by then…

    1. Especially as I’ve only ever used LISP for writing unit tests and I don’t think I’m actually smart enough to grok the LISP way of doing things.

      1. Oh yeah, my theory for why LISP is considered the best way to program anything? It’s sufficiently hard on a conceptual level that only the best programmers will ever use it. Thus, when awesome code is written in LISP, that has little to do with the language and more to do with the programmers.

        I’m sure you could take the same set of programmers, make them code in BASIC and they’d still produce awesome code.

        (Okay, the awesome code might be for their killer robots to hunt you down for making them use BASIC, but my point remains.)

        1. but LISP is fun!

          uhh..

          We use the Scheme dialect as a scripting interface to OpenCog – which actually makes things incredibly simple for representing graph structures.

          I’m still hanging out for one of our GSoC students to finish the Python bindings though.

          1. Yeah, but you’re better at this kind of stuff than me. Quite a lot better.

            (I could totally take you in a laser welding deathmatch though.)

  1. I leaped out of bed recently realising I’d misread the timer2 section of the uC datasheet, and re-read it, and read my code, and then realised I was on crack and it was fine.

    I need to do less leaping out of bed when Code Madness hits.

Leave a Reply

Your email address will not be published. Required fields are marked *