Comments for Tom Dalling

Comment on Hilarious Massive Facebook Privacy Flaw by David

David — Fri, 26 Feb 2010 01:46:22 +0000

Nice. Guess I should stop sending credit card details to all my friends on Facebook eh? Never know who might end up with them!

Comment on SOLID Class Design: The Dependency Inversion Principle by SOLID Class Design: The Interface Segregation Principle « Tom Dalling

SOLID Class Design: The Interface Segregation Principle « Tom Dalling — Thu, 18 Feb 2010 13:17:29 +0000

[...] « SOLID Class Design: The Dependency Inversion Principle [...]

Comment on Implementing Your Own Cocoa Bindings by Technomadic » Links for October 25th through January 23rd

Technomadic » Links for October 25th through January 23rd — Sat, 23 Jan 2010 17:02:49 +0000

[...] Implementing Your Own Cocoa Bindings « Tom Dalling [...]

Comment on Implementing Your Own Cocoa Bindings by A Tasty Pixel » Blog » Links for October 25th through January 23rd

A Tasty Pixel » Blog » Links for October 25th through January 23rd — Sat, 23 Jan 2010 17:02:20 +0000

[...] Implementing Your Own Cocoa Bindings « Tom Dalling [...]

Comment on SOLID Class Design: The Open Closed Principle by SOLID Class Design: The Dependency Inversion Principle « Tom Dalling

SOLID Class Design: The Dependency Inversion Principle « Tom Dalling — Sat, 19 Dec 2009 08:54:28 +0000

[...] may notice that the above example is practically the same as an example in a previous article about the Open Closed Principle (OCP). Both make use of dependency injection (DI), but for different reasons. The OCP uses DI to [...]

Comment on SOLID Class Design: The Liskov Substitution Principle by SOLID Class Design: The Dependency Inversion Principle « Tom Dalling

SOLID Class Design: The Dependency Inversion Principle « Tom Dalling — Sat, 19 Dec 2009 07:41:08 +0000

[...] « SOLID Class Design: The Liskov Substitution Principle [...]

Comment on SOLID Class Design: The Single Responsibility Principle by SOLID Class Design: The Open Closed Principle « Tom Dalling

SOLID Class Design: The Open Closed Principle « Tom Dalling — Sat, 21 Nov 2009 06:58:58 +0000

[...] SOLID Class Design: The Single Responsibility Principle SOLID Class Design: The Liskov Substitution Principle [...]

Comment on SOLID Class Design: The Open Closed Principle by SOLID Class Design: The Liskov Substitution Principle « Tom Dalling

SOLID Class Design: The Liskov Substitution Principle « Tom Dalling — Sat, 21 Nov 2009 06:49:35 +0000

[...] « SOLID Class Design: The Open Closed Principle [...]

Comment on Coding Tip: Have A Single Exit Point by Tom

Tom — Wed, 04 Nov 2009 06:39:26 +0000

I do make exceptions, and optimization is one of those exceptions, but that occurs maybe less that 1% of the time. I definitely subscribe to the “premature optimization is evil” mantra.

Returning on finding bad data can be a good idea, such as function guards.

It really depends on the situation. It’s not that black and white.

Comment on Coding Tip: Have A Single Exit Point by alex

alex — Wed, 04 Nov 2009 03:30:24 +0000

Would you make an exception to save cycles? I.e. returning when continuing in the function no longer makes sense (possibly from bad input data)?