TODO: Write a project description
TODO: Describe the installation process
matthewmccullough
/ continuous-delivery.md
Created
February 27, 2014 22:42
| layout | title | description | path |
|---|---|---|---|
bare |
Continuous Delivery |
The next step in the evolution of software development is making ever smaller changes and continually deploying to production. |
technology/_posts/2001-01-01-lesson-continuous-delivery.md |
Continuous delivery is the current buzz, but let's take a few minutes to demystify it. 1. Does it work? 2. How would you go about getting towards that mode of operation? 3. Why would you want to have continuous delivery? 4. What tools facilitate this? You'll leave a transformed developer. The idea of releases being non-stressful and able to be merged in on Friday at 4pm is attractive to the majority of us who have suffered at the hands of the "awful rollback" and the "long weekend." These travails are partially the result of being on the opposite end of the spectrum from continuous delivery. Come with an open mind to branching strategies, feature toggles, and Readme-driven development.
marcuslilja
/ ubuntu-server-setup-16.04.md
Last active
January 30, 2020 23:28
Server setup for Ubuntu 16.04 on Digital Ocean
PurpleBooth
/ README-Template.md
Last active
November 29, 2024 01:15
A template to make good README.md
- Consider Your Options - covers stock grants, nonqualified options, incentive stock options and employee stock purchase plans in an easy to understand way.
- Customer Success: How Innovative Companies Are Reducing Churn and Growing Recurring Revenue
- Creativity, Inc. by Ed Catmull - Lessons learned at Pixar while trying grow and sustain an incredible and creative culture
slikts
/ advanced-memo.md
Last active
September 12, 2024 18:33
Advanced memoization and effects in React
Memoization is a somewhat fraught topic in the React world, meaning that it's easy to go wrong with it, for example, by [making memo() do nothing][memo-pitfall] by passing in children to a component. The general advice is to avoid memoization until the profiler tells you to optimize, but not all use cases are general, and even in the general use case you can find tricky nuances.
Discussing this topic requires some groundwork about the technical terms, and I'm placing these in once place so that it's easy to skim and skip over:
- Memoization means caching the output based on the input; in the case of functions, it means caching the return value based on the arguments.
- Values and references are unfortunately overloaded terms that can refer to the low-level implementation details of assignments in a language like C++, for example, or to memory