Comments for Roop says

Comment on Java to Coldfusion HashMap by Elliott Sprehn

2008-09-01T06:17:44Z

This is because CF uppercases struct keys that are accessed using dot notation.

map = createObject(”java”,”java.util.HashMap”).init();
map.put(”foo”,1);
map.put(”BAR”,1);

// this won’t work
map.foo;

// this will
map[”foo”]

// this will too, since we inserted it in upper case
map.bar

Comment on Program to an interface not an Interface by Daniel Roop

2008-07-14T02:06:47Z

@Russ

Very good point, I agree you don’t lose much by creating the interface, but it does clutter up your packages, and increase the files you need to maintain in your software. And we all know the more lines of code, the more bugs in the code ;-).

Regardless, that is a good point, I just wish more seasoned developers would speak out, so that the new developers don’t get stuck believing the interface advocates are the only seasoned train of thought.

Comment on Program to an interface not an Interface by Russ

2008-07-13T04:18:05Z

I think its probably part of the learning experience. Everyone goes through a collection of practices until they learn what’s useless and what’s not. The mix up in nomenclature from the GoF book is likely the cause… but the end result of making an interface for everything in your system isn’t entirely bad. Its a tedious way of learning how to think about the (lowercase) interface (as opposed to the uppercase one). Once you learn that you can make better concrete classes and only extract interfaces when you need them. The debate will continue, though, because there’s always someone who doesn’t know any better.

Comment on Actionscript 3.0 Object Equality by Ryan Christiansen

2008-07-07T12:23:04Z

I’ve been developing a FlexUnit alternative called FUnit and came across this issue this weekend. Through my research, I found that FlexUnit is definitely an exception to the rule. The result of my findings can be found here:

http://blog.funit.org/?p=13

Pending community feedback, Assert.areEqual() will support member-wise value comparison like what has been suggested here, and NOT reference comparison. A second Assert.areSame() will be available for that purpose.

Comment on Program to an interface not an Interface by Theo Briscoe

2008-07-04T02:10:55Z

I concur, the idea of creating all the interfaces up front (before they are needed) does not make sense. All the modern IDE can generate interfaces later in the development process when they are needed.

Comment on Program to an interface not an Interface by Bucky Schwarz

2008-06-30T14:41:00Z

Great post. I feel like I don’t have much to add to this discussion right now, so I’ll leave it at good job.

Comment on Program to an interface not an Interface by Michael Sica

2008-06-30T01:57:53Z

I agree, even in scenarios where you’re implementing an interface in your class (like the threading stuff in java - what is it, runnable?) the only thing you’re getting from an Interface is the compiler saying, “hey, you did this wrong”… Like you weren’t going to ever run the code until it’s in a production/mission critical/life threatening situation?

If I’ve got an API doc - I’m good.

Comment on What makes a great developer? by A New Look at Development

2008-06-06T03:56:26Z

[…] to programming though, what matters is problem solving, core programming concepts and most of all passion. While staying up to date with what interests you may not be hard, most would agree it’s […]

Comment on What makes a great developer? by Russ

2008-05-18T20:25:14Z

In my case, I think passion = anger.

Comment on What makes a great developer? by Daniel Roop

2008-05-16T12:01:41Z

@Brian

Yes that is all I need and, correct you are an ampersat dollar dollar.

Thanks for the comment, so far I have been lucky in finding places that will tolerate my…passion. Every once in a while though you have to go through the growing pains of something new though.