Log in

No account? Create an account
04 May 2016 @ 09:31 pm
4 May 16  
very clever, if somewhat crazy, code at work.
same after, in fact.
sprockets, sockets, grommets & gasketsrandomdreams on May 5th, 2016 02:40 pm (UTC)
I love this.
But man, I'm also so learning the truth of the assertion that since debugging is harder than writing code, if you write the cleverest code you can, you're unable to debug it.
Martin Tithoniumtithonium on May 5th, 2016 03:35 pm (UTC)
I admit, in the post-work minecraft code, I spent 20 minutes trying to figure out why it was suddenly deleting /all/ the marked points instead of just the ones it had found in the first cycle... turned out I had rescoped a couple variables and so it was being /told/ to delete everything. oops.

As for the work stuff.. basically, I'm hiding a bunch of ugly remote data access behind stuff that was /originally/ intended to be pseudocode. It's not perfect, but it gets the job done until I can rewrite it to do things right. The important thing is to make sure I'm doing things /correctly/, rather than /right/. I'll be testing that part today.
sprockets, sockets, grommets & gasketsrandomdreams on May 5th, 2016 03:39 pm (UTC)
I like that distinction, yes.
I was fighting with something similar, and trying to describe to a hardware guy that with complex software/hardware, just because you're getting the right result doesn't necessarily mean you're doing the right thing.