Threads for conroy

  1. 1

    I was sadly one of the speakers that had to drop out. It turns out that even a ten-minute talk is more work than I expected. Excited for the next one (if it happens).

    1. 3

      These are the only type of tests I write for sqlc. Check that a known set of inputs create a known set of outputs. Makes internal refactors really easy.

      1. 2

        Super cool! I always look for something like this whenever there’s a concert coming up in my location.

        • How do you choose which cities to monitor?
        • I’m assuming you’re using the free tier on Heroku, any thoughts on if/when you’d hit the rate limit on it?
        • Are you considering building a more robust front-end for this? For example, letting the user search their city and pulling events/creating playlists on demand?
        1. 2

          To start, I picked my favorite venues in the Bay Area. I’ve just been asking people for venues they like that aren’t on the list. I just created two playlists for venues in Las Vegas for someone on Reddit.

          The script to create the playlists runs once a week, so I won’t hit any free tier limits. If I decide to make it self-serve, I may need to pay for a single Hobby dyno.

          No plans for a front-end yet, but I do want to make it easier to add venues. If it proves popular, I’ll probably invest more time into it. I really need a catchy name.

        1. 5

          I’m working on some new features for Equinox, my service for software updates. Specifically on a build service for any Go package that is available via go get. Also work on supporting new distribution mechanisms such as Chocolatey and Snap.

          I’m also working on fleshing out archive, a Go project to parse personal data archives from a variety of services. I have initial support for Twitter and Instagram with Facebook coming next. The next step is write a guide for users to export their data and make sure that my parsers are correct. My hope is that people can take my work to build out better tools for these archives.

          1. 4

            I quit my job a few weeks ago and have been enjoying the time off. I’m heading to GopherCon this week where I’m hoping to find a few more customers for my side project,

            1. 2

              I despise daily standups as they’re done in most settings. Having a meeting where ~10 people go around a room and give a status update is a waste of time. If it’s just a status meeting, then you can disseminate those updates via email / chat.

              I do find daily, unstructured check-ins with fellow project members useful. It’s just a simple conversation between humans, not a sacred ritual at the altar of Agile.

                1. 15

                  I haven’t posted in a while, but just wanted to chime in and congratulate the moderators on a successful migration. As someone sitting on the sidelines, I found the entire process transparent and incredibly well executed. Kudos to everyone involved.

                  1. 2

                    For work, focusing on launching a new set of API endpoints. I’m also slowing migrating a set of tables to a simpler data model.

                    I’m trying to start blogging again. Check out of your interested in developer tools or API discussion.

                    1. 1

                      I work at Stripe if you have any questions not answered by the post.

                      1. 6

                        I’m continuing work on Call to Speakers, my website for tracking open applications for speakers at conferences. I posted it on Hacker News a few weeks ago, and have seen steady growth in Twitter followers. This week I’m working on adding application forms directly to the site, so users won’t have to navigate (often confusing) conference website to submit their talks. Filtering the list of conferences on the front page is also high on the list.

                        I’ve also been doing API reviews for companies here in SF. I comb through the documentation and play around with an API to find bugs, poorly designed features, and incorrect behavior. It may sound dull, but I find it exciting. It’s a great way to validate all the API work I’ve put in over the last three years. I’m hoping to finish two more reviews this week.

                        And as always, I’m working on the API at Stripe, addressing performance problems and developing new features. We just had an intern start last week, so I’m helping him get up to speed.

                        1. 2

                          Nice. I pasted to my company Slack, and the preview appeared to be… “foo”. ;-) Be sure to change it.

                          <meta name="description" content="foo">

                          1. 1

                            Whoops, all fixed :)

                          2. 1

                            Is there anything out there that you would consider to be a good guide to designing (and documenting) a good API? What do you think of things like Swagger?

                            1. 2

                              I’m not a huge fan of Swagger as I think the documentation it generates isn’t user friendly. I’m becoming a fan of Hyper Schema, simply because it’s machine-readable.

                          1. 2

                            At work, I’m finishing up a custom integration with a large vendor. Also focusing on low-hanging bugs to get myself more comfortable with the code base.

                            At home, getting ready to launch Call to Speakers, a website for tracking conference speaking opportunities. I already have an RSS feed and a Twitter account. This week is focused on code clean up and email notifications.

                            1. 7

                              I’m starting to just wish the comments section had no voting. We get so few comments, I’m starting to think that upvotes aren’t helpful. Instead, I’d just like a flag link next to “link” which presented a drop down of “spam”, “troll” and “abusive”.

                              1. 3

                                Upvotes may be helpful for surfacing the most interesting or useful comments in a discussion, however there are several issues here:

                                • Reading all the comments on a thread isn’t often hard (we’re just not that big)
                                • Getting all the best comments up front may discourage reading the whole discussion (particularly as a site grows, and without an RES-like comment collapsing feature). There is an issue of diminishing returns in a voting system
                                • Group-think becomes more prevalent. The comments that end up at the top are the ones most people agree with. As they climb to the top more people see them, and because they are already likely close to the average opinion, they go higher. People entering after this has happened are presented first with a carefully selected and possibly homogeneous mix of opinions, with dissenting voices pushed downward.

                                Personally, I would love some experimentation with comment ordering. The site is still small enough that it isn’t likely to hide certain content behind a wall of previous content (like Reddit), and it could encourage a more balanced discussion by avoiding issue 3 listed above.

                                1. 1

                                  Maybe sort by votes but keep recent comments on top as well, so that you have everything within like the past hour or so on top for people to vote on, and then the top rated comments after that. Khan Academy’s comment system works a bit like that, and it seems pretty good.

                              1. 6

                                No need to create an aggregation page for Twitter. Instead you should just make a Twitter List.

                                1. 2

                                  In the specific case of Twitter sure. But better to create a single aggregation that can have many kinds of input and many kinds of output, including Twitter, than creating individual aggregations for each output service.

                                1. 10

                                  I think this is a great idea and would also encourage a stronger community.

                                  1. 13

                                    Where “good” is defined by the complexity and feature-set of the type system. As covered in the HN thread, the author of this post is looking for a more featured and complex type system, which Go does not offer. Yes, there are things you can do in Rust and Haskell which are difficult in Go. If you want to do those things, use Rust or Haskell.

                                    1. 9

                                      Actually, I think the language he is looking for is D. I get the impression what he is looking for is a Systems Programming Language.

                                      I think Go, by Pike’s own admission, is a particularly weak contender in that space.

                                      It would be much more interesting to see that level of analysis between Rust and D, and on the basis of a casual reading of that blog post my thoughts on each Rust vs Go point made were, “Eh, D wins over both…”

                                      Here is a panel discussion between Stroustrup for C++, Pike for Go, Alexandrescu for D and Matsakis speaking for Rust….


                                    1. 2

                                      When I saw this repository earlier, I brushed it off as another small-time effort by a single person. After reading the article, I’m much more excited. Having the backing of Google is a huge win here. I plan on installing this tonight.

                                      1. 9

                                        I think that’s ‘part’ of it. It also depends on the type / style of moderation. We run a huge community (4 million visitors a month) - we’ve had to ban some of our top posters over the years - just for being smarmy bastards.

                                        You can be big, and have a friendly place - but you’re going to have to do some ‘shitty’ things to keep it that way.

                                        1. 6

                                          I love talking about community management. Can you tell us more about the community you run and how you approach community management?

                                        1. 4

                                          I thought it was being taken up by @conroy, but I’m happy to keep them going.

                                          1. 2

                                            Sorry, I’ve been super busy with traveling and starting a new job. Anyone should feel free to post the thread on Mondays using older threads as a template.

                                          1. 12

                                            First day at Stripe! Focusing on getting up to speed so I can start shipping code.

                                            1. 1

                                              Congrats on the new gig!

                                              1. 1

                                                Welcome! I started at Stripe last week, and it’s been great.