Skip to the content.

Multiple teams, one codebase

When multiple (small, agile) teams are working on the same codebase, it can be tempting to create a branch for each team so they can work in isolation without impacting each other. Don’t do it. Teams working in isolated branches may appear to make faster progress, but it is an illusion–in reality, work in an isolated branch can’t be delivered without getting through some big scary merge in the future. The hard work of integration is just being kicked down the road and gets harder the longer it waits. There is no substitute for coordination and communication.

Read More

SSIS data flow vs. insert-select

To transform data within a single SQL Server, with source and target data in the same database, it is probably faster to use an INSERT statement than a SSIS data flow task.

Read More

Microstrategy Visual Insights live connection issues

Microstrategy’s data import feature is promising, because it can shorten the time to insight. Instead of architecting a project schema up front (attributes, facts, metrics), you can import tables directly into a dataset (Intelligent Cube).

Read More

Aaron Burr quotes on the lean startup

My kids have been listening to the “Hamilton” soundtrack a lot. When I was Googling for something to answer a question for them, I came across this quote attributed to Aaron Burr:

Read More