Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. San Diego Fireworks Bug

San Diego Fireworks Bug

Scheduled Pinned Locked Moved The Lounge
helpquestion
8 Posts 6 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    Karl Sanford
    wrote on last edited by
    #1

    http://youtu.be/NFv0p0sWXtw?t=45s[^]

    Quote:

    The Fourth of July fireworks show above San Diego Bay was over before it was supposed to start after a malfunction caused the display that was planned to last nearly 20 minutes of Fireworks Explode in 15 Seconds

    Listen as the owner, of the fireworks company responsible, explains how a programming bug was to blame. There are probably many lessons to be learned from this: 1. Always test 2. Have a fail safe 3. Safety should be the default 4. Always test 5. Have another fail safe 6. Mix programmers and fireworks with caution 7. Always test

    Be The Noise

    T S A 3 Replies Last reply
    0
    • K Karl Sanford

      http://youtu.be/NFv0p0sWXtw?t=45s[^]

      Quote:

      The Fourth of July fireworks show above San Diego Bay was over before it was supposed to start after a malfunction caused the display that was planned to last nearly 20 minutes of Fireworks Explode in 15 Seconds

      Listen as the owner, of the fireworks company responsible, explains how a programming bug was to blame. There are probably many lessons to be learned from this: 1. Always test 2. Have a fail safe 3. Safety should be the default 4. Always test 5. Have another fail safe 6. Mix programmers and fireworks with caution 7. Always test

      Be The Noise

      T Offline
      T Offline
      Tim Corey
      wrote on last edited by
      #2

      The fireworks were premature, but it seems this post was ... postmature? :-D http://www.codeproject.com/Lounge.aspx?msg=4301254#xx4301254xx[^]

      K I 2 Replies Last reply
      0
      • K Karl Sanford

        http://youtu.be/NFv0p0sWXtw?t=45s[^]

        Quote:

        The Fourth of July fireworks show above San Diego Bay was over before it was supposed to start after a malfunction caused the display that was planned to last nearly 20 minutes of Fireworks Explode in 15 Seconds

        Listen as the owner, of the fireworks company responsible, explains how a programming bug was to blame. There are probably many lessons to be learned from this: 1. Always test 2. Have a fail safe 3. Safety should be the default 4. Always test 5. Have another fail safe 6. Mix programmers and fireworks with caution 7. Always test

        Be The Noise

        S Offline
        S Offline
        Steve Mayfield
        wrote on last edited by
        #3

        8. Scratch VB :doh: 9. Scratch F# (F does not stand for "Fireworks") :laugh:

        Steve _________________ I C(++) therefore I am

        1 Reply Last reply
        0
        • T Tim Corey

          The fireworks were premature, but it seems this post was ... postmature? :-D http://www.codeproject.com/Lounge.aspx?msg=4301254#xx4301254xx[^]

          K Offline
          K Offline
          Karl Sanford
          wrote on last edited by
          #4

          :sigh:

          Be The Noise

          1 Reply Last reply
          0
          • T Tim Corey

            The fireworks were premature, but it seems this post was ... postmature? :-D http://www.codeproject.com/Lounge.aspx?msg=4301254#xx4301254xx[^]

            I Offline
            I Offline
            Ian Shlasko
            wrote on last edited by
            #5

            Tim Corey wrote:

            The fireworks were premature

            They have drugs for that :)

            Proud to have finally moved to the A-Ark. Which one are you in?
            Author of the Guardians Saga (Sci-Fi/Fantasy novels)

            1 Reply Last reply
            0
            • K Karl Sanford

              http://youtu.be/NFv0p0sWXtw?t=45s[^]

              Quote:

              The Fourth of July fireworks show above San Diego Bay was over before it was supposed to start after a malfunction caused the display that was planned to last nearly 20 minutes of Fireworks Explode in 15 Seconds

              Listen as the owner, of the fireworks company responsible, explains how a programming bug was to blame. There are probably many lessons to be learned from this: 1. Always test 2. Have a fail safe 3. Safety should be the default 4. Always test 5. Have another fail safe 6. Mix programmers and fireworks with caution 7. Always test

              Be The Noise

              A Offline
              A Offline
              Abhinav S
              wrote on last edited by
              #6

              Karl Sanford wrote:

              how a programming bug was to blame

              It was not the software. It was the hardware...it was...er..too fast. :-D

              Build your own survey - http://www.factile.net

              R 1 Reply Last reply
              0
              • A Abhinav S

                Karl Sanford wrote:

                how a programming bug was to blame

                It was not the software. It was the hardware...it was...er..too fast. :-D

                Build your own survey - http://www.factile.net

                R Offline
                R Offline
                Roger Wright
                wrote on last edited by
                #7

                Don't you just hate hardware that does exactly what it's asked to do, immediately? More to the point, don't you hate tech writers who fail to document that fact, or if they do, the programmers who felt there was no need to read the manual? :)

                Will Rogers never met me.

                A 1 Reply Last reply
                0
                • R Roger Wright

                  Don't you just hate hardware that does exactly what it's asked to do, immediately? More to the point, don't you hate tech writers who fail to document that fact, or if they do, the programmers who felt there was no need to read the manual? :)

                  Will Rogers never met me.

                  A Offline
                  A Offline
                  Abhinav S
                  wrote on last edited by
                  #8

                  Roger Wright wrote:

                  programmers who felt there was no need to read the manual?

                  Manual? What manual? There was a Manual? :wtf:

                  Build your own survey - http://www.factile.net

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Don't have an account? Register

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • World
                  • Users
                  • Groups