News for hackers. Stuff that matters.

IanWhalen

Re:Show HN: Version Control for Microsoft Word on Wednesday June 14, 2017 @10:52AM (#14553149)
I feel like I've searched pretty extensively but not found such an add-on. If you can remember the name and link it here that would be awesome.
Re:Show HN: Version Control for Microsoft Word on Wednesday June 14, 2017 @10:24AM (#14552920)
The addition of tags/versions is something that I would kill for in Google Docs. It would make life so much easier in my current role if we had the ability to tag a version so that you can easily see a diff between that specific, tagged version and the current version (rather than just seeing diffs over time as it is currently implemented).
Re:How Chromium Works on Friday September 25, 2015 @02:27PM (#10279802)
I'm curious whether you've got any interesting projects underway to work on the flaky test issue? I've been looking at FBs test lifecycle approach with some interest (http://goo.gl/QtUNxY), but would love to hear about any other approaches to solving the same problem.

And FWIW on building MongoDB with Evergreen (https://evergreen.mongodb.com) we've found that a stepback approach seems to give us the finest granularity with minimal cost in identifying the introduction of an error - we batch commits for execution, but when a specific test fails we start running just that test on each previous commit until we hit a passing execution. It obviously doesn't work perfectly in the face of flaky tests (see above question) but it seems to do pretty well.

Re:Ask HN: Who is hiring? (July 2014) on Tuesday July 01, 2014 @11:16AM (#7971177)
MongoDB - New York, Palo Alto, and more

MongoDB is hiring engineers of pretty much every stripe!

==========================

In New York:

+ Java application engineers Work on MMS (our monitoring, backup and automation platform - https://mms.mongodb.com)

+ Systems/ops engineers Build out the data centers used by MMS

+ Database kernel engineers Work on the core MongoDB database (C++)

==========================

In New York/Palo Alto/many other places:

+ Technical service engineers Support our users and customers to ensure their success

+ Consulting engineers Assist our users and customers with all phases of implementation

+ Solutions Architects Design systems/architectures alongside our customers

==========================

As well as:

+ Performance engineers in Palo Alto

+ Test engineers in New York, Palo Alto, Austin and Boston

+ Technical writers in New York

+ Language-specific driver developers around the world

==========================

You can apply online or just get in touch with me at [email protected]

http://hire.jobvite.com/j/?aj=oWm7Yfw7&s=Ian_Whalen

Re:Ask HN: What Are Some Good GitHub "Contributing" Examples? on Sunday November 25, 2012 @11:11AM (#4828414)
notmyname's mention of their process does reinforce one of the difficulties you'll have to address if you want to make a Bootstrap-like template - almost every company has a slightly different process.

OpenStack doesn't use GitHub for issues or pull requests, while MongoDB doesn't use their issues but does use pull requests. Some projects require you to sign a contributor agreement, some don't. Different languages (coding standards), different platforms (testing), etc. So you'll probably want to bake the customization aspect (a la http://twitter.github.com/bootstrap/customize.html) into the very core of your idea.

As for examples: - the guidelines for the MongoDB project (not bad, I think) are here: https://github.com/mongodb/mongo/blob/master/CONTRIBUTING.rs... - and the Contributor Guidelines for Chef are quite good too: http://wiki.opscode.com/display/chef/How+to+Contribute