• (cs)
    Anonymous:
    Anonymous:
    Alex Papadimoulis:

    [image]...most knew Java only as that bitter beverage they add sugar, cream, and (occasional) whiskey to, and drink every morning.



    So who made the coffee the day they interviewed guru? 

    For some reason, that cup of java looks more like a cup of melted brown crayon than a cup of coffee.

    Real coffee man... sugar should stay afloat over the foam for a few seconds before going down. Of course, sugar is for the weak.  

    Our coffee machine is broken... must have caffeine...   

  • anony coward (unregistered) in reply to dhoffman

    >I'm a bit tired of you IT snobs ranking on Access developers.  Some of us code carefully, use best >practices, and produce well running applications that work well for the users.

    Yes, and I'm a bit tired of people saying VB developers suck too! By now, it really ought to be assumed and thus has no need to be said.

    The reason these feelings still exist is because we're rather certain that if the Access and VB developers knew better, they would use different tools. The fact that anyone deigns to still use Access or VB is very telling: they either don't know any better or they're getting paid an enourmous amount to stoop so low.

  • (cs) in reply to cowpoke
    Anonymous:
    SomebodyElse:

     

    Java has checked exceptions that have to be caught or the code won't compile.  Judging from the timeline, most exceptions were checked at this point.  Any JDBC coding must be done in try catch blocks because SQLExceptions and subclasses are checked. 

     

    Just declare the exception to be thrown, and you are done with it.

     

     Ah, "the buck stops...somewhere else" philosophy.  Great. 

    Hell yes.  If you can't think of what to do with an exception besides catching it, YOU SHOULDN'T BE CATCHING IT AT ALL.   Leave it up to a caller to decide.

    P.S.:  Logging an exception does NOT count as "doing something meaningful" with it.
     

  • Glorious Finklebottom (unregistered) in reply to sf

    There is a limitation in Java class files, of no more than 65536 bytes of compiled Javur bytecodes inside one method of a class. Compiled. Has nothing to do with try-catch blocks, though their use obviously adds to the method length. Long string constants, to contrast, do not since they are stuck in a distinct constant pool. Likewise for 8-byte integer literals, inner classes (they go in a very bad, dark place in Java) and so forth.

    For comparison, we have this ass-horrible method at work. It's in a likewise ass-horrible Swing Panel subclass which encapsulates most of our homegrown CRM stuff. It grabs fields from the panel's constituent widgets and shoves them into the database in one orgastic transaction. Its length used to be measured in hundreds, but is now measured in the thousands of lines. I'm not talking about those "}\n" lines either. Yet it runs nowhere close to the 64KiB limitation; its compiled form was somewhere around twelve kilobytes the last I took a look (just to see how close we were).

    I guess the OP had misunderstood what he'd been taught at Potato Compootard Collage. Not that I blame him.

  • (cs) in reply to Erik Buitenhuis

    Writing the entire thing in an entire JSP would be a real WTF. This looks like it is a JSP page with a very large servlet behind it. Im guessing all the fancy frameworks weren't there or not relatively well known back then. Even better would have been to not use JSP and just use a single method to serve web pages.

  • JD (unregistered) in reply to Glorious Finklebottom
    Anonymous:
    ...

    I guess the OP had misunderstood what he'd been taught at Potato Compootard Collage....

    Thats "Potatoe Compootard Collage"   (how could you forget the "e" !?)

  • me (unregistered)

    When I started learning perl (~7 years ago) I had worse scenario ... I had to update/edit/fix bugs on a classified site someone else have written and it was single ~110kB (yes , right!!) CGI-script...

    Full of if-elseif's  and print's.The record was single if-elsif-elsif.... around ~25 terminal pages long ;)
     

     

     

  • (cs)

    What a DORK too bad so sad I see it all the time...people either look good or are good at what they do and clearly this guy looked good...

  • enterprisey! (unregistered) in reply to dhoffman
    dhoffman:
    Anonymous:

    MS-Access has a similar three-layer structure: the front-end, the back-end, and the caveman-sloping forehead of the "Access developer/architect" at the keyboard.

     I'm a bit tired of you IT snobs ranking on Access developers.  Some of us code carefully, use best practices, and produce well running applications that work well for the users.

     Not every application has to be cutting edge, super tech and state of the art.  Get a life and say something positive instead of making fun of something that isn't even relevant to this topic.

    uh, you mispelled "user" as "users".

    just kidding. i developed my first app on vb6 and access. it was the door that let me into db programming and, no, i didn't let it hit me on the way out. ;-)

    access does suck, though. or it did.

    how about using an access front on end on a real client server db like postgresql?

    then, when you lose the access front end, you can rank on "access guys," too.

    just kidding. seriously, i think you can differentiate yourself from other "access guys" by going the postgresql route and provide a better product to your customers.

    you would have to learna bit about a new db, but you have the talent so why not?

  • (cs) in reply to VGR
    VGR:
    Anonymous:
    SomebodyElse:

     

    Java has checked exceptions that have to be caught or the code won't compile.  Judging from the timeline, most exceptions were checked at this point.  Any JDBC coding must be done in try catch blocks because SQLExceptions and subclasses are checked. 

     

    Just declare the exception to be thrown, and you are done with it.

     

     Ah, "the buck stops...somewhere else" philosophy.  Great. 

    Hell yes.  If you can't think of what to do with an exception besides catching it, YOU SHOULDN'T BE CATCHING IT AT ALL.   Leave it up to a caller to decide.

    P.S.:  Logging an exception does NOT count as "doing something meaningful" with it.
     

     That depends, as well.  If your caller should not have specific knowledge of your implementation, then you may want to wrap or substitute your Exception in some way.  You should not implement your DAO classes to throw SQLExceptions, since yor DAO may encapsulate access to non-SQL data sources.  Does a SQLException make sense if I your backend is actually a webservice?
     

Leave a comment on “Yes, It Really is Three Tiers”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article