Useful slang to communicate with data scientists

  • Definition: A precise and unambiguous description of the meaning of a mathematical term. (Everybody knows that…)
  • Claim:Assertion that is then proved.  It is often used like an informal lemma. (I say…)
  • Axiom/Postulate: A statement that is assumed to be true without proof. (Believe me when I say…)
  • Lemma: A lemma is a useful observation that serves as a stepping stone to understand theorems. (I see…)
  • Conjecture: A conjecture is a guess mostly based on observations. (I guess…)
  • Hypothesis: A hypothesis is a conjecture with lots of partial evidences and significant consequences. (I believe…)
  • Theorem: A theorem is a single essential contribution to a theory (I know…)
  • Corollary: A result in which the (usually short) proof relies heavily on a given (ergo…)
  • Theory: This is how it works, based on this theorems (It is…)
  • Paradox: A statement that can be shown, using a given set of axioms and definitions, to be both true and false (WTF!)
  • […]
  • Grand Unified Theory of Everything: The ÜBER THEORY. (Oh my God… it is full of stars. Look…a Higgs Boson!)

PowerShell new features.

PowerShell 5.0 (Windows Management Framework 5.0)

  • By default in Windows 10 & Windows Server 2016 Technical Preview.
  • Remote Script Debugging in ISE 🙂
  • Transcription works in ISE by default
  • .NET enumerations.
  • Improved DSC.

PowerShell 4.0

  • By default in Windows 8.1 & Windows Server 2012 R2
  • DSC: Desired State Configuration
  • Remote Script Debugging in console (no ISE)
  • Improved Invoke-RestMethod and Invoke-WebRequest to specify headers.

PowerShell 3.0

  • By default in Windows 8 & Windows Server 2012
  • Improved ISE: IntelliSense
  • Improved remote PowerShell ( New-PSSession)
  • Module Auto-Load
  • Invoke-RestMethod and Invoke-WebRequest
  • Ordered Hashtables
  • Scheduled jobs

The James White Manifesto

Taken from websages blog.

    == Rules ==
On Infrastructure
– There is one system, not a collection of systems.
– The desired state of the system should be a known quantity.
– The “known quantity” must be machine parseable.
– The actual state of the system must self-correct to the desired state.
– The only authoritative source for the actual state of the system is the system.
– The entire system must be deployable using source media and text files.

On Buying Software
– Keep the components in the infrastructure simple so it will be better understood.
– All products must authenticate and authorize from external, configurable sources.
– Use small tools that interoperate well, not one “do everything poorly” product.
– Do not implement any product that no one in your organization has administered.
– “Administered” does not mean saw it in a rigged demo, online or otherwise.
– If you must deploy the product, hire someone who has implemented it before to do so.

On Automation
– Do not author any code you would not buy.
– Do not implement any product that does not provide an API.
– The provided API must have all functionality that the application provides.
– The provided API must be tailored to more than one language and platform.
– Source code counts as an API, and may be restricted to one language or platform.
– The API must include functional examples and not requre someone to be an expert on the product to use.
– Do not use any product with configurations that are not machine parseable and machine writeable.
– All data stored in the product must be machine readable and writeable by applications other than the product itself.
– Writing hacks around the deficiencies in a product should be less work than writing the product’s functionality.

In general
– Keep the disparity in your architecture to an absolute minimum.
– Use Set Theory to accomplish this.
– Do not improve manual processes if you can automate them instead.
– Do not buy software that requires bare-metal.
– Manual data transfers and datastores maintained manually are to be avoided.

Useful MarkLogic links

Useful MarkLogic links: