-
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.
-
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.
-
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 stackmachine.com of your interested in developer tools or API discussion.
-
I work at Stripe if you have any questions not answered by the post.
-
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.
-
-
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.
-
conroy
4 years ago
|
link
| on:
Is it ok to anonymously downvote a comment as "incorrect" without any explanation?
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”.
-
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.
-
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.
-
-
No need to create an aggregation page for Twitter. Instead you should just make a Twitter List.
-
-
I think this is a great idea and would also encourage a stronger community.
-
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.
-
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….
-
-
conroy
4 years ago
|
link
| on:
Google Online Security Blog: Making end-to-end encryption easier to use
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.
-
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.
-
-
I thought it was being taken up by @conroy, but I’m happy to keep them going.
-
-
First day at Stripe! Focusing on getting up to speed so I can start shipping code.
-
-
As a maintainer of a few open source projects, I agree with the author that building and managing a community is difficult and time consuming.
It’s very easy to open source a project, but too many companies see the first public commit as the end product. If you don’t have a dedicated engineer to manage issues, field pull requests, fix bugs, answer questions, and all the other tasks required in running a project, your community will stay small.
The two tactics I’ve used in building my open source communities are being generous with commit access and investing in automation. Many open source projects are treated as pet projects, where only the original creator has commit access. If you’re lucky to have a person contribute more than one patch, give that person commit access. They’ll feel great because they can now help out with asking for permission, and you’ll feel great because you now have more help.
My goal with automation is simple: if a user has commit access, they should be able to manage the entire project. For my open source game, this means that the entire release process is automated, powered by pull requests. Anyone can create a pull request from master into the release branch. If the pull request is merged, then the CI system packages up and publishes the release. While I had to invest significant time into the process, it allowed me to step back from the game without slowing down development.
-
-
gabeio
edited
4 years ago
|
link
| on:
Follow up to the investigation results behind github employees claims
How interesting that this site prides itself on having their users who downvote explain why they did. And yet I receive two downvotes one of which I understand because it is my first post and I am just trying to get to understand where it should fit in and the other just makes non-sense because this story unless the title was completely changed has not been already posted. And yet neither of these users cared to comment to help me understand where they were coming from. This is the second post on github’s blog about the topic I do understand that they were similarly titled but I tried not to change the title but still make it understandable. (not the same thing as) https://github.com/blog/1823-results-of-the-github-investigation
-
Hi @gabeio, welcome to Lobsters. I’m sorry that your first post hasn’t gone smoothly. As one of the four people that down voted this article (and two that hid it) I’ll walk you through the reasoning behind the downvotes. At the time I’m writing this comment, the story has down votes for already posted, off-topic, and poorly tagged.
already posted: While your article itself has not been posted, this person is probably referring to the fact that this topic has already been covered in a previous submission. I agree with you that this isn’t a fair reason to downvote your story.
poorly tagged: The tags you’ve used don’t really apply to this story. The article is about the results of an internal investigation at GitHub. While it pertains to GitHub’s culture, most stories tagged “culture” are about how to improve or manage a company’s culture. Also, the “web” tag isn’t appropriate, because this article has nothing to do with the internet, it is merely posted using the web.
off-topic: I downvoted this story as off-topic because I, like many Lobsters users, don’t like seeing these types of stories. This story has zero technical content. It’s about a HR mishap inside I company I don’t work for. And even though this blog post sheds some new light on the issue, it still provides zero value beyond celebrity and valley gossip.
Lobsters itself has a strong bias against valley news of any kind. You won’t find news here about new startups, acquisitions, or IPOs.
Also, a meta-comment: please refrain from using unnecessary capitalization in your comments. There’s no need to yell :)
-
Thanks for your comments and I will take them under consideration next time posting something but it seems that you at least are incorrect about only one part.
like many Lobsters users, don’t like seeing these types of stories
at least thus far the favor is for seeing a story like this, 10:4.
As such I did agree that it is tagged wrong as I didn’t know of the extended description of these tags. And as for off-topic this is more of an opinion and less of a true/false and in my opinion should not be available.
Sorry, I corrected the cap lock to italics ;].
-
Yes, for this particular story, I agree that I am in the minority. I should have made it clear that my comment refers to other stories in the past with similar content that were not well received.
And as for off-topic this is more of an opinion and less of a true/false and in my opinion should not be available
I disagree with removing the “off-topic” down vote, as down-votes are not about expressing facts, but instead about expressing opinions. I’d rather not see these type of articles on Lobsters, so I used my downvote to express that fact.
-
I disagree with removing the “off-topic” down vote, as down-votes are not about expressing facts, but instead about expressing opinions. I’d rather not see these type of articles on Lobsters, so I used my downvote to express that fact.
Fair enough. & I will still attempt not to make posts about “valley drama” which I don’t really know/care what companies are in the valley (as I am on the east coast) so it’s hard for me to filter my posts about such topics.
-
It doesn’t have to do with where the company is located so much as that it’s fundamentally a who-did-what type story. There’s a quote (often attributed to Eleanor Roosevelt, which seems dubious) that great minds discuss ideas, average minds discuss events, small minds discuss people. Well, there are plenty of sites on the web already for discussing people.
Lobsters so far has distinguished itself to me as a place of interesting idea-level links, appearing here much sooner than they gain traction elsewhere, if they gain any traction at all. News stories that gain favour here are generally those of broader significance.
-
-
-
-
-
-
First off, congratulations on your internship! Enjoy your time and learn a bunch. Don’t get too upset about using Java and Windows, amazing software has been writing using both. Java itself is seeing a revival, as the JVM is very performant.
I use OS X with MacVim, Terminal.app, Git, and SizeUp, writing Go, Ruby, and Python. For communication, my company uses a mix of Slack, GMail, Hackpad, Google Groups, Google Drive, and GitHub.
-
Thanks! I understand that amazing software has been written using both! Unfortunately I’m just (a lot more) comfortable with Unix/ Unix-Like systems.
With the languages you use it sounds like you have a very interesting stack!
-
-
I’m really excited about this news. While I don’t plan on using Atom, I was really worried that it was going to see major adoption, only to be eventually abandoned. Now that it’s fully open-source, it can grow into it’s own community.
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, https://equinox.io