1. 1

    This sounds interesting, but the link is broken. Is there a backup somewhere?

      1. 1

        Food for thought. Thanks for the links!

      1. 1

        Because you haven’t fixed it yet.

        1. [Comment removed by author]

          1. 1

            A perfect opportunity to learn!

      1. 3

        I’m dismayed by all the people in the comments who didn’t read the article but think that “LOL PHP” is a valuable contribution.

        1. 2

          Sharing your dismay at them isn’t valuable either.

          1. 3

            This site gets lonely sometimes, I’m experimenting with commenting as a way to get things flowing.

            1. 2

              Perhaps they were commenting for similar reasons. How is your day going?

        1. 2

          Having to have a facebook account is a real downer.

          1. 2

            You don’t need one to solve the puzzles.

          1. 1

            Disregarding the analogy, there are problems with the doctrine itself. For example, here are two that stand out:

            “Hell is a place where people are no longer in the presence of God” – how could this be if God is omnipresent?

            In a similar vein, if Lucifer rebelled and Adam & Eve chose, and if God is omnipotent/omniscient/omnipresent, then it would mean that God chose to allow both events to occur. If that is the case then God chose to allow his own creation to be corrupted.

            1. 3

              Jared makes a good point. However, it’s possible to strike a balance between simplicity and capability by making available optional, modular features for a given product; users install modules on request to add capabilities outside the core feature set. A model like this avoids both problems mentioned in the article – keeping the UI/UX approachable, and the code untangled. It does add some complexity though, which is unavoidable. Still, it could be a good way to get new users up and running quickly, then retain them when their requirements grow.