1. 1

    At my company, we use Slack, Asana, and Bitbucket to collaborate between our Minneapolis and San Francisco offices. We’re on Macs exclusively and use Xcode for iOS dev and IAR Workbench for embedded dev. Most of us use Sublime Text for everything else.

    1. 1

      This seems like the same natural evolution I see in my code.

      Is there something wrong with starting with the naive approach?

      Seems like if I started with the final product, I might waste time writing code if we decide that an email marketing feature was un-necessary.

      1. 2

        I’ve been using TDD for most of my new projects. I found that when I start writing tests for my code, I naturally break it up into testable chunks as seen in the post. Testing EmailSubscriptionWorker is much more robust than mocking the MailChimp object when testing User.subscribe_to_mailchimp and makes a lot more sense.

      1. 1

        That second vulnerability—keybase.io/myname may not represent twitter.com/myname—seems to be covered by Keybase already: they allow you to verify a Twitter account and link it to your Keybase account. I don’t know what more they can do.

        1. 2

          They could possibly prohibit linking to a twitter account with the same name as an existing keybase account.

          This is something of a problem. For example, I’m tedunangst on twitter and tedu on github. I decide to be tedu on keybase. My evil doppelganger decides to impersonate me by signing up as keybase/tedunangst and linking with twitter/tedu and github/tedunangst. How are you to know who’s who?

          By artificially imposing some uniqueness constraints, keybase could for example notice that although my keybase name is tedu, my twitter handle is tedunangst. Therefore, they would prohibit creating keybase/tedunangst. Or they would prohibit any account from linking to twitter/tedu. Or both.

          There are obviously some land grab/denial of service issues here, but if they’re trying to be my “one true identity”, they need to cut down on aliases and collapse keybase/github/twitter into a single namespace.

        1. 2

          This presentation was a whole lot of buzzwords without a whole lot of substance when you take away the speech attached.

          1. 0

            I’ve given irrefutable scientific evidence on why Scala will make you less productive.

            What a mess of an article.

            1. 10

              I read it, in the context of the article, as simply being “tongue in cheek”. The first two paragraphs set quite a jocular tone from the outset.

              I don’t think the author’s intent was to win a Pulitzer, so I am not sure why it earned such a glib “what a mess” remark.

              1. 5

                Not to mention he gives plenty of examples about things that will slow you down and will make your life harder.

            1. 2

              This is fantastic. Postgres is one step closer to replacing Mongo as my document store o choice.

              1. 1

                Does this get you any closer?

                1. 1

                  FWIW, if you’re trying to find a “MongreSQL” then mongres seems to be a reasonable start at the MongoDB wire protocol and behavior for PostgreSQL servers. It uses plv8 and the ‘json’ datatype (could easily use jsonb).

                1. 2

                  I have one of the JDS models of his amp; I like the technical performance, but the design is poor (the power, input and output are all on the same face, making it a real PITA to use.) I wondered about such a grievous misdesign, but now I read about the “no derivate works” and the light goes on.

                  I get annoyed by design a lot, and I work at Apple. Idly, I wonder which direction the causality arrow points.

                  1. 1

                    I wondered about such a grievous misdesign, but now I read about the “no derivate works” and the light goes on.

                    What do you mean by that?

                    1. 2

                      Just that JDS felt they didn’t have the freedom to alter the layout, because of the license.

                  1. 3

                    If you aren’t an approved commenter and you post a comment, you can’t post another comment until the first one is approved (or expires and is deleted in 24 hours).

                    1. 2

                      The limit has now been raised to 5 “in-flight” comments at the same time.