We tailored the data we request to exactly what’s needed by the UI. This saves both on network overhead and eliminates unnecessary fetches on the server-side since additional fields often require additional calls to backend services.
3½ simple rules to follow:
1. Numerical data is right-aligned
2. Textual data is left-aligned
3. Headers are aligned with their data
3½. Don’t use center alignment.
One easy way to keep your tables properly aligned is to keep the same number of significant figures — usually the number of digits after the decimal — consistent within each column. Significant figures is a whole rabbit hole of a topic, so I’ll keep my advice here brief: the fewer sig figs you can get by with, the better.
The repository setup that we use and that works well with this branching model, is that with a central “truth” repo. Note that this repo is only considered to be the central one (since Git is a DVCS, there is no such thing as a central repo at a technical level). We will refer to this repo as
origin, since this name is familiar to all Git users.
master, this is a new production release by definition. We tend to be very strict at this, so that theoretically, we could use a Git hook script to automatically build and roll-out our software to our production servers everytime there was a commit on
The different types of branches we may use are:
Each of these branches have a specific purpose and are bound to strict rules as to which branches may be their originating branch and which branches must be their merge targets.
--no-ffflag causes the merge to always create a new commit object, even if the merge could be performed with a fast-forward.
--no-ffflag was used.
developis when develop (almost) reflects the desired state of the new release. At least all features that are targeted for the release-to-be-built must be merged in to
developat this point in time. All features targeted at future releases may not—they must wait until after the release branch is branched off.
When the state of the release branch is ready to become a real release, some actions need to be carried out. First, the release branch is merged into
master (since every commit on
master is a new release by definition, remember). Next, that commit on
master must be tagged for easy future reference to this historical version. Finally, the changes made on the release branch need to be merged back into
develop, so that future releases also contain these bug fixes.
Hotfix branches are very much like release branches in that they are also meant to prepare for a new production release, albeit unplanned.
Trust me to pick the incorrect 'allowJS'. I make a great Gorilla tester :)
"Chef Spike Gjerde of Woodberry Kitchen in Baltimore preserves over 60,000 pounds of fruits and vegetables each year. Here's his guide to some the restaurant's most prized pantry staples."
Shared by Robert Sutor, 1 save total