In business, master data management (MDM) is a method used to define and manage the critical data of an organization to provide, with data integration, a single point of reference.[1] The data that is mastered may include reference data - the set of permissible values, and the analytical data that supports decision making.[2]
In computing, a master data management tool can be used to support master data management by removing duplicates, standardizing data (mass maintaining),[3] and incorporating rules to eliminate incorrect data from entering the system in order to create an authoritative source of master data. Master data are the products, accounts and parties for which the business transactions are completed. The root cause problem stems from business unit and product line segmentation, in which the same customer will be serviced by different product lines, with redundant data being entered about the customer (a.k.a. party in the role of customer) and account in order to proc
| Things are packages of emphasis. Some things are emphasized in a product. Some things are not done as well in a product. Some things are chosen not to be done at all in a product. Different people make different choices, and if the market tells us we’re making the wrong choices, we listen to the market. We’re just people running this company. We’re trying to make great products for people, and so, at least we have the courage of our convictions to say, “We don’t think this is part of what makes a great product. We’re going to leave it out.” | |
| Some people are not going to like that. They’re going to call us names. It’s not going to be a certain company’s vested interest that we do that, but we’re going to take the heat, because we want to make the best product in the world for customers. We’re going to instead focus our energy on these technologies, which we think are in their ascendency, and we think are going to be the right technologies for customers. | |
| And you know what? They’re paying us to make those cho |
| #!/bin/bash | |
| # Script to use custom ssh keys for various git repositories | |
| # Run without arguments to get usage info. | |
| # | |
| # How it works: | |
| # When used with SSH, git sends the path to the repository in the SSH command. | |
| # @see: https://github.com/git/git/blob/e870325/connect.c#L1268 | |
| # We extract this info and search for a key with the name. | |
| # Based on the source, this seems to be used format since v2.0 at least. | |
| # @see: https://github.com/git/git/commit/a2036d7 |
| name: CI | |
| on: [push] | |
| jobs: | |
| test: | |
| runs-on: ubuntu-latest | |
| services: |
| # Run the test suite if a source or test file changes | |
| **/tests/test_*.py { | |
| # prep +onchange: pytest @dirmods | |
| prep +onchange: pytest @mods | |
| } | |
| requirements.txt { | |
| # prep +onchange: pytest @dirmods | |
| prep +onchange: " | |
| pip install -U -r requirements.txt |
2019 update: this essay has been updated on my personal site, together with a followup on how to get started
2020 update: I'm now writing a book with updated versions of all these essays and 35 other chapters!!!!
If there's a golden rule, it's this one, so I put it first. All the other rules are more or less elaborations of this rule #1.
You already know that you will never be done learning. But most people "learn in private", and lurk. They consume content without creating any themselves. Again, that's fine, but we're here to talk about being in the top quintile. What you do here is to have a habit of creating learning exhaust. Write blogs and tutorials and cheatsheets. Speak at meetups and conferences. Ask and answer things on Stackoverflow or Reddit. (Avoid the walled gardens like Slack and Discourse, they're not public). Make Youtube videos
| # This setup took me a few hours to come up with; codecov docs turned out to be useless in the end. | |
| # With this gist I hope to be the last one to have ever faced it again :) | |
| sudo: required | |
| services: | |
| - docker | |
| before_install: | |
| - docker version |
| # NOTE: Be sure to set the API key further down in the code! | |
| require "net/http" | |
| require "uri" | |
| require "json" | |
| class WIP | |
| def initialize(api_key:) | |
| @api_key = api_key | |
| end |