| Aspect | Open Source | Enterprise |
|---|---|---|
| Governance | Maintainers, community consensus, meritocracy-based influence | Empowered teams, lightweight oversight, guardrails over gates |
| Code Review | Public PRs, async reviews from global contributors, emphasis on transparency | Small PRs, fast feedback loops, pair/mob programming as alternative |
| Documentation | README-driven, contributor guides essential, public wikis | Living documentation, lightweight ADRs, docs as code |
| Branching Strategy | Fork-and-PR model, contributors work in personal forks | Trunk-based development, short-lived feature branches (< 1 day) |
| Communication | Public channels (GitHub issues, Discord, mailing lists) | Co-located teams (in space /and or time), minimal ceremony |
| Release Cadence | Varies widely, often semver-based, maintainer-driven | Continuous delivery, deploy on merge, feature flags for controlled rollout |
| Testing | CI on PRs, community-contributed |
| """ | |
| The most atomic way to train and run inference for a GPT in pure, dependency-free Python. | |
| This file is the complete algorithm. | |
| Everything else is just efficiency. | |
| @karpathy | |
| """ | |
| import os # os.path.exists | |
| import math # math.log, math.exp |
| # Add color coding based on Rails environment for safety | |
| if defined? Rails | |
| banner = if Rails.env.production? | |
| "\e[41;97;1m #{Rails.env} \e[0m " | |
| else | |
| "\e[42;97;1m #{Rails.env} \e[0m " | |
| end | |
| # Build a custom prompt |
Video: https://www.twitch.tv/videos/177667117
"In God we trust, all others bring data" W. Edwards Deming
Performance 👎
- Latency
- Throughput
- Latency ⍺ Concurrent Users
This guide has moved to a GitHub repository to enable collaboration and community input via pull-requests.
https://github.com/alexellis/k8s-on-raspbian
Alex
Optimistic Locking assumes that a database transaction conflict is very rare to happen. It uses a version number of the record to track the changes. It raise an error when other user tries to update the record while it is lock.
usage
Just add a lock_version column to the table you want to place the lock and Rails will automatically check this column before updating the record.
Pessimistic locking assumes that database transaction conflict is very likely to happen. It locks the record until the transaction is done. If the record is currently lock and the other user make a transaction, that second transaction will wait until the lock in first transaction is release.
usage
- Intro to algorithms by Cormen (aka CLRS book)
- Cracking the Coding Interview by McDowell
A complete list of RxJS 5 operators with easy to understand explanations and runnable examples.