helper

If you write a syntactically and semantically correct go program it will compile. Can you give an example?

You can't add more data once you've truncated.

AMT and the 90 day limit on exercising after leaving a company are the main things that make options painful. There has been some movement in the industry to get away from the 90 day limit (by converting from ISOs to NSOs), but has there been any recent attempts to get the AMT rules changed for ISOs? Does anyone think the current AMT rules for stock options are fair? I'm curious how this is viewed by people outside the industry.

I read go's stdlib implementation more than any other language I have ever worked with. The main reason? Because the implementation is just a click away when you are looking at godoc.

I was able to get a few hits from a quick google search that are still in google's webcache.

Reviewable doesn't hide whitespace changes, it shows just enough so you can tell that whitespace changed without getting in the way of reading the rest of the diff.

+1 for reviewable. In addition to this feature reviewable's diff display is a lot nicer. For example it does a much better job handling whitespace only changes when a block of code gets reindented but otherwise doesn't change.

Before the remodel Ritual was open until 10pm every day except Sundays. I would occasionally do some work there in the evenings. It was convenient, but it didn't seem like they had enough traffic to justify being open that late.

Meraki is completely cloud based. Firmware upgrades happen automatically although you have some options about when they get applied (and you get notification before hand).

Having built a software platform that integrated with the big enterprise wifi vendors, I can comfortably say meraki's is the most intuitive and easiest to use.

And here is a map of California's reservior levels: http://cdec.water.ca.gov/cdecapp/resapp/getResGraphsMain.act...

Its too bad no one has written a tool that keeps the familiar strace cli flags interface and output format but under the hood uses perf/ebpf. If such a tool existed I would be much more likely to reach for that than to fall back to strace.

Let me be clear, I think redis is a well engineered piece of software and I have been constantly impressed with the way antirez runs the project.

Specifically for the question of a locking service, I need more availability than what a single node can offer. I'm not sure if you are advocating for using redis cluster as a locking service, but since it intentionally doesn't offer write safety during a partition that does not seem advisable.

I personally wouldn't use redis for anything besides a cache.

As a long time Cassandra user its easy to forget that some of Cassandra's semantics will be surprising to new users. That being said, if you are considering adopting an AP database it really is important for you to know the details about how write conflicts get resolved. This is perhaps the biggest difference between Cassandra other databases like Riak and ought to be part of your decision making process instead of a surprise you run into later.

That being said, using Cassandra for distributed locks is a terrible idea. I can't think of any way in which Cassandra would be better than using {Zookeeper,etcd,consul}. Trying to force a database to do something it really isn't designed for will almost always lead to disappointment (and often resentment) of said database.

Will requiring salts break ms-chap-v2?

Interesting. A bunch of my old dead YouTube RSS feeds suddenly had new posts (of old videos) in them this week.

They had killed off public rss feeds but you could still get an rss URL if you were singed in and subscribed to the channel.

Thank you for your general civility on the lists. I'm glad that you are on the PMC.

I've been a Cassandra user for 5+ years and have been watching the drama unfold on the mailing lists the past few months. I have no business relationship with Datastax and have never paid them money for any of their services (except for attending the Datastax sponsored Cassandra Summit a number of times). I'm not a committer but I have been an active member of the community opening bugs, participating in the user mailing list, Stack Overflow, maintaining a client library, etc.

From my perspective it seemed like the ASF board members had already prejudged the situation before engaging in any public discussions on the Cassandra mailing lists. The first interaction was about why Cassandra doesn't ship with its own client drivers[1]. The board member believed this to be a sign of Datastax "controlling" Cassandra because they have their own high quality open source client libraries. As a user and a former maintainer of a client library, this theory came off as completely ridiculous. The project has never shipped a production ready client driver in tree. It is simply impractical to be able to do that for all the languages for which there are drivers. I've got code in three different languages in production right now and none of them use Datastax drivers. If you read that mailing list thread, that is basically what everyone says on it (including the new Casssandra PMC chair), and yet the conclusion that the ASF board member takes away is that Datastax is controlling the project by having out of tree open source client libraries.

That ASF board member also got upset when a question on the mailing list was answered with a link to Datastax hosted documentation[2]. Again this seemed like an overreaction from the board member over a fixable problem as justification for a Cassandra shakeup.

Then recently there was a new wave of threads about Apache and Datastax[3][4]. Both sides come off looking pretty bad in these threads. Its clear that at this point a lot of people in the Cassandra community have negative feelings toward certain members of the ASF board. It also seems like those board members have become very defensive about what has transpired. Fortunately people have started to calm down and there has been a few reasonable emails from both sides.

From my perspective the ASF came off looking like they care more about the Apache trademarks than they do about the health of the community. I do believe there were some actual issues that were identified as places for improvement for the Cassandra community, but I don't think it was necessary to come in wielding a sledge hammer. It seems that the Cassandra board was not given an opportunity to fix the issues (mostly by increasing the number of project committers) before the board forced the changes. This has resulted in a lot of hurt feelings and a general sense of distrust between the Cassandra community and the ASF.

All that being said, I'm not particularly worried about Cassandra's future. I was sad to see Jonathan Ellis leave as the chair person, but hearing that Nate McCall was stepping into that position put a lot of my concerns at ease.

I hope that the Datastax folks know that the community appreciates all that they have contributed to the open source Cassandra project, even if the ASF doesn't.

[1]: https://lists.apache.org/thread.html/72a884fa8f35cbed23135c8...

[2]: http://www.mail-archive.com/dev@cassandra.apache.org/msg0914...

[3]: http://www.mail-archive.com/dev@cassandra.apache.org/msg1003...

[4]: http://www.mail-archive.com/dev@cassandra.apache.org/msg1002...

I loved this series. It inspired us to do similar experiments with SSDs as we were spec'ing out new servers. I highly recommend doing this so you get a feel for what SMART looks like for your specific SSDs. Its nice to be able to monitor that to have some idea when your SSDs are going to die, especially if most of your drives are aging together.

The most challenging thing for us is running a new enough kernel to get these features. While upgrading to a newer kernel isn't particularly hard, small companies don't have a lot of engineering resources to run kernels that aren't maintained by their distro of choice (usually on the LTS release).

The good thing is this is solved simply by waiting long enough. The bad thing is most developers can't just pick this up today without a bunch of extra effort.

If you are looking for something you can use with old kernels you should definitely checkout Brendan's perf-tools repo[1]. It takes advantage of older kernel features and works with things as old as ubuntu 12.04.

*Edit: Fixed Brendan's name

[1]: https://github.com/brendangregg/perf-tools

YES. We have a strict no-EBS policy. Our main concern is that historically EBS has been a big single point of failure that can take down an entire AZ or worse a whole region. There were a number of outages in 2010-2012 that really bad for EBS instances[1][2]. The rate of outages has certainly gone down since then, but its hard to trust a system that has burned you badly multiple times in the past.

There was a good post by Bryan Cantrill after one of those really bad outages[3]. While this post is from an AWS competitor, the arguments about the reliability of network storage are sound.

While the trend by AWS has been to move away from ephemeral storage, it doesn't seem like they are working to completely kill it off. d2 and i2 fill a lot of our storage node needs. For our compute nodes I could see us moving to a model of booting off ebs and then pivot rooting into a ramdisk root fs so nothing would touch ebs after boot.

[1]: https://aws.amazon.com/message/67457/ [2]: http://www.agilesysadmin.net/ec2-outage-lessons [3]: https://www.joyent.com/blog/on-cascading-failures-and-amazon...

Waste is a much bigger problem in the US than it is in other countries because fuel reprocessing is prohibited in the US. About 20% of the spent fuel is plutonium created from neutron activation of uranium 238. Another ~65% is stable fission products. The amount of dangerous materials is a lot smaller than what the US currently insists on burying.

The US has held the no reprocessing position since 1977 when Jimmy Carter put a stop to it. Carter was worried about nuclear weapons proliferation, and believed that stopping spent fuel processing would help with that by reducing the amount of available plutonium. It seems that he hoped other countries would follow the US' example, but everyone else in the world went on processing and the US now has a big nuclear waste storage problem.

IAM instance roles were only added in 2012: https://aws.amazon.com/blogs/aws/iam-roles-for-ec2-instances...

I found this guide to be pretty comprehensive: https://www.esev.com/blog/post/2015-01-pgp-ssh-key-on-yubike...

No. Besides some cracks in the sidewalk you can't tell that it has sunk. (I work across the street from the Millennium Tower).

This is by far best enjoyed on paper. Print one out and share it with your office!

How do you get `netstat -s` information out of ss?

I don't want to run it in an external process, I want to run it in a goroutine.

How easy is it to embed this into go tests? Right now I use goamz/s3test for that, but it has a lot of limitations.

I didn't realise that Jeff Barr has been doing these posts all the way back to 2006.