trevorhartman

They finally updated the status page: https://status.pagerduty.com/posts/dashboard

Looks like they're back up for me. They were down for about 15 minutes. But zero acknowledgement on the status page.

They've been down for at least 10 minutes but their status page still shows everything up: https://status.pagerduty.com/posts/dashboard

Does PagerDuty use PagerDuty? Maybe they don't know they're down.

I've wanted something like this for a long time!

Related: If you want to understand how and why the American Healthcare system is broken, read the excellent book An American Sickness: How Healthcare Became Big Business and How You Can Take It Back by Elisabeth Rosenthal.

16GB is the max :( http://www.apple.com/macbook-pro/specs/

Any word on max memory? 16GB is standard on 15" but can it be upgraded to 32GB?

I've been using kube-lego [0] to request/renew certs from LE. It doesn't handle the DNS for you automatically, which has the benefit of working outside of GKE and downside of having to configure DNS yourself. It's been working well.

[0] https://github.com/jetstack/kube-lego

Docker image is up! https://hub.docker.com/r/library/alpine/tags/

Awesome. I've been waiting for the DNS fix (along with everyone else) so I can run it on Kubernetes.

I don't see a new Docker tag yet: https://hub.docker.com/r/library/alpine/tags/ Anyone know when it's expected to hit? Edit: here's the issue tracking it https://github.com/gliderlabs/docker-alpine/issues/178

All the links in the docs TOC are broken: https://github.com/syl20bnr/spacemacs/blob/master/doc/DOCUME...

One solution that I've adopted: never use Finder.

How do I upvote myself again?

Sometimes I like to spend my karma by posting crap like this. Also: http://2.bp.blogspot.com/-osQ0QDYcXJ8/VGZqisyHLYI/AAAAAAAAAY...

I don't get it. Haven't they ever heard of vim/emacs?

I don't want to sit in the front seat and I hate those stupid mustaches.

I found Learn You a Haskell to be one of the best programming books I've ever read and no I'm not joking. It's a work of art.

Dash has become a part of my standard workflow in the last few months. It's great and it's always getting better. @kapeli responds quickly to feedback/questions on Twitter. I use it with Alfred and the vim plugin.

Jeremy, I really appreciate this post and all the excellent content over at Math ∩ Programming. Thanks, and please keep it up!

Cool, but if you can learn electrical engineering concepts, you can learn to copy/paste/hack some ultra-simple C too :)

Years ago, perhaps. Can't remember a specific instance.

Yes, but I don't know the answers to these questions because I know to avoid code like this.

jQuery or <jQuery-compatible substitute> is one of the few things I don't have to think twice about before including in EVERY WEB PROJECT I EVER WORK ON before doing anything else.

Next up: you might not need <insert abstraction>.

Really?! What does "need" mean? Go write assembly.

https://github.com/tpope/vim-fireplace is where it's at for vim/clojure tools.

They may appear to be returning a fresh copy, but internally much of the structure is shared rather than copied. See Persistent data structure: http://en.wikipedia.org/wiki/Persistent_data_structure

I'm not suggesting dumbing-down their product in any way. I'm talking about a usable, well-designed CLI and web console.

They've made quite a few incremental improvements over the years, but it's still mediocre at best.

Imagine how easy-to-use AWS would be if AMZ had anywhere close to the level of focus on usability that Heroku consistently demonstrates.

To rebase or not is a religious war. Also on HN today/yesterday: - git pull --rebase until it hurts: http://jrb.tumblr.com/post/49248876242/git-pull-rebase-until... - Please, oh please, use git pull --rebase https://coderwall.com/p/7aymfa I've seen a ton of posts like this on both sides.

The non-chronological history is unfortunate. In practice, when `git pull --rebase`ing several times per day the way we do, commits will only end up a few minutes out of order, which won't affect queries like `git log --since=1.week.ago`.

One of the things we optimize for is early integration. I conceptually like his recommendation, but I think it'd slow us down since we're always depending on each others' commits.

> Don't fix the symptom by rebasing endlessly, figure out your problem. And you do have a problem, because not only are you writing crap code, but you're committing it as well!

Translation: make sure your code is perfect before you commit. That's ridiculous.

> You really, really need to collaborate in real-time with another dev. and so must share all your code? At this point you're pair-programing - maybe look up GNU screen & its 'acladd' command to allow you to share a terminal with your collaborator. Or just tell each other when you're about to commit.

False and ridiculous.

I am a fan of heavily rebasing non-public history. Non-public obviously meaning local branches, but also, a loose definition for us is a public branch that you own and are confident no one else is working on. (If GitHub let us fork private repos without counting against our private repo limit, we could have true private remote branches). Sometimes I commit things very cleanly, creating separate commits for each concern, and sometimes I don't. When I don't, I'll often do a quick interactive rebase to re-group changes into logical commits–the purpose being a clean history that makes it easy to read/revert/cherry-pick/bisect specific, individual changes.

So there are pros and cons to both philosophies - it just depends on what you're optimizing for. This guy is writing in support of his particular needs, but makes the mistake of asserting they are the best or only.

Also, I think a future version of git could address the non-chronological history issue, which was the only con I'm aware of.