Leon

Can you explain?

I've got multiple lambda functions that need to be associated with each other for an AWS Simple Work Flow. For CI I've it set up to update the versions of each lambda in a project repo. During packaging and deployment I inject the configuration of the git sha so that the next lambda function in the workflow that is called is consistent. Once the new workflow lambda call-chain is in place I can test / validate the new environment and then roll over the lambda that starts the workflow.

What I need to make sure of is that all the lambda functions / roles are updated before the starter so that the workflow doesn't break, as there could be breaking changes between commits.

A suggestion would be to create a repo per lambda function, but that becomes a hassle to manage after a few dozen, and just throws in even more work on ensuring the order of updates necessary. It is easier to flow between commit versions.

Can Kappa support custom versions and aliases? That's been one thing I haven't seen able to be controlled via kappa config or command line, and it's been the reason I haven't used it.

I think you are right; and what you're saying reminds me of a story from Malcolm Gladwell about the 1981 Traveller Trillion Credit Squadron tournament [1] that Doug Lenat won. He used some type of genetic algorithm (he never released his source) to find that swarming the challenger with many small boats would dominate as a tactic. Miniature swarms, which drones are cheap enough and more than capable for, are not a tactic that people are use to. I fear that a swarm could be terrible in its destruction if used to hurt people, individually targeted or for mass harm.

[1] http://www.newyorker.com/magazine/2009/05/11/how-david-beats...

I'm agreeing with you because the alternative would make deployment processes of snapshotting built images for faster startup time against the law. If you couldn't use AMIs in AWS because the Oracle JRE is installed but instead are forced to install at launch time then that makes Oracle largely irrelevant to use in the cloud - no one wants to limit their startup time by a multiple minutes to download and install for a scaling event (and barring any network issues on their servers if hosting the installer package is seen as distribution as well). I haven't heard of any issues with moving around your own internally built virtual images with Oracle Java if you have accepted the licensing agreement for during the build and snapshot process, and using docker seems no different.

That can help with fingerprinting. Any entropy escaping from a users session is useful.

There is a lot more to parenting than just breastfeeding (which can be pumped and stored ahead of time - it's not always practical).

I believe you can hack an if statement by doing a length, substring and equality comparison to make it equivalent.

CoreOS and SELinux together is pretty secure if set up properly; even if you broke out of a container you wouldn't be able to do anything, even start a process. But still, yeah, in a unikernel there is no 'breaking out' at all.

This isn't entirely what happens. For most doctors at their first jobs the hospitals will write out most, if not all, of their medical school loans depending on how much there are. They use this as signing bonuses and to tempt doctors to their hospital.

It's not always an option to host and manage a registry, some parts it's easier for the customers to rely on a registry service like quay, in which case it can make a difference for some images to think about layering. But you are right, s3 is fast and that's one of the reasons I'm glad Deis moved to support s3 out of the box.

Once you've automated the entire process of bringing up a container cluster with monitoring, metrics, logging, etc then it becomes trivial to make as many as you want. The same is done with separate virtual networks for security concerns.

It becomes as simple as asking what name the cluster should have.

It also makes sense from managing resource concerns to some extent, such as a cluster with cheap instances for low priority applications but need HA support or a cluster with beefy instances in a subnet that has fewer hops should be used for edge tier applications.

I also do what the other poster does, but we take it a step further and make sure that the layers on the image have smaller and more variable layers near the last layer add. On instance startup we can do a docker pull and bring down only a few k of bytes for docker image updates. This way we can update the ami less often (which it takes longer anyway) and we don't worry too much about pushing updates to the container repo without having to batch ami builds for quicker turn around deployment.

Wouldn't that end up as the person with the most money has the biggest voice?

Superfish was because the laptop manufacturer bundled adware which added its own root certificate that was broken, they aren't able to add root certificates in this case.

Am I the only one that doesn't entirely enjoy gamification of everything? What's wrong with just writing software?

There aren't always great reasons behind great hacks.

We can appreciate them for the ideas they present, the interesting implementation of features, and the what-if's that can come from expanding the hack further.

How is this NASA's failing? A congressional mandate to fund and build this regardless of the agencies needs is the failure. There's no need to display the agency in a bad light, especially if you have the information about what happened and show it was caused by other government involvement.

As someone who had their gallbladder out with complications afterwards, I feel like this article isn't realistic to the after effects. It's great the author did not have any, but before they recommend people go have it removed they should know that someone might be tied down to taking medicine daily for the rest of their life in the not-so-rare situation that their body disagrees with not having a gallbladder.

I use the Sansair device - it seems pretty solid and is very easy to use. I'm not sure how much I'd trust a hack I would do that involves water and electricity, but others who work with hardware more I think would have no problem. The device is incredibly dumb, it's really just a circulator, heating element, and a decent voltage regulator with a thermometer and some basic logic gates to raise or lower the voltage when the temperature is closer or further away from the target.

The other poster says it proves operations won't happen again - does it do both?

I have not used Rust before; does working with statistical analysis of runtime environments hinder debugging? In a multithreaded environment - does it pause the world for its runtime analysis or are there locks on shared resources representing ownership of individual objects, or does it do copies on writes of resources for idempotent operations as the references are moved around environment for lockless operations?

1) It is fun and feels nice / is appreciated to make food for friends and family.

2) I ballpark what I might want when grocery shopping but generally make serious plans for a meal for several people.

3) Sous vide chicken is currently popular. Grilling and smoking meats is the second most popular food prep I do, with baking or pan-frying fish a third.

4) No but I stay away from red meats, pork, and carbs because I feel better not eating them (so chicken fish and vegetables are most of the menu with some grains).

5) I'll agree with others - cooking is a fun event for friends to participate in.

He/she is implying that Doctor's want to keep people alive so that they can bill them for services rendered longer and make more money.

It's not pure nicotine, but a mixture of propylene glycol or vegetable glycol, flavoring, and then nicotine.

Some of the off the shelf disposable / prepackaged e-cigs aren't powerful enough to have a strong vaporization of the solution. When you're refilling yourself, it becomes substantially cheaper (maybe a few dollars for a month of heavy usage?), and with the higher end kits you can program your voltage / amperage settings on curves for your preference as you in inhale.

I generally go by the saying, baring any existing req's that abstraction patterns would help with:

'Code to use, Refactor to re-use'

Reminds me of the problems with Cowboy Coders. Many people would agree with your second approach.

http://c2.com/cgi/wiki?CowboyCoder http://c2.com/cgi/wiki?CowboyCoding

Login credentials or an authentication token? It's pretty standard to use an auth token in situations such as emails to protected content, considering that users profiles are blocked to non-members. To allow you to do a follow through from an email link it is necessary to introduce a way to automatically log yourself in through a click. You'll see the same email behavior from most websites you have an account for and you've allowed to send you emails. The trust chain that this is generally considered OK is that the email has gone through a two way verification for that account you've signed up for, so a uniquely generated auth token emailed is akin to a forget password at that point.

The security failure was mostly on your part, but also on the sites for not conveying a notice that email links that automatically authenticate you are in emails.

Sharing any directly copied link information from an email to a set of anonymous users, especially as unreputable as you have stated, is unadvised.

Yes, that is the question to ask!

What bothered me most about this essay was one point near the end: "Ask yourself, 'Am I being grumpy right now?'. If the answer is yes, then stop!"

This is a non-realistic response to an issue of moral with a real underlying cause. What bothers me most about this is that it will only cause further issues with the developer as they cover the problems with the group they are working with. Their proposed solution is what someone would say to someone suffering from depression, 'Just stop being unhappy and cheer up!'.

This does not work, what they suggest will not work and will only further the decline of morale, company culture, and retention of developers. Grumpiness is a symptom of underlying causes within a company.

The information is usually already publicly available : for examples the facebook graph api uses the same setup for some of their basic api methods (such as letting a site log you in through facebook) - base64 encoded json user data and an hmac signed with a private key + timestamp. Since the data is already publicly available (it's your facebook user id and other publicly available data), there's no need to use a more costly encryption algorithm. The hmac is there to confirm to the server who manages whichever associated online service that also created a facebook app you just gave access your profile to that this is good data, since they've got the secret on their end that the staff registered with on facebook. HMAC is fast.