In a lean/agile environment, you avoid Big Design Up Front (BDUF) in favor of getting something small and simple to work first, then iterating as you learn more.
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).
Microstrategy has a new R Integration Pack which allows you to use R scripts to calculate new Microstrategy metrics. Here are some tips on how to use it. I also have a sample R script that will call the
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:
After using SSAS cubes on a project recently, I’m not sure I would do it again. Some of my observations:
Parts of Spark jobs that do pure-functional transformations on dataframes or RDDs – independent of I/O – are ideal candidates for unit testing.
Previously I complained about React and JSX readability. I was unhappy with something like this:
One of the activities at my daughter’s 9th birthday party was decoding secret messages (e.g., “be sure to drink your Ovaltine”) using this decoder ring my wife found on Pinterest.
I was looking at some code the other day to convert a comma-delimited string like
"1,2,3,4" into a list of integers.
.NET Core along with ASP.NET Core, looks like a promising alternative to build ASP.NET web applications, without a dependency on Windows and Visual Studio. This squarely addresses the biggest downsides of ASP.NET – namely, that it only runs on Windows, and you can’t just fire up an application from a command line like you can with Node/Ruby/etc.
I put together this app to try out a few things together:
(I’m writing about NHibernate, but this applies equally to JPA in the Java universe. I’m not sure about Entity Framework.)
One argument I’ve heard for building microservices from the beginning is that, teams often lack discipline to enforce modularity and separation of concerns. A monolith usually turns into a “big ball of mud,” which is a problem. Starting with microservices forces teams to think about their module boundaries up front.
A few years back I wrote about how I was starting to like C# better than Java.
I like Uncle Bob’s post on Screaming Architecture.