| <!-- | |
| This example requires some changes to your config: | |
| ``` | |
| // tailwind.config.js | |
| module.exports = { | |
| // ... | |
| plugins: [ | |
| // ... | |
| require('@tailwindcss/forms'), |
| <button type="button" class="rounded-full bg-indigo-600 p-1 text-white shadow-sm hover:bg-indigo-500 focus-visible:outline focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-indigo-600"> | |
| <svg class="h-5 w-5" viewBox="0 0 20 20" fill="currentColor" aria-hidden="true" data-slot="icon"> | |
| <path d="M10.75 4.75a.75.75 0 0 0-1.5 0v4.5h-4.5a.75.75 0 0 0 0 1.5h4.5v4.5a.75.75 0 0 0 1.5 0v-4.5h4.5a.75.75 0 0 0 0-1.5h-4.5v-4.5Z" /> | |
| </svg> | |
| </button> | |
| <button type="button" class="rounded-full bg-indigo-600 p-1.5 text-white shadow-sm hover:bg-indigo-500 focus-visible:outline focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-indigo-600"> | |
| <svg class="h-5 w-5" viewBox="0 0 20 20" fill="currentColor" aria-hidden="true" data-slot="icon"> | |
| <path d="M10.75 4.75a.75.75 0 0 0-1.5 0v4.5h-4.5a.75.75 0 0 0 0 1.5h4.5v4.5a.75.75 0 0 0 1.5 0v-4.5h4.5a.75.75 0 0 0 0-1.5h-4.5v-4.5Z" /> | |
| </svg> | |
| </button> |
| def sane_badge(color:, &block) | |
| color = color | |
| color_classes = case color | |
| when :red, :green, :blue | |
| "border-#{color}-border text-#{color}-text" | |
| end | |
| default_classes = "whatever" |
Effort: 1 order per month per Buyer Total effort for all Buyers: 10 orders Visits: 2-10 - create order, see offer, react
Effort: 10 offers per month per Seller Visits: 30+ , untill order is found, then to create offer, then to check for result, then wait for next offer
Problem: Traditional systems built on RDBMS suffer from loss of (potentially valuable) information. Information system, is a system which recieves Inputs, Transforms them somehow, and then stores derived State. It is important to highlight, that while system evolves schema of Inputs may change, code of Transformers may change, and State may change.
Solutions:
| Design Systems as single source of truth: common failures. | |
| TLDR: | |
| Names should be practically unambiguous. | |
| Namespacing should be based on rules - you may change them, but have them explicitly stated, | |
| so if you reshape your namespaces - only reason is that you gained new understanding of priorities. | |
| Source code repositories should have one 'main' branch for reason. You've been warned. | |
| Dependency structure should be discoverable. Dependency roots are more important than edge. |
| def simulate_a_b | |
| sizes = [1_000, 10_000, 100_000] | |
| funded_distribution = [500, 500, 500, 500, 600, 700, 800, 1000, 1500, 2000] | |
| convertion_rate = 0.03 | |
| results = {} | |
| results = { | |
| a: {visits: 0, funded: 0, converted: 0}, | |
| b: {visits: 0, funded: 0, converted: 0}, | |
| } |