• (disco)

    They should have used APDB, that way they didn't have to reimplement their whole persistence layer from scratch.

    It's been released since 2010-04-01 <!-- the real deal -->and yet they didn't hear about it.

  • (disco)
  • (disco)

    Yay Visual Basic?

  • (disco) in reply to JBert

    Pff. Amateurs. Why don't they keep up with the latest technologies?

  • (disco)

    “It’s a really genius pattern, because it’s like using a database, but without actually using a database. It runs in memory, so it’s lightning fast! I’ve learned so much from the Guru.”

    Lightning fast execution is a noble and lofty goal, but hacking your entire system to try to work like a large database without an actual database is the sort of thing that it would take an entire development team and an obscene amount of high-powered hardware to accomplish.

  • (disco) in reply to Fox

    Rules of optimization:

    1. Don't optimise
    2. Don't optimise yet.
    3. Measure your bottlenecks
    4. Benchmark your improvements. You should not accept greatly increased complexity at little performance benefit.
  • (disco) in reply to PleegWat

    Your rules of optimization directly contradict the rules of enterprisiness:

    1. optimize from the very beginning
    2. do it right the first time
    3. if you are a guru, the way you did it automatically fulfills points 1 and 2. If you are an underling, there's your problem.
    4. allow only volkswagenized benchmark tools to be used on your stuff.
  • (disco) in reply to Fox
    Fox:
    try to work like a large database without an actual database is the sort of thing that it would take an entire development team and an obscene amount of high-powered hardware to accomplish.
    or `sqlite3_open(":memory:", &myDb)` :trolleybus:
  • (disco) in reply to JBert
    JBert:
    They should have used APDB, that way they didn't have to reimplement their whole persistence layer from scratch.
    They could always try CornifyDB [image]
  • (disco)

    Exceptions were always caught and ignored.

    :wtf: Not even proper On Error Resume Next?

  • (disco)

    When Rich blinked and backed away, he should have done what I do in Kingsmouth (The Secret World survival horror zone) when I back away from something. That something is usually a group of flesh-eating zombies that I've interrupted. I back away while letting rip with, uncharacteristically(1), a large ugly shotgun. For the next zone, I need a larger, uglier one.

    (1) I haven't yet found a GAU-8 in-game, much less one they'll let me carry around and use.

  • (disco) in reply to PleegWat
    1. Allow time for your developers to do all this and produce no changes
  • (disco)
  • (disco)

    "Gurus" like this do have 2 actual skills in abundance:

    1. Salesmanship.
    2. Structuring things in such a way that they and their work are never questioned until after they've run away with all the money.
  • (disco) in reply to EatenByAGrue
    EatenByAGrue:
    "Gurus" like this do have 2 actual skills in abundance:
    Hm. Sounds like you've been eaten by a Guru.
  • (disco)

    “It’s a really genius pattern, because it’s like using a database, but without actually using a database. It runs in memory, so it’s lightning fast! I’ve learned so much from the Guru.”

    The idea that execution speed is the most important aspect of a database is what got us MySQL.

  • (disco) in reply to PleegWat

    Yeah, but it's pretty obvious that the DB and IO are going to be the bottlenecks for lots of applications. Especially if you have experience the domain. So why waste months writing against a platform you know will unacceptably slow?

  • (disco) in reply to Captain
    Captain:
    why waste months writing against a platform you know will unacceptably slow?

    So instead waste months writing something even slower, except you don't know until it's done?

Leave a comment on “The Guru and The Code”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article