You are an AI systems engineer designing a greenhouse automation system.
Your job is to combine the requirements from three stakeholders — a grower, an engineer, and an operator — into a coherent, testable control-system design and a concrete action proposal.
Use the complete information below. Treat this as an illustrative engineering exercise, not a system authorized to control real equipment.
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real
| cordova plugin add aerogear-cordova-push | |
| Fetching plugin "aerogear-cordova-push" via plugin registry | |
| npm http GET http://registry.cordova.io/aerogear-cordova-push | |
| npm http 404 http://registry.cordova.io/aerogear-cordova-push | |
| Error: 404 Not Found: aerogear-cordova-push | |
| at RegClient.<anonymous> (/Users/kpiwko/.nvm/v0.10.40/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:268:14) | |
| at Request.self.callback (/Users/kpiwko/.nvm/v0.10.40/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/npm/node_modules/request/index.js:148:22) | |
| at Request.emit (events.js:98:17) | |
| at Request.<anonymous> (/Users/kpiwko/.nvm/v0.10.40/lib/node_modules/cordova/node_modules/cordova-lib/node_modules/npm/node_modules/request/index.js:876:14) | |
| at Request.emit (events.js:117:20) |
| /Users/kpiwko/devel/mobile/ag/aerogear-unifiedpush-server-integration-tests/tests/integration/src/test/java/org/jboss/aerogear/unifiedpush/test/MessageSendTest.java:687: error: no suitable method found for with(InstallationWorker,Variant) | |
| installations.addAll(ups.with(worker, variant).findAll().detachEntities()); | |
| ^ | |
| method UnifiedPushServer.<ENTITY#1,ENTITY_ID#1,BLUEPRINT#1,EDITOR#1,PARENT#1,CONTEXT#1,WORKER#1>with(WORKER#1) is not applicable | |
| (cannot infer type-variable(s) ENTITY#1,ENTITY_ID#1,BLUEPRINT#1,EDITOR#1,PARENT#1,CONTEXT#1,WORKER#1 | |
| (actual and formal argument lists differ in length)) | |
| method UnifiedPushServer.<ENTITY#2,ENTITY_ID#2,BLUEPRINT#2,EDITOR#2,PARENT#2,CONTEXT#2,WORKER#2>with(WORKER#2,PARENT#2) is not applicable | |
| (inferred type does not conform to lower bound(s) | |
| inferred: WORKER#3 | |
| lower bound(s): InstallationWorker) |
| #! /bin/sh | |
| # TODO: parse & pass-through sudo options from $@ | |
| sudo_options="-E" | |
| scls=$X_SCLS | |
| #available_scls="`scl --list | tr '\n' ' ' | sed 's/ $//'`" | |
| for arg in "$@" | |
| do | |
| case "$arg" in | |
| *\'*) |
| @Describe("JBoss Home, you can specify relative path to Spacelift Workspace or absolute path") | |
| DeferredValue<File> jbossHome = DeferredValue.of(File.class).from("JBOSS_HOME") |
| spacelift { | |
| logging {[ | |
| console: info, | |
| file: fine, | |
| additional: new MyExtraLogger() | |
| ]} | |
| properties { | |
| jbossHome(defaultsTo: new File(project.workspace, "jboss-wildfly-8.1"), | |
| // in future version enable ObservableMap behavior and add listener bound to the property | |
| listener: {evt -> println evt.propertyName, evt.newValue, evt.oldValue}) |
| def jbossInstallationTemplate = { File ups, File jbossHome, Map params -> | |
| assert ups | |
| assert jbossHome | |
| assert params | |
| ... | |
| } | |
| def jbossInstallation = null; |
| == Title: Upstream and downstream testing challenges | |
| === Abstract | |
| There is a plenty of testing efforts ongoing in both upstream and downstream communities. Every team does it differently. Every project/product is somewhat unique. | |
| This slot provides a unique opportunity to discuss test and test framework development processes, opensourcing policies, lessons learned and challenges your team has gone through when trying to keep pace with testing of ever evolving upstream code and very conservative downstream code at the same time. | |
| Come and share your experience or just get inspired by the experience of others. |
Karel Piwko is a Senior Software Engineer at Red Hat, Inc., currently leading JBoss Mobile related testing efforts. He is actively participating in improving test automation tools for both mobile front ends and mobile related back ends.
Karel is involved in Arquillian testing platform, leading a few testing extensions there. He is also improving usage of Maven and Gradle from Java code via ShrinkWrap Resolver project. He focuses on system and integration testing including complex architecture scenarios without mocking, currently being a Groovy/Gradle enthusiast. Before joining mobile testing universe, he was working on Java EE application testing.