Hello!
The comments on this profile are unclaimed and thus are unverified.
Do they belong to you? Claim these comments.
Christine D.
Is this you? Claim Profile »
11 months ago
in Si Dawson: War Games Cracks Me the Hell Up on Si Dawson
Sometimes one no isn't enough.
1 reply
si dawson
yeah, I have many such memories. All involving women I'm about to ask out on a date. What's with that?!?
1 year ago
in Si Dawson . Com: Unit Testing - Necessary, but Not Enough on Si Dawson . Com
The accessibility thing bothers me, too. Someone needs to hack our respective languages and create a new accessibility modifier for "public, but only for testing robots. Otherwise private".
(I suppose an alternative would be to have unit tests living in the same class as the code they are testing. I dislike it in an architectural purity kind of way d: )
(I suppose an alternative would be to have unit tests living in the same class as the code they are testing. I dislike it in an architectural purity kind of way d: )
1 reply
si dawson
a couple of my testing rigs depend on conditional compilation code which is internal - it's pretty much necessary to access all the internal variables. And the overall code is so complex that without that you'd never know what was wrong.
I suppose, thinking about it, you could just wrap all the header declarations with conditional statements - then change the compile flags every time you tested.
You're right though, it's ugly & impure.
I suppose, thinking about it, you could just wrap all the header declarations with conditional statements - then change the compile flags every time you tested.
You're right though, it's ugly & impure.
1 year ago
in Si Dawson: Food Processor - Inner City Styles on Si Dawson
It's probably a little better suited to the task (;
I'm actually thinking about getting one myself. I've never owned a food processor before; and they do seem kinda handy for all sorts of things.
I'm actually thinking about getting one myself. I've never owned a food processor before; and they do seem kinda handy for all sorts of things.
1 reply
1 year ago
in Si Dawson . Com: Unit Testing - Necessary, but Not Enough on Si Dawson . Com
At the very least, code that I write which is unit tested is written in a way which is much clearer than code that isn't - if I can't easily test something, just about every time it's because there's a better way to organise things.
(And, well, I like the happy green lights that unit testing tools inevitably show up when everything is working properly <: )
Unit tests, at least, can help you make sure that the little details at the bottom keep on doing what they're supposed to / unit tests which *could* be testing the wrong thing are probably trying to test too much.
(And, well, I like the happy green lights that unit testing tools inevitably show up when everything is working properly <: )
Unit tests, at least, can help you make sure that the little details at the bottom keep on doing what they're supposed to / unit tests which *could* be testing the wrong thing are probably trying to test too much.
1 reply
si dawson
Yep, I completely agree.
I'm definitely in the "unit testing is a must" camp now. I'm just not sure they're enough
However, I am finding, even going back and writing tests afterwards, that it's making me double (and triple) check all of my logic. Plus, as you point out, tidying up everything at the bottom of the stack, and rethinking flow. It's kindof an enforced code review - which is always helpful.
The only thing I dislike is the requirement to expose so much of the interface in order to test things thoroughly. There's a stack of private methods that are really only pertinent to the inside of any given module that shouldn't be exposed.. and yet have to be. But it's a minor gripe really - particularly considering how sloppy my architecture is generally :)
I'm definitely in the "unit testing is a must" camp now. I'm just not sure they're enough
However, I am finding, even going back and writing tests afterwards, that it's making me double (and triple) check all of my logic. Plus, as you point out, tidying up everything at the bottom of the stack, and rethinking flow. It's kindof an enforced code review - which is always helpful.
The only thing I dislike is the requirement to expose so much of the interface in order to test things thoroughly. There's a stack of private methods that are really only pertinent to the inside of any given module that shouldn't be exposed.. and yet have to be. But it's a minor gripe really - particularly considering how sloppy my architecture is generally :)
1 year ago
in Si Dawson: Food Processor - Inner City Styles on Si Dawson
You can get small food processors which aren't that much bigger, you know (;
(Cuisinart miniprep are magical words that lead in that direction)
I would guess there's something about either the fat or protein content of nuts that will degrade the grinder over time (The one I had was a pain to clean, so you may find it gets a bit funky as any residual fat turns rancid).
I guess you'll find out eventually (:
(Cuisinart miniprep are magical words that lead in that direction)
I would guess there's something about either the fat or protein content of nuts that will degrade the grinder over time (The one I had was a pain to clean, so you may find it gets a bit funky as any residual fat turns rancid).
I guess you'll find out eventually (:
1 reply
si dawson
well, it didn't take long to find out :)
And I was feeling SO clever.. for about. ohhh.. 6 hours there *laugh*
No matter, took your advice, went on a hunt for mini preps. Didn't find that brand, but equivalent, for about a third of what I was expecting to pay - and you're right, very similar footprint. So, I'm happy, even if I am down one coffee grinder :)
And I was feeling SO clever.. for about. ohhh.. 6 hours there *laugh*
No matter, took your advice, went on a hunt for mini preps. Didn't find that brand, but equivalent, for about a third of what I was expecting to pay - and you're right, very similar footprint. So, I'm happy, even if I am down one coffee grinder :)
