heynickc
Location: MD, USA
Remote: Yes
Technologies: C#, F#, .NET Core, ASP.NET MVC, ASP.NET Core, SQL Server, TeamCity, Akka.NET, Domain-Driven Design, Event Sourcing, CQRS
Websites: https://buildplease.com, http://dddweekly.com
Contact page: https://buildplease.com/pages/consulting/
Github: https://github.com/heynickc
Self-published books: "Intuitive Testing with Legacy Code" (https://buildplease.com/products/itmvc/), "Applying Domain-Driven Design with CQRS and Event Sourcing" (https://buildplease.com/products/fpc/)
Also:
Conference calls
Being treated like garbage (by incompetent people)
700 line loops
dbo.v_TheFirstTimeIMadeThisView followed by dbo.v_TheFirstTimeIMadeThisView_1 (referencing dbo.v_TheFirstTimeIMadeThisView)
I don't really have a set way I cut out the noise - but I definitely try to in as many ways as I can. It helps me to look at it as a fear of loss/fear of missing things and when I make note of that fear - I can ignore the noise more easily.
Side Projects: A blog where I tackle topics that junior/mid-level software engineers might like to learn more about.
In my experience, the most important part of doing network analysis is to have a "topology model" for your road network data. It contains the information necessary to model turns, drive-time, traffic signals, etc.
Anyway, I used to know the 1000 ft view of the math behind this stuff but not anymore. If, however, you're trying to build it into an application - there are solutions like pgRouting https://github.com/pgRouting/pgrouting which utilizes PostGIS (PostgreSQL), ESRI's Network Analyst ($$), and Google Maps Directions API. These all leverage some underlying topology data like Open Street Map to do routing and figure out the subsequent times/schedule to get from point to point to point...
Hope this helps!
Something that stood out to me was their discussion about "Big Data technologies" (Hadoop, HBase...) and how they "support" data mining techniques. So sometimes I wonder if big data technologies are more for the processing of the data, like the ETL needed for data warehouses - but since it's big, we need those special technologies to process it (and do additional data-sciencey things on it - like calculate a probability of churn, probability of loan default, etc). End results can still be those high-performance in-memory objects that we can slice and dice, just like our data warehouses, if that's how we need to see them.
This is all coming from no practical experience with Hadoop / Big Data, just research so hopefully someone clarifies :)
I know you said you're aware of Ralph Kimball, but the first ~100 pages are broken into 1) Defining the Business Requirements and 2) Designing the Business Process Dimensional Model. It's really helped me wrap my head around the original design of the Facts and Dimensions as they relate to the business.