Erik on Software

Sign in Subscribe

Topic

community

A collection of 42 issues

Community Comment: Part 30 - With respect to Azure, Databricks Unity Catalog & Microsoft Purview is not an either-or proposition

* Databricks Unity Catalog & Microsoft Purview * Not an either-or proposition for Azure * Likely need to integrate these products * Integration dependant on several factors The comments I provided in reaction to a community discussion thread. Cloud Solutions Architect at Consulting Firm: Read my latest post if you want to know what

Community Comment: Part 29 - Usage of normalized versus denormalized data storage is dependent on usage patterns

* Normalized versus denormalized data * Data storage dependent on usage patterns * Denormalized data makes reads efficient * Normalized data makes writes efficient The comments I provided in reaction to a community discussion thread. CEO at Business Intelligence Product Firm: After 100s of conversations with analytics engineers, I'm convinced the way

Community Comment: Part 28 - Technical debt is actually a subset of organizational debt

* Not all technical debt is the same * Discussion with purported CTOs * Technical debt is subset of organizational debt * Business + technology = "our business" The comments I provided in reaction to a community discussion thread. Fractional CTO and "Engineering Management Expert": "Technical debt? Is that a joke?

Community Comment: Part 27 - Assessment is needed when deciding between transactional and analytical modeling

* Transactional versus analytical modeling * Discussion with purported staff data engineer * Making broad generalizations doesn't help * Quoting $ savings in vacuum not advised The comments I provided in reaction to a community discussion thread. Owner of Data Engineering Training Firm and former Staff Data Engineer at Airbnb: If you model

Community Comment: Part 26 - With respect to data normalization, performance is key

* Normalized versus denormalized data * Discussion with purported training firm CEO * Performance is important consideration * More factors involved than just record count The comments I provided in reaction to a community discussion thread. Founder & CEO of "Big Data" Training Firm: Normalization vs Denormalization Normalization is a process of

Community Comment: Part 25 - When considering the choice between waterfall and agile methodologies, keep product life cycle in mind

* Waterfall versus various agile claims * Software engineering methodologies * Poor methodologies assume product lifespan * Lifespan may be too short to see success The comments I provided in reaction to a community discussion thread. Owner at Software Delivery Firm: What does this say to you? #agile #waterfall #softwaredevelopment #iterativedevelopment #incrementaldevelopment Gfesser: The

Community Post: Part 2 - Without "conflict", there's no "colleague"

* "Colleague", "co-worker" & "teammate" * Surprising word origin of "colleague" * Root word means "to arrive together" * Without "conflict", there's no "colleague" A well-received community post I recently made: https://www.linkedin.com/posts/erikgfesser_career-wordorigin-respect-activity-6998107676408770560-dHt_

Community Comment: Part 24 - Self-service data product use cases exist, with caveats

* Self-service data product use cases exist, with caveats * Users need to know what they're doing * Stakeholders need to be aware of benefits & drawbacks * Some commercial products (e.g. Power BI) introduce unique risks The comments I provided in reaction to a community discussion thread. Owner & Data

Community Comment: Part 23 - Architecture diagrams can often mislead

* Architecture diagrams can often mislead * Databricks isn't a storage solution * Databricks is a Hadoop successor * Both ETL and ELT involve input & ouput The comments I provided in reaction to a community discussion thread. Product Manager at Data Modeling Product Firm: It's interesting how data storage

Community Comment: Part 22 - The phrase "it depends" is still relevant!

* The phrase "it depends" still relevant * Decisional factors need to be accounted * Never bow to unjustified pressure * Your clients & customers will thank you The comments I provided in reaction to a community discussion thread. CEO at Consulting Firm: Software meetings best practices: ❌ Never say: Never. ✅ Always say: