This is a discussion on What is a database developer in .net environment? within the Oracle Database forums, part of the Database Server Software category; --> On Sun, 09 Oct 2005 21:53:57 +0200, Matthias Hoys interested us by writing: >>>> >>>> >>>> Frustrated. >>>> >>> ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| On Sun, 09 Oct 2005 21:53:57 +0200, Matthias Hoys interested us by writing: >>>> >>>> >>>> Frustrated. >>>> >>> any more so than a database developer in the java world? >> >> Java developers don't get frustrated. After all, anyone who has 3279 >> classes and interfaces to learn (based on j2SE 1.5 API doc) to become >> proficient in the basics doesn't have time to be frustrated. Or time to >> read the doc and find out how to do things. <g> >> >> -- > > Couldn't the same be said of Oracle DBA's ? :-) Yes, you are right ... many Oracle DBAs get frustrated with Java and .Net database developers. <g> -- Hans Forbrich Canada-wide Oracle training and consulting mailto: Fuzzy.GreyBeard_at_gmail.com *** I no longer assist with top-posted newsgroup queries *** |
| |||
| "HansF" <News.Hans@telus.net> wrote in message news > On Sun, 09 Oct 2005 21:53:57 +0200, Matthias Hoys interested us by > writing: > >>>>> >>>>> >>>>> Frustrated. >>>>> >>>> any more so than a database developer in the java world? >>> >>> Java developers don't get frustrated. After all, anyone who has 3279 >>> classes and interfaces to learn (based on j2SE 1.5 API doc) to become >>> proficient in the basics doesn't have time to be frustrated. Or time to >>> read the doc and find out how to do things. <g> >>> >>> -- >> >> Couldn't the same be said of Oracle DBA's ? :-) > > Yes, you are right ... many Oracle DBAs get frustrated with Java and .Net > database developers. <g> > > -- I'm more referring to the "let's do it quick and dirty first and read the docs afterwards" kind of approach, a methodology highly supported by IT and other managers :-) |
| ||||
| On Mon, 10 Oct 2005 21:26:40 +0200, Matthias Hoys interested us by writing: > > I'm more referring to the "let's do it quick and dirty first and read the > docs afterwards" kind of approach, a methodology highly supported by IT and > other managers :-) Yes, I know. The GAAP (Generally Accepted Acconting Practice) related to clear and distinct separation of 'Capital Expense' vs 'Operation Expense', thus permitting a project to be defined at a minimum cost and released with the idea that it'll be fixed by operations. .... without permitting operations any ability to reference the stupidities at the initial capital project layer where the costs were created. -- Hans Forbrich Canada-wide Oracle training and consulting mailto: Fuzzy.GreyBeard_at_gmail.com *** I no longer assist with top-posted newsgroup queries *** |