PatternAI is an automated machine learning platform that reveals critical patterns in data for narrow business problems.
We are looking for a savvy Data Engineer to join our growing team of data experts. The hire will be responsible for expanding and optimizing our data pipeline architecture, as well as optimizing data flow and collection for cross functional teams.
Responsibilities:
- Build and deploy the data pipelines that power PatternAI’s machine learning platform.
- Develop warehouse architectures that integrate data from diverse sources.
- Design analytics solutions for both product development and internal collaborators.
Google has handled themselves better than the content providers in past disputes, and the providers typically fold. I think Google has garnered goodwill by proactively reducing their prices etc.
AIUI, yes, it has been found that, e.g. there are games where two players who can’t communicate but who do have a pair of entangled qubits and can each make a measurement, would have a strategy which is better for both players than if they didn’t have this resource.
(where the games in the version where they don’t have the resource of the entangled pair of qubits, are fairly simple games where each player receives some information and then has a choice between two options)
This is the classic case of development velocity pitted against operational stability. Entirely different incentives, and when vested into the same role that role is bound to prioritize one incentive over the other. For this reason I think they must be separated at least by body if not by team. They certainly need to separated by different managers.
I tend to think QA is perhaps well situated alongside Ops("DevOps"), and very close to Product + Design.
We were a small and good team developping hardware/software combos.
We ruined a demo to a client by promising some hard to do feature, and during the demo, the said feature had not been well tested for a particular environment.
The debriefing of that failure was memorable. The big boss was yelling at us, saying we should do better, work harder, longer, whatever was required to succeed.
When this calmed down, I only asked one question: when going back to my desk, should I work on this new feature promised to some other customer, or test this old one for any combination of inputs/environments?
The response was: "You do both"
I insisted that I will do both, but which one first?
He responded with some blabla I do not remember, but no response to my question.
To any manager which cannot decide between feature and stability:
If you cannot prioritize, the dev will do it, with whatever information/incentive they have. You may not be happy of the result.
Didn’t Corea and Fleck also do something along those lines with a third person? I remember the name “Trio”. Can’t remember who the third was though.. maybe Jean Luc Ponty or Stanley Clark?