3amOpsGuy

Linked in is the only social network that's managed to link me to other people in ways i cannot explain.

An example: I had a real life connection to a trainer, i studied for an industry qualification with him. I had zero online line connections to him. Somehow linked in put us together.

His profile mentioned nothing about taking that course, mine mentioned nothing about attending his course. My work handled all the procurement side of things so he had no access to my email address or anything like that.

In credit to linked in, this guy happened to be the best trainer i'd ever studied with so i was actually pleased to see the recommendation. Still wondered how they managed it though!

I agree, it's one of the factors that tipped me into pre-ordering (no word on my delivery yet though!)

There doesn't appear to be that much spare capacity, at least on the 7010's FPGA, around 2k cells IIRC? Certainly won't be creating a bitcoin miner in that :-)

Still the most interesting bit of hardware to come down the pipe yet.

Middle paste has never been a reliable feature, (are you pasting from X clipboard or GNOME clipboard? - it changes depending on context). For that reason alone, i can see a case can be made for this change.

At first glance it seems like a backward move to me, but i'd be at least willing to give the idea a try.

GNOME 3 takes a lot of heat, they're one of the few actually pushing the envelope so it's to be expected i suppose.

A little more encouragement and a little less boring complaints "stating the obvious" would go a long way.

I didn't know about them until recently. To be honest, my first impressions of their site weren't great, just based on visuals i assumed it was some syndicated content with advertising.

How wrong was i. Consistently one of the best feeds in my feedly these days.

That's just the dev concerns.

Here's a rather contrived example but it illustrates the idea i'm getting at: "Will the inventory agent software be able to login to audit this container environment when they're done building their release?"

Skills.

Most developers are not full-stack aware - nor should they be. Having a pack of generalists drive a product is sure to reduce momentum.

Better that the contract is "here's a platform you can deploy to" than "here's some CPU time, break it and you get to keep both pieces"

It's kinda cliched for someone with a username containing "ops" to come out and say "i love checklists", but i do!

I've never found a better tool for communicating what to do and in what order. Everyone just understands them, with zero training. You can even play with the format slightly and people still get it, e.g. break out a formal time column? Sure! People just start using it.

I especially like them for high pressure situations. E.g. for handling prod outages i've consistently found checklists work better in practice than flow charts, knowledge bases, call trees... etc.

I use them for many things, from the fairly benign (releases?) to the relatively rare (new joiners).

I recommend, just based on my experiences so may not apply in all environments, using a simple web based app to handle all your check lists. It'll be accessible from any device, without installing anything up front.

A couple of small extra features will make it infinitely more useful:

1) Allow for both a "ticked" / done status and a "working on" / "i've grabbed this one" status. Display the user who's grabbed it and the time they grabbed it.

2) Allow for checklists to have all their boxes reset on a schedule, e.g. daily reset of the "start of day" check list.

3) Archive completed checklists - they capture useful information about who and when, so I don't bin them when they're completed

"That said, the ISPs objections are likely cost"

And rightly so. If this goes through, i'd like to see the ISPs add a line item to everyone's bill calling this out in plain sight to all their customers. "This month you paid an extra #1.75 to cover the costs of Government censorship infrastructure we're required to purchase / install / maintain.

I don't get the extra emphasis on Netflix here either.

Netflix are part of the content industry, it's not that they're the best of a bad bunch, they're actively more open than some artists.

Reduce the quality quotient (severely, like .98 -> .3) and don't cut the resolution as far, e.g. Keep 2x the pixels.

Much better appearance for the same file size.

I like the ingenuity but how would we track when the page has been left - conceivably I could delete an account on Friday then click undo on Sunday.

I guess if it immediately gets soft deleted and in a maintainance batch gets purged. Until maint runs the undo link could still work (although it would still only display until they left the page).

Undo's, yes!

Power users aren't tripped up with an annoying confirmation. Novice users can revert. This seems a much better paradigm.

Are there any cases where this doesn't make for good UX?

This is a really good idea. We already buy in site licences for the Uncle Bob series (kinda comparable idea for programmers), i imagine many other places are the same. This model works quite well.

Does this need funding? I'd be more than happy to chip in some pennies towards this effort.

In my experience it's surprisingly hard to recruit good quality ops people. Actually it's hard just to get recruiting agencies to filter well for ops jobs but that's another story... Anything that might help this is worthwhile investment.