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.
"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 :-)"
Depends on whether you'd like to use the Epiphany chip or not, as the FPGA logic used to interface with the Epiphany can be used for your own projects too (albeit with the catch that you lose the ability to access the full potential of the Epiphany chip). I'd be interested in using the Parallella board as a cheap Zynq dev board.
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.
Everywhere I've worked, the developers have needed to figure out the dependencies requires to get the software working. Sometimes with the assistances of a dev-ops or ops guy.
All this does is say "while you figure that out, put it in a script". First, it means we can test the dependencies easily by re-running the script to see that it actually accurately reflects what needs to be done.
Secondly, when you're done, you have a reproducible deployment environment that massively simplifies ops and dev: Ops can decide on upgrades, re-run the scripts, have QA run their tests and know the upgrade won't break stuff in production. Dev can make code changes and be confident that what they hand off will actually work in the production environment because they've test deployed it on VMs built from identical templates.
As long as your team can figure out how to deploy the software they write, they can do this. If they can't, you have bigger problems.
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?"
The point is : PaaS give you the advantages of shared hosting, but a good PaaS isolate properly all apps. It's definitively a good way to focus on dev and let a ops and constraint on trained teams.
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
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.
Would something like Keycard[1] work for locking the screen when you're not nearby?
I wonder if it could be set to lock at boot unless your phone (or BT headphones or whatever) is nearby.
I doubt this can be all that secure since it can be downloaded from the App Store, I'm pretty sure that means it can be force quit (it could not prevent this key combo since its restricted in the sandbox). It may be just enough.
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!