It’s so weird to see all these fancy and barely affordable even to me now restaurants and shops with “refugees welcome here” signs.
I know they mean well, or are just cynical, but when we were in that situation Panda Express was an unforgettable treat.
Man on Red Square shouts, ‘Brezhnev is an idiot!’ He gets sentenced to 15 years: five years for insulting the Soviet leader, and 10 years for betraying a state secret.
The CTO is an idiot. BTW if you know what company leave a comment…
I don’t know what this company is, but if their CTO has never done it himself, I am baffled how he (it had to be a he) became one. I totally made this mistake at the old company. Dropped a production table that everything depended on. It has to happen to everyone, at least (hopefully) once. People in my team, back when I had a team, have done it too. I made sure to congratulate them on this rite of passage, and how having to go beg the dba (nicely) to resurrect what’s lost from backup, is a part of it, and how this is why we have paranoid rules about production. every single boss I had has always been super understanding. For the same reason.
Unlocking the value of data is a primary goal that AWS helps our customers to pursue. In recent years, an explosion of intelligent devices have created oceans of new data across many industries. We have seen that such devices can benefit greatly from the elastic resources of the cloud. This is because data gets more valuable when it can be processed together with other data.
At the same time, it can be valuable to process some data right at the source where it is generated. Some applications – medical equipment, industrial machinery, and building automation are just a few – can’t rely exclusively on the cloud for control, and require some form of local storage and execution. Such applications are often mission-critical: safeties must operate reliably, even if connectivity drops. Some applications may also rely on timely decisions: when maneuvering heavy machinery, an absolute minimum of latency is critical. Some use cases have privacy or regulatory constraints: medical data might need to be stored on site at a hospital for years even if also stored in the cloud. When you can’t address scenarios such as these, the value of data you don’t process is lost.
As it turns out, there are three broad reasons that local data processing is important, in addition to cloud-based processing. At AWS we refer to these broad reasons as “laws” because we expect them to hold even as technology improves:
Law of Physics. Customers want to build applications that make the most interactive and critical decisions locally, such as safety-critical control. This is determined by basic laws of physics: it takes time to send data to the cloud, and networks don’t have 100% availability. Customers in physically remote environments, such as mining and agriculture, are more affected by these issues.
Law of Economics. In many industries, data production has grown more quickly than bandwidth, and much of this data is low value. Local aggregation and filtering of data allows customers to send only high-value data to the cloud for storage and analysis.
Law of the Land. In some industries, customers have regulatory or compliance requirements to isolate or duplicate data in particular locations. Some governments impose data sovereignty restrictions on where data may be stored and processed.
Today, we are announcing the general availability of AWS Greengrass, a new service that helps unlock the value of data from devices that are subject to the three laws described above.
AWS Greengrass extends AWS onto your devices, so they can act locally on the data they generate while still taking advantage of the cloud. AWS Greengrass takes advantage of your devices’ onboard capabilities, and extends them to the cloud for management, updates, and elastic compute and storage.
AWS Greengrass provides the following features:
Local execution of AWS Lambda functions written in Python 2.7 and deployed down from the cloud.
Local device shadows to maintain state for the stateless functions, including sync and conflict resolution.
Local messaging between functions and peripherals on the device that hosts AWS Greengrass core, and also between the core and other local devices that use the AWS IoT Device SDK.
Security of communication between the AWS Greengrass group and the cloud. AWS Greengrass uses the same certificate-based mutual authentication that AWS IoT uses. Local communication within an AWS Greengrass group is also secured by using a unique private CA for every group.
Before AWS Greengrass, device builders often had to choose between the low latency of local execution, and the flexibility, scale, and ease of the cloud. AWS Greengrass removes that trade-off—manufacturers and OEMs can now build solutions that use the cloud for management, analytics, and durable storage, while keeping critical functionality on-device or nearby.
AWS Greengrass makes it easier for customers to build systems of devices (including heterogeneous devices) that work together with the AWS Cloud. Our goal is not to provide an alternative for the cloud, but to provide tools for customers to use the cloud to build applications and systems that can’t be moved entirely to the cloud. Using AWS Greengrass for local execution, customers can identify the most valuable data to process, analyze, and store in the cloud.
With AWS Greengrass, we can begin to extend AWS into customer systems—from small devices to racks of servers—in a way that makes it easy to do the things locally that are best done locally, and to amplify those workloads with the cloud.
Getting started: AWS Greengrass is available today to all customers, in US East (N. Virginia) and US West (Oregon). You can get started by visiting http://aws.amazon.com/greengrass.
We’re so excited to introduce America’s new astronauts! After evaluating a record number of applications, we’re proud to present our 2017 astronaut class!
These 12 new astronaut candidates were chosen from more than 18,300 people who submitted applications from December 2015 to February 2016. This was more than double the previous record of 8,000 set in 1978.
This Washington native graduated from the U.S. Naval Academy with a Bachelor’s degree in Systems Engineering. A Gates Cambridge Scholar, Barron earned a Master’s degree in Nuclear Engineering from the University of Cambridge.
She enjoys hiking, backpacking, running and reading.
Zena is a native of Virginia and completed a Bachelor of Science degree in Biology and Master of Science degree in Marine Sciences at The University of North Carolina, Chapel Hill. Her research has focused on microorganisms in subsurface environments, ranging from caves to deep sea sediments.
In her free time, she enjoys canoeing, caving, raising backyard chickens and glider flying.
Raja is an Iowa native and graduated from the U.S. Air Force Academy in 1999 with Bachelor’s degrees in Astronautical Engineering and Engineering Science. He continued on to earn a Master’s degree in Aeronautics and Astronautics from Massachusetts Institute of Technology and graduated from the U.S. Naval Test Pilot School.
He has accumulated more than 2,000 hours of flight time in the F-35, F-15, F-16 and F-18 including F-15E combat missions in Operation Iraqi Freedom.
This Colorado native earned a Bachelor of Science in Electrical Engineering from the University of San Diego and a Master of Science degree in Systems Engineering from the Naval Postgraduate School. He graduated from U.S. Naval Test Pilot School.
He has more than 1,600 hours of flight time in 28 aircraft, 400 carrier-arrested landigns and 61 combat missions.
Bob is a Pennsylvania native and earned a Bachelor’s degree in Aerospace Engineering from Boston University. He is a graduate of the U.S. Air Force Test Pilot School, where he earned a Master’s degree in Flight Test Engineering. He continued on to earn a Master’s degree in Aerospace Engineering from the University of Alabama.
During the last five years, he has served as a research pilot at NASA’s Johnson Space Center.
Nicknamed “Woody”, this Pennsylvania native earned a Bachelor’s degree in Aeronautics and Astronautics from the Massachusetts Institute of Technology (MIT) and a Doctorate in Electrical Engineering and Computer Science from the University of California, Berkley.
This California native trained and operated as a Navy SEAL, completing more than 100 combat operations and earning a Silver Star and Bronze Star with Combat “V”. Afterward, he went on to complete a degree in Mathematics at the University of San Diego and a Doctorate of Medicine at Harvard Medical School.
His interests include spending time with his family, volunteering with non-profit vertern organizations, academic mentoring, working out and learning new skills.
Robb is an Alaska native and earned a Bachelor’s degree in Mechanical Engineering from the University of Denver, before going on to complete a Master’s degree in Materials Science and a Doctorate in Engineering at the University of California, San Diego.
He is a private pilot and also enjoys playing piano, photography, packrafting, running, cycling, backcountry skiing and SCUBA diving.
This New York native earned a Bachlor’s degree in Aerospace Engineering with Information Technology at the Massachusetts Institute of Technology, followed by a Master’s degree in Aerospace Engineering from the Naval Postgraduate School.
She is also a distinguished graduate of the U.S. Naval Test Pilot School and has accumulated mofre than 1,600 hours of flight time and 150 combat missions.
This Texas native earned a Bachelor of Science degree in Aerospace Engineering at the University of Kansas and a Master of Science degree in Aeronautics and Astronautics from Purdue University.
In her free time, she enjoys working in the garage, traveling, surfing, diving, flying, sailing, skiing, hiking/orienteering, caving, reading and painting.
Frank is a Florida native and graduated from the U.S. Military Academy and earned a Doctorate of Medicine from the Uniformed Services University of the Health Sciences.
He is a board certified family physician and flight surgeon. At the time of his selection, he was serving in the 10th Special Forces Group (Airborne).
This Colorado native earned a Bachelor’s degree in Geological and Environmental Sciences at Stanford University, and a Doctorate in Geology from the University of California, Los Angeles (UCLA).
She enjoys soccer, rock climbing, skiing and creative writing.
The cult of overwork that dominates tech came to the fore this past month, and Susan Fowler led the discussion:
This week’s Twitter debate reminded Susan Fowler, the former Uber engineer whose allegations of a toxic work culture kicked off an independent investigation, of The Protestant Ethic and Spirit of Capitalism, the major work authored by German sociologist Max Weber. “There’s this concept of the ‘Protestant work ethic’ that’s intrinsically related to capitalism, the idea being that, to the Protestant, ‘hard work’ is a religious duty, a profession of faith and devotion,” she tells WIRED. “The harder you work, the better a Christian you are, the better chance you have of salvation.”
The ideology has become so powerful, it’s had a strong downstream influence on startups, the types of markets these companies develop, and even the way they advertise contract work to their potential labor supply. (A recent New Yorker article about the gig economy’s marketing style called Lyft “ghoulishly cheerful” for celebrating the fact that a driver worked through her last week of pregnancy.)
[…]
Fowler says the pressure manifests itself in two ways. Either management and founders tell employees they need to work long hours or they don’t belong. Or bosses don’t explicitly demand 10 to 14 hour workdays, “but employees who don’t work these hours are denied promotions or are seen as ‘not being cultural fits’ or ‘not being committed or passionate.’” Fowler has seen both examples in practice, including employees with families who “can ‘only work ten hours,’ and therefore aren’t ‘cut out’ for the industry.”
It “definitely limits the idea of a ‘someone who belongs in tech’ to the small section of the population that is young, has little to no responsibility, and honestly who doesn’t know any better,” Fowler says.
David Heinemeier Hanson (of Ruby on Rails fame) was another vocal detractor of the work-till-you-drop mentality, and the leading voice in support of overwork is Keith Rabois, a venture capitalist who may have incited this cascade of chatter with a single incendiary reply:
Isn’t it surprising that we know so little about ourselves and our society that we really don’t know which of the two strategies – working ‘harder’ (meaning longer hours) or working ‘smarter’ (meaning fewer hours, but more productively) – is better (meaning leading to both long-term success and well-being).
tinfoilparachute 