I see your point, but I got the impression he was talking about a tactical/technical productivity boost rather than expanding their recruiting net or code expressiveness.
"...static typing becomes a big convenience in enforcing coherency across all the systems. You can guarantee that your dataflow is more or less going to work, and focus on the functional aspects...But as we move into a…
True enough in general, but that cuts both ways -- I've worked with a number of longtime C++ guys that tend to optimize early, write long unreadable methods and seem positively allergic to standard OOP architectures,…
If you haven't watched Peepcode's Play by Play with Zed Shaw, you should. Really insightful stuff.
Zed's a strong cup of coffee and guys like him generally play a really healthy role in the community they are a part of, driving discussions in directions they might not have taken and playing the part of Gadfly at…
Sure, but in my experience the challenge of describing imperative instructions with tabular data (in general) makes the Object/Relational problem look one-dimensional.
Not knocking OP's efforts as a nifty academic excercise -- good stuff. But MSI is a real world (admittedly MS) attempt at writing imperative instructions into relational tables. And, again...<shudder>
Anyone who thinks programming with tables is a neat idea hasn't had to write a complex Windows Installer/MSI deployment. The horror...the horror...
I guess the part I should have emphasized better in my original comment was "in theory"...
Agree with all of this, and I've made the same arguments myself. That's one reason code coverage metrics are of limited use -- they can't measure the quality of the tests. I wasn't intending to diminish the role of QA…
OR in an agile/integrated testing environment, the Black Team would be working with the dev to help develop unit tests and/or find the bug before it was delivered.
Ruthless and thorough QA is a good thing, but has nothing to do with TDD. TDD should in theory help prevent the developer from ever hearing from the Black Team to begin with. If the Black Team found the bug, the dev's…
Contrast could be better but I like the layout and fonts. Simple.
You'd also think a cisco engineer up to such shenanigans would know enough to use an anonymous/proxy whois registration.
Add Josh Bloch, Google's Chief Java Architect to that list.
"I almost never test at the view level, and barely at the controller level" You sound like every Rails dev I know. It depends on the controller action in question. If it's a boilerplate Rails controller action, then the…
"Like Xerox and Kleenex, the popular usage is technically incorrect, but in practice, it doesn't matter." The integrity of some acronyms is worth defending. I wouldn't want 'ACID' diluted to mean anything less than its…
Romantic, starry-eyed, hopelessly idealistic and mostly true.
The problem I have with this theory is that Android just wasn't written as a general-purpose GUI framework/OS. It's very mobile and memory-constraint centric, and IMO would need a whole new UI layer, if not a major…
By this logic every language should have C-style headers. There's nothing to prevent me from creating a bloated API/interface with or without the framework forcing me to declare it external to the class, in interfaces,…
There's some Western philosophical precedents for this tack as well. Heraclitus comes to mind, later Nietzsche, Kierkegaard. William of Occam I suppose would never allow 'classes' at all, only radically individual…
Yeah exactly! 'raise "not implemented"' is how I imitate abstract classes (on the rare occasion that I need them).
I get what you're saying, but Ruby already allows you to do this. If you like an API/design, then go ahead and reimplement it however you like. There are no class-level contracts anywhere in Ruby that would prevent…
This simply makes no sense in a Ruby idiom (and I'm not really sure this is the best way to think of it in Java either -- I can make an API public and well-documented with or without interfaces.) I've used dozens of…
"Kant's seperation between Phenomena and Noumena relates to the difference between interface and implementation, as well as to the concept of abstractions in general." I'm not sure Kant would allow that phenomena are…
I see your point, but I got the impression he was talking about a tactical/technical productivity boost rather than expanding their recruiting net or code expressiveness.
"...static typing becomes a big convenience in enforcing coherency across all the systems. You can guarantee that your dataflow is more or less going to work, and focus on the functional aspects...But as we move into a…
True enough in general, but that cuts both ways -- I've worked with a number of longtime C++ guys that tend to optimize early, write long unreadable methods and seem positively allergic to standard OOP architectures,…
If you haven't watched Peepcode's Play by Play with Zed Shaw, you should. Really insightful stuff.
Zed's a strong cup of coffee and guys like him generally play a really healthy role in the community they are a part of, driving discussions in directions they might not have taken and playing the part of Gadfly at…
Sure, but in my experience the challenge of describing imperative instructions with tabular data (in general) makes the Object/Relational problem look one-dimensional.
Not knocking OP's efforts as a nifty academic excercise -- good stuff. But MSI is a real world (admittedly MS) attempt at writing imperative instructions into relational tables. And, again...<shudder>
Anyone who thinks programming with tables is a neat idea hasn't had to write a complex Windows Installer/MSI deployment. The horror...the horror...
I guess the part I should have emphasized better in my original comment was "in theory"...
Agree with all of this, and I've made the same arguments myself. That's one reason code coverage metrics are of limited use -- they can't measure the quality of the tests. I wasn't intending to diminish the role of QA…
OR in an agile/integrated testing environment, the Black Team would be working with the dev to help develop unit tests and/or find the bug before it was delivered.
Ruthless and thorough QA is a good thing, but has nothing to do with TDD. TDD should in theory help prevent the developer from ever hearing from the Black Team to begin with. If the Black Team found the bug, the dev's…
Contrast could be better but I like the layout and fonts. Simple.
You'd also think a cisco engineer up to such shenanigans would know enough to use an anonymous/proxy whois registration.
Add Josh Bloch, Google's Chief Java Architect to that list.
"I almost never test at the view level, and barely at the controller level" You sound like every Rails dev I know. It depends on the controller action in question. If it's a boilerplate Rails controller action, then the…
"Like Xerox and Kleenex, the popular usage is technically incorrect, but in practice, it doesn't matter." The integrity of some acronyms is worth defending. I wouldn't want 'ACID' diluted to mean anything less than its…
Romantic, starry-eyed, hopelessly idealistic and mostly true.
The problem I have with this theory is that Android just wasn't written as a general-purpose GUI framework/OS. It's very mobile and memory-constraint centric, and IMO would need a whole new UI layer, if not a major…
By this logic every language should have C-style headers. There's nothing to prevent me from creating a bloated API/interface with or without the framework forcing me to declare it external to the class, in interfaces,…
There's some Western philosophical precedents for this tack as well. Heraclitus comes to mind, later Nietzsche, Kierkegaard. William of Occam I suppose would never allow 'classes' at all, only radically individual…
Yeah exactly! 'raise "not implemented"' is how I imitate abstract classes (on the rare occasion that I need them).
I get what you're saying, but Ruby already allows you to do this. If you like an API/design, then go ahead and reimplement it however you like. There are no class-level contracts anywhere in Ruby that would prevent…
This simply makes no sense in a Ruby idiom (and I'm not really sure this is the best way to think of it in Java either -- I can make an API public and well-documented with or without interfaces.) I've used dozens of…
"Kant's seperation between Phenomena and Noumena relates to the difference between interface and implementation, as well as to the concept of abstractions in general." I'm not sure Kant would allow that phenomena are…