Watching the launch, I noticed they seem to have finger rests below the screens. I wonder if this is the reason.

Can't do much about the time it takes light to get here, so I guess the answer is we'd have to learn to love 75 minute ping :)

Alcubierre warp drive powered Sneakernet?

If you can't be with the one you ping, ping the one you're with.

> While it is easy to bash on an inanimate object, there are some very dedicated and empathetic people who care deeply about the project. Some of those people do this work in their off-hours and some to this work as part of their daily work activities AND also in their off hours.

I've been using Jenkins heavily over the past year since a client of our purchased the enterprise version. It was billed to me as a mature open source product that has been refined over the years by people trying to optimize their dev operations. While I'm sure some people really care about it, the user experience is so utterly disappointing it's almost impossible to imagine how it got to this state without neglect.

Even if you ignore all the complicated stuff, the web UI is embarrassing. While I don't suggest a "pretty" UI is necessary for devops, I would think you'd have a quick win just by having some people re-style the existing UI to make it look and feel like something built this century and not require a dozen clicks to get to important information. There are also bugs that are so painfully obvious it makes me wonder how they still exist. An example is if your Github branch has a slash in it (eg. feature/something) you get a 404 error if you try to navigate to that builds' results.

There are also features that appear to have almost no value yet are in the core UI and clearly took some time to build. The weather icons representing various permutations of previous build states is one ridiculous example that comes to mind.

I would respectfully suggest you run through some real world Jenkins experiences like the ones mentioned in the article. Also setting up a new server, configuring non-trivial SCM settings, debugging Jenkinsfiles, etc. To echo the article's sentiment - it feels like I'm constantly fighting with Jenkins to do what I need instead of being guided into a mature set of features.

Conversely - Octopus Deploy is a related product I have been using alongside Jenkins which has been an absolute joy to work with. Everything from initial setup to configuring its agent software on host servers has been straightforward. It has a simple, elegant UI that provides access to important information and actions where you would hope to see them. And most importantly - everything works. I have yet to encounter a bug or experience any broken UI states.

I'm glad to hear CloudBees is making some effort to improve things and I hope PMs like you continue to be involved in the community and solicit feedback, even if it's hard to hear sometimes.

Hi I exist

> And, if the best minds are employed in large corporations to work out how to persuade people to click on online advertisements instead of cracking hard-core science problems, not much can be expected to change in the years to come.

This is so sad

> It failed spectacularly, but they're already talking about building a bigger one

Awww it isn't that bad. They found the Higgs and at least verified we need to look at higher energy levels to find anything new.

It is rare because other systems that form these objects are VERY far away (trillions of KMs). Imagine trying to slide a hockey puck from one end of a hockey rink to the other, but have it pass through a small (~1M) circle at the far end from you. If you took 1000 attempts even randomly, you'd probably hit the circle by accident at some point. Now someone else is also shooting at the circle, but they are 50,000KM away. Suffice to say no matter how many attempts that person takes, it will be significantly more rare to see their puck cross through the circle than yours.

To this point, here is the 2nd last sentence in the article:

> So, if you enjoy your swears, and being awake really late, and have a messy room, don't worry. You have a higher IQ than most!

300k is nothing given the potential profit of this idea working. Tesla probably spends more than 300k on R&D every week.

It's hidden way down at the bottom, but I found the Timeline to be my favourite part :)

Edit: Can't see to format it correctly, just check the original source.

This one?

  2016/12/26 05:48 Report vulnerability to GitHub via HackerOne
  2016/12/26 08:39 GitHub response that have validated issue and are working on a fix.
  2016/12/26 15:48 Provide more vulneraiblity detail.
  2016/12/28 02:44 GitHub response that the fix will included with next release of GitHub Enterprise.
  2017/01/04 06:41 GitHub response that offer $5,000 USD reward.
  2017/01/05 02:37 Asked Is there anything I should concern about if I want to post a blog?
  2017/01/05 03:06 GitHub is very open mind and response that it’s OK!
  2017/01/05 07:06 GitHub Enterprise 2.8.5 released!

Or this one?

  Day 1 - Setting VM
  Day 2 - Setting VM
  Day 3 - Learning Rails by code reviewing
  Day 4 - Learning Rails by code reviewing
  Day 5 - Learning Rails by code reviewing
  Day 6 - Yeah, I found a SQL Injection!