Comments on: Programming for someone with blinders http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html Productive software development using ASP.NET, C#, Adobe Flex, and other technologies and tools. Thu, 09 Sep 2010 10:53:34 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Bookmarks about Flex http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html/comment-page-1#comment-1286 Bookmarks about Flex Mon, 12 Jan 2009 10:45:32 +0000 http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html#comment-1286 [...] - bookmarked by 4 members originally found by cstarrett on 2008-12-17 Programming for someone with blinders http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html - bookmarked by 1 [...] [...] – bookmarked by 4 members originally found by cstarrett on 2008-12-17 Programming for someone with blinders http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html – bookmarked by 1 [...]

]]> By: Design your classes for their consumer http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html/comment-page-1#comment-625 Design your classes for their consumer Mon, 11 Aug 2008 19:45:43 +0000 http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html#comment-625 [...] have a tendency to just focus on the class we’re currently working on. Of course I believe this is a good thing, because we all know the importance of focus. However, you should never forget the reason [...] [...] have a tendency to just focus on the class we’re currently working on. Of course I believe this is a good thing, because we all know the importance of focus. However, you should never forget the reason [...]

]]> By: Romeo http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html/comment-page-1#comment-617 Romeo Sat, 26 Jul 2008 08:07:45 +0000 http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html#comment-617 I share your enthusiasm when it comes to being strict with coding standards, particularly with the readability of codes. Some TLs who'd like code reviews, with this in mind, you'd have to worry less. It's basic OOP principle..."Separation of concern". :D I share your enthusiasm when it comes to being strict with coding standards, particularly with the readability of codes.

Some TLs who’d like code reviews, with this in mind, you’d have to worry less.

It’s basic OOP principle…”Separation of concern”. :D

]]> By: Rex http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html/comment-page-1#comment-611 Rex Thu, 24 Jul 2008 19:39:17 +0000 http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html#comment-611 But what about job security...? JK I really agree with you. Having an application split up into different classes really is the easiest way for me to understand it. I'd much rather have different classes representing objects and an actual data access layer, etc, than having a Windows Form with 10,000 lines of code in it that does everything. But what about job security…? JK

I really agree with you. Having an application split up into different classes really is the easiest way for me to understand it.

I’d much rather have different classes representing objects and an actual data access layer, etc, than having a Windows Form with 10,000 lines of code in it that does everything.

]]> By: Al http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html/comment-page-1#comment-608 Al Wed, 23 Jul 2008 14:29:04 +0000 http://www.ytechie.com/2008/07/programming-for-someone-with-blinders.html#comment-608 While I don't think anyone should be scared of creating additional classes where required, you do have to be mindful of having too many classes, too many interfaces, to overly complex inheritance. Being able to understand a given class is one thing, being able to understand the system and how/why it is constructed in a particular way is another thing entirely I think. I know I've seen people walk into sections of a software stack that is deliberately heavily decoupled and flounder for quite a while - until they finally nut their way through it or seek help from a more senior programmer. Remember, everything comes with a trade off. While I don’t think anyone should be scared of creating additional classes where required, you do have to be mindful of having too many classes, too many interfaces, to overly complex inheritance.

Being able to understand a given class is one thing, being able to understand the system and how/why it is constructed in a particular way is another thing entirely I think.

I know I’ve seen people walk into sections of a software stack that is deliberately heavily decoupled and flounder for quite a while – until they finally nut their way through it or seek help from a more senior programmer.

Remember, everything comes with a trade off.

]]>