krishicks

Using the `fly` CLI allows you to know what changes are being made when you update the pipeline (it shows a diff), and when your configuration is invalid (or when the update fails for another reason).

More links:

Concourse's own CI: https://ci.concourse.ci and Concourse Slack: http://slack.concourse.ci

I started basic barbell training 3 times per week, including squats and deadlifts, about 3 months ago.

I guess I didn't notice any problems with hip flexors when sitting on a few very long flights recently, so maybe you're right.

I'm coming up on my 5-year standing anniversary.

One thing I've noticed that the video doesn't mention is what it's like to work at a sitting desk after having exclusively stood so long.

It sucks.

My hip flexors aren't used to sitting for more than short intervals, which means I can't work at a sitting desk for a whole day without having hip pain.

This was an issue last year when I did some consulting at a company where they didn't have any standing desks available. (At some companies I've actually started the standing desk trend, but this Major US Cable Company was having none of it).

You can use Lattice for that: http://lattice.cf/docs/

I enjoyed the piece. It felt like reading an episode of RadioLab.

Hmm.

File numbering is already available via `git add -i`.

    git add -i
    u
    1,9
    <return>
    q

And you get a more powerful tool, and you're using regular git.

This can also be done safely from the git cli with the `--force-with-lease` option. `--force-with-lease` will only do the push if the latest ref you've fetched from the remote matches the current ref of the remote. There's a few options you can give it, too, so I recommend reading the docs: https://git-scm.com/docs/git-push

The biggest selling point for it in my view isn't Force Click but the uniformity of the trackpad. You can press anywhere on the trackpad and it takes exactly the same amount of force to make a click. On the previous mechanical glass trackpads the amount of force required to make a click goes up the closer to the keyboard you press the trackpad. I'm now happy to use my thumb to click the trackpad because I can click it just under the spacebar easily.

It's very obvious when going back to the trackpad on my 2013 rMBP, which feels (and sounds) like junk in comparison.

On the 2013 rMBP I use the "Tap to click" setting so I don't have to press the awful button. On the 2012 MacBook I don't; it's just not necessary.

A more advanced version of this can be seen in the some of the tests for CloudFoundry's new Diego runtime: https://github.com/cloudfoundry-incubator/runtime-schema/blo...

The 'table' consists of an array of calls to constructors of structs that contain fields which are used to set up the context for each test, set value expectations specific to that test, and whether certain tests in shared examples apply to that context.

There is a certain level of cognitive overhead involved in understanding this method of writing tests, to be sure, but the benefits (concise expression of a huge matrix of variations) outweigh the costs (massive duplication, and therefore comprehension of thousands of more lines of test code).

It's important to note that this style of test is really best for the situation where there is a large matrix of things you'd like to test.

The example I linked included ~70 different contexts, each of which is being run through the large Test() function at the bottom: https://github.com/cloudfoundry-incubator/runtime-schema/blo...

They seem to have only fixed this on Yosemite.

I can reproduce the bug on Mavericks and Chrome 41.0.2272.118 after the 2014-004 update for Mavericks.