Object Oriented Development vs Practicality - Contractor UK Bulletin Board

Visitors can check out the Forum FAQ by clicking this link. You have to register before you can post: click the REGISTER link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. View our Forum Privacy Policy.
Want to receive the latest contracting news and advice straight to your inbox? Sign up to the ContractorUK newsletter here. Every sign up will also be entered into a draw to WIN £100 Amazon vouchers!

You are not logged in or you do not have permission to access this page. This could be due to one of several reasons:

You are not logged in. If you are already registered, fill in the form below to log in, or follow the "Sign Up" link to register a new account.
You may not have sufficient privileges to access this page. Are you trying to edit someone else's post, access administrative features or some other privileged system?
If you are trying to post, the administrator may have disabled your account, or it may be awaiting activation.

TheMonkey replied

30 August 2006, 19:38
Originally posted by Joe Black

design patterns, oh dear...what next CSLA?

Sorry I just vomited.
Leave a comment:
_V_ replied

30 August 2006, 18:29
Yes, it can spoil a good marriage.
Leave a comment:
Diestl replied

30 August 2006, 18:17
Premature optimization is the root of all evil.
Leave a comment:
Joe Black replied

30 August 2006, 18:14
design patterns, oh dear...what next CSLA?
Leave a comment:
DimPrawn replied

30 August 2006, 13:42
OO is sooooooooo 1990's

You should be thinking of SOA, message exchanges, schemas, XML, design patterns.

Also, this techie focus on over optimising is very sad. "Oh I can't use that feature as it uses an extra cycle out of the billion i have per second".

Design and code for maintainability, security, scalability and support.

Purlease, get a grip. This is the 21st century not 1992.

HTH
Leave a comment:
Stan replied

30 August 2006, 13:35
Good OO advice is to favour composition over inheritance. I have seen far too many (and for a while probably created a few ) cases of inappropriate use of inheritance.
Leave a comment:
TheMonkey replied

22 August 2006, 17:36
Originally posted by Jabberwocky

Are you some sort of magpie AtW ? I suggest you go back to school and get a proper comp sci education.

Like my electrical engineering one

We're not all native comp sci.
Leave a comment:
Jabberwocky replied

22 August 2006, 08:50
Are you some sort of magpie AtW ? I suggest you go back to school and get a proper comp sci education.
Leave a comment:
AtW replied

22 August 2006, 08:48
Go look at something shiny jabber.
Leave a comment:
Jabberwocky replied

22 August 2006, 08:47
Horseshi*t - properties are fine if used in the proper context e.g. graphical components - only an half-ar*ed ruskie would be getting and setting in a performance critical loop involving no other opertations - they are only a few mc ops anyway.
Leave a comment:
AtW replied

22 August 2006, 00:37
Yeah properties are performance killer - strange that they are not inlined. Performance wise C# is actually very good - I had some stuff ported to Visual C++ and assembly code generated was not much better.
Leave a comment:
TheMonkey replied

21 August 2006, 22:46
Originally posted by Diestl

thanks

My pleasure.

I entirely agree with your point. I'm actually learning Objective C at the moment (OO layer on top of C basically). Less convoluted than C++...
Leave a comment:
Diestl replied

21 August 2006, 21:43
thanks
Leave a comment:
TheMonkey replied

21 August 2006, 21:39
Originally posted by Diestl

Why use C# if you're only interested in performance, use C++ or C. Things like properties are there to allow proper object oriented implementation.

Very insightful!
Leave a comment:
Diestl replied

21 August 2006, 21:19
Why use C# if you're only interested in performance, use C++ or C. Things like properties are there to allow proper object oriented implementation.
Leave a comment: