11–20 of 27 posts
Oddly named campaign to promote better use of inheritance. "The Anti-Type Fields Campaign" would be more appropriate and less confusing.
This is a joke, right? They're making fun of all the programs you see that have 20 different forests of tiny classes spreading the logic of one function across 45 files, right?
Oddly named campaign to promote better use of inheritance. "The Anti-Type Fields Campaign" would be more appropriate and less confusing.
It's not about type fields and tag-and-switch. It's about the "if" statement. Let's be clear about how batsh*t crazy this messaging is.
Don't solve with conditionals that which can be solved by your language's dispatch mechanism.
Don't solve with 15 minutes that which you can bill your client 80 hours for.
And after that, we will eliminate source code, because it's too complicated. Everything you need to do can be done with 5x7 index cards.
Earlier quoted context omitted.
Don't solve with 15 minutes that which you can bill your client 80 hours for.
And don't forget, lots of those 15 minute intervals can add up to serious money. ("Stovepipe" systems.) You can also set up an opportunity to bill for coming later in and "fixing" a seemingly intractable big mess.
Earlier quoted context omitted.
It's not about type fields and tag-and-switch. It's about the "if" statement. Let's be clear about how batsh*t crazy this messaging is.
If you read their content (what little there is), it's type fields that they actually object against. I don't think they're actually saying "remove all ifs from code." If they are, then, yes, that would be batshit crazy. Instead of being crazy, though, I think they're just ineffective at communicating their message.
The idea is just bad.
Earlier quoted context omitted.
Don't solve with 15 minutes that which you can bill your client 80 hours for.
And don't forget, lots of those 15 minute intervals can add up to serious money. ("Stovepipe" systems.) You can also set up an opportunity to bill for coming later in and "fixing" a seemingly intractable big mess.
after vanquishing all if statements, we're going to go after function calls. And after that, we will eliminate source code, because it's too complicated. Everything you need to do can be done with 5x7 index cards.
Earlier quoted context omitted.
And don't forget, lots of those 15 minute intervals can add up to serious money. ("Stovepipe" systems.) You can also set up an opportunity to bill for coming later in and "fixing" a seemingly intractable big mess.
"Oh, I see the problem right here, Mr. Client. Your previous consultant used 'if' statements. Here, let me replace that function with 80 new class files. You'll be much more agile!"