text: In early 2006, I started Grave Error, a blog where I posted all sorts of digressions from my daily life in Spain (as an American living Madrid) to politics, jazz, and literature. In recent years, I have increasingly had less time to dedicate to Grave Error, especially since becoming a husband and father. Nonetheless, I hope to jump start Grave Error — with its new look and feel (and hopefully migrating the old blog here).
  
  Expectations are assertions for data. They are the workhorse abstraction in Great Expectations, covering all kinds of common data issues.
  Since docs are rendered from tests, and tests are run against new data as it arrives, your documentation is guaranteed to never go stale. Additional renderers allow Great Expectations to generate other type of "documentation", including slack notifications, data dictionaries, customized notebooks, etc.
  Wouldn't it be great if your tests could write themselves? Run your data through one of Great Expectations' data profilers and it will automatically generate Expectations and data documentation. Profiling provides the double benefit of helping you explore data faster, and capturing knowledge for future documentation and testing.
  Automated profiling doesn't replace domain expertise—you will almost certainly tune and augment your auto-generated Expectations over time—but it's a great way to jump start the process of capturing and sharing domain knowledge across your team.
  Expectations are a great start, but it takes more to get to production-ready data validation. Where are Expectations stored? How do they get updated? How do you securely connect to production data systems? How do you notify team members and triage when data validation fails?
  Great Expectations supports all of these use cases out of the box. Instead of building these components for yourself over weeks or months, you will be able to add production-ready validation to your pipeline in a day. This “Expectations on rails” framework plays nice with other data engineering tools, respects your existing name spaces, and is designed for extensibility.
  Every component of the framework is designed to be extensible: Expectations, storage, profilers, renderers for documentation, actions taken after validation, etc. This design choice gives a lot of creative freedom to developers working with Great Expectations.
  We recommend deploying within a virtual environment. If you’re not familiar with pip, virtual environments, notebooks, or git, you may want to check out the Supporting Resources section to set up your environment.
  We keep our GitHub issues update with what we are working on while addressing our communities issues.
  A place where you can find and share advice on GE implementing and keep up on some of the more cutting edge developments on Great Expectations
  Please reach out on slack with questions. If you're feeling really motivated, you can help us make our integrations better by contributing!
  
  I’m indulging myself during this tedious lockdown by re-reading Arnold Bennett’s Imperial Palace (1930). At the moment I’m wondering about something that occurs in the episode where dynamic Gracie Savott parks her car outside Smithfield market, and asks a policman to keep an eye on it.
  On leaving the market, ‘she resumed her dark cloak, tipped the policeman before Evelyn could do so, and slowly climbed into the car’.
  I’ve come across the custom of tipping policeman before in novels of the twenties, especially detective novels.
  These days, though, I’ve feeling that I’d be regarded with some suspicion if I offered our local community police officer a fiver for services rendered. So – does anyone know when the custom of tipping policemen ended? My guess would be somewhere about the Second World War. Am I right?
  This entry was written by George Simmers and posted on May 11, 2020 at 9:57 am and filed under attitudes, History, novels with tags Arnold Bennett, Imperial Palace, policemen, tipping. Bookmark the permalink. Follow any comments here with the RSS feed for this post.	Post a comment or leave a trackback: Trackback URL.