80/15/5. Spend 80% of your time on low-risk/reasonable-payoff work. Spend 15% of your time on related high-risk/high-payoff work. Spend 5% of your time on things that tickle you, regardless of payoff. Teach the next generation to do your 80% job. By the time someone is ready to take over, one of your 15% experiments (or, less frequently, one of your 5% experiments) will have paid off and will become your new 80%. Repeat.

Start projects by measuring the current state of the world

Arrows can be naturally combined. If the codomain of one map is the same as the domain of another then we can create a third map.

To me this gets to the heart of the teaching of mathematics. There are (at least) two distinct skills: The mechanical system of converting one thing to another using an array of symbols The translation system mapping those moves onto the world. We can emphasise the mechanical (the approach of most school systems) or we can emphasise the translation (the approach of Conrad Wolfram and others who argue that computers should do the calculation).

There are other important costs you might have heard of. One is sunk cost, which really means money that was spent in the past. Sunk costs are generally ignored in most financial analyses, even if that's pretty painful.

By definition, accounting is a set of rules that govern how a business records transactions

You’re walking to work and you see a burning mansion. You’ve been in that mansion and know that there’s a Picasso worth $100 million. (Quick math: 100,000 lives saved.) You’re about to run into the mansion to save the Picasso…But right next to you, there’s a lake. And in that lake, there’s a drowning child.

Second, the range of the function must be efficiently computable, and it must be efficiently computable by you.

And in business novices make a product nobody wants.

The seeds had a typical shelf life of about a year. While this limitation might have had some benefits (preventing inflation and encouraging spending, for example)

Cutting Contexts by Architectural Need Bounded Contexts needn't be organized solely by the functional area of an application. They're very useful in dividing a system to achieve desired architectural examples. The classic example of this approach is an application that has both a robust transactional footprint and a portfolio of reports. It's often desirable in such circumstances (which might occur pretty often) to break out the reporting database from the transactional database. You want the freedom to pursue the right degree of normalization for developing reliable reports, and you want to use an Object-Relational Mapper so that you can keep coding transactional business logic in the object-oriented paradigm. You can use a technology such as Microsoft Message Queue (MSMQ) to publish data updates coming from the model and incorporate them into data warehouses optimized for reporting and analysis purposes. This might come as a shock to some, but it's possible for database administrators and developers to get along. Bounded Contexts give you a glimpse of this promised land. If you're interested in architectural Bounded Contexts, I highly recommend keeping tabs on Greg Young's blog. He's quite experienced with and articulate about this approach and produces a fair amount of content on the subject.

These time windows are not usually enforced by the system(s) but instead are often a convention, documented elsewhere.

A common approach to this problem is to freeze source data formats or to add a change control process on all source data

requirements for a replacement system to support import and export of data can often have a root cause in this kind of workaround

These larger projects then become magnets for all the small changes that weren't previously justifiable

Musk doesn’t believe in induced demand; he recently called it “one of the single dumbest notions I’ve ever heard in my entire life.”

After you’ve authenticated once, creating synced databases is as simple as pasting a link.

But most of this research failed to take into consideration the associations between names on the one hand and race and social class on the other.

Once a name hits a critical mass among females, its use for the male population declines precipitously. And feminine names never become masculinized.

"cocktail party" effect

We can do that, using the @typedef JSDoc:

Workable, but less than perfect.

In actuality, TypeScript is not one language. It’s an infinity of languages, each one slightly different, and each one “generated” by a specific configuration file.

everybody should move to dynamic typing

my code was “clean”

This was because dynamic typing doesn’t give the safety net that static typing does. So you write more tests. Which is a good thing.

because you’re dealing with data, and not trying to abstract it away, then the design becomes simpler. Much easier to reason and deal with.

but that we’re looking to science for answers that ultimately require human moral intervention

There is such a thing as a price umbrella, but there's also one for customer happiness.

ex nihilo

Web Launch Checklist

According to a report jointly released by Indian Cellular and Electronics Association and consulting firm KPMG,

“ContributionofSmartphonestoDigitalGovernanceinIndia