Connect with a global community of data experts to share and learn about data products, platforms & all things modern data! Managed by team at @TheModernDataCo

Internet
Joined October 2023
Discover a curated selection of top-notch data resources on the MD101 community website's resources page. Modern data resources: moderndata101.com/resources Check the for this week's top picks!
1
2
2
44
🚀 Analytics Heroes to the Rescue! 🚀 Meet Ryan Brown, Sr. Data Engineer Architect at Trace3. With 5+ years of mastering ETL pipelines & data infrastructure, he’s dropping gems in our latest episode! 🎤💡 Stay tuned!
1
5
5
85
Modern Data 101 retweeted
What an Actual Lean AI Strategy Looks Like moderndata101.substack.com/p…
1
7
10
800
Modern Data 101 retweeted
Where Exactly Data Becomes Product: Illustrated Guide to Data Products in Action moderndata101.substack.com/p…
1
6
9
1,609
Data Modeling Gone Wrong: Why? Data modelling is crucial but can derail efforts if not done right, leading to suboptimal outcomes. Here's why.
1
3
3
41
Hey All 👋 Modern Data 101 newsletter is here. In this edition, we delve into the topic: Semantics and Data Product Enablement - A Practitioner's Secret Read the entire article here: moderndata101.substack.com/p…
1
3
3
41
Hey All 👋 Modern Data 101 newsletter is here. In this edition, we delve into the topic: Tearing Down the Monolith | The Rise of Microservices & Modular Architecture in Data Engineering. Read the entire article here: moderndata101.substack.com/p…
1
3
3
36
Modern Data 101 retweeted
Thus far, we’ve explored Product Thinking Basics, Dealing with Data, and Starting Strong in our module Bring Product Thinking to Data, clearing the fundamentals. It's time for the next exciting chapter! Read the full chapter here: moderndata101.com/product-th…
1
4
5
55
Hey All 👋 Modern Data 101 newsletter is here. In this edition, we delve into the topic: Usage Analytics Roadblocks: Solving with Model-First Data Products Read the entire article: moderndata101.substack.com/p…
1
4
4
47
Hey All 👋 Modern Data 101 newsletter is here. In this edition, we delve into the topic: Building Data Platforms: The Mistake Organisations Make Read the full article: moderndata101.substack.com/p…
1
3
3
27
Modern Data 101 retweeted
Decentralized Data Systems: Dream or Nightmare Is a fully decentralized data system the holy grail, or a recipe for disaster? Let's talk about feasibility v/s value... (Thread)
1
3
5
59
Modern Data 101 retweeted
Hey all👋 Modern Data 101 is here with it’s latest newsletter edition. In this issue, we delve into the topic: 𝐖𝐡𝐚𝐭'𝐬 "𝐌𝐨𝐝𝐞𝐫𝐧" 𝐢𝐧 𝐭𝐡𝐞 𝐌𝐨𝐝𝐞𝐫𝐧 𝐃𝐚𝐭𝐚 𝐒𝐭𝐚𝐜𝐤 Read the entire article here: moderndata101.substack.com/p…
1
3
4
29
Modern Data 101 retweeted
Great article on fundamentals and landscape of data engineering by my friends at Airbyte. I'm sharing my two cents as well 😉. airbyte.com/blog/data-engine…
2
13
70
5,372
Modern Data 101 retweeted
The Approach vs Technology Confusion: Where do Data Products Fit In? moderndata101.substack.com/p…
1
4
7
2,505
Modern Data 101 retweeted
The perfect, accurate and fully integrated data warehouse WILL NOT magically imbue you with actionable insights that will improve your business. The work in fact is just beginning. Say you get the perfect DWH. It's accurate and fully integrates all your data sources. Now what? How are you going to use it to improve your business? How are you going to find actionable insights? 7000 dashboards? Good luck with that! Not gonna happen. You need a systematic process to regularly review your business, find areas for improvement, develop solutions, implement them and then assess them. How come nobody in the data space talks about this?
9
4
2
64
9,408
Modern Data 101 retweeted
Top 4 reasons why data engineering is the best data profession: 1. highest pay for the least education Machine learning engineers and data scientists make 10-15% more but spent 30% more time in college. Data analysts make less than data engineers but require less schooling. 2. Data engineering projects are the least risky Machine learning projects fail an astounding EIGHTY percent of the time! When you build a data pipeline, you provide value regardless of how predictive the data ends up being. 3. LLMs will make data engineering grow dramatically How do you stop LLM hallucinations? Better data. How do you get that data? Better data engineering. 4. Data engineers have the most career options Branching from data engineering to software engineering isn’t too crazy. Or going to data science. Or going to machine learning. All of these are possible from the central location of data engineering. What do you think make data engineering a great career choice? #dataengineering
9
68
5
472
68,020
Modern Data 101 retweeted
Figuring out which data role you should become can be challenging! One dimension to look at is how much time you spend digging into the data vs how much time you spend building infrastructure! Obviously other factors like pay, responsibilities, and skill set are also factors. I’ve tried most of these roles throughout my career. Where should ML engineer fall on this continuum? #datascience #dataengineering
3
47
3
264
18,347
Modern Data 101 retweeted
As data teams continue adopting practices of software teams, many want to build something akin to developer tools instead of consumer products. But their typical stakeholders are unwilling to do as much as legwork as developers typically are, so this is a big source grief
3
5
2
85
9,032
Modern Data 101 retweeted
Ryan Peterman
@ryanlpeterman27 Dec 2023
If you want to become a better software engineer, read these famous posts from top companies (OpenAI, Airbnb, Stripe, Figma, Netflix, Meta) I spent hours curating top posts so you don't have to:
19
421
2
2,220
317,504
Modern Data 101 retweeted
A few strategies I implemented in my Data Engineering production systems to make it more "cost effective💰" and "less cool" 1. Maximize the use of caching wherever feasible. adding a cache layer between the client and data warehouse, resulting in over 60% cache hits weekly 2. Data warehouse(s) for poor. Established multiple cost-effective data warehouses using @duckdb endpoints for varied data sets, with a custom client handling request redirection. This approach led to significant cost savings. Users only hit the big DWH when duckdb endpoints have no references. 3. Avoided using big data technologies for non-big data tasks, reducing reliance on Spark and transitioning many processes to @DataPolars. 4. Reevaluated the need for orchestrators in data engineering jobs, discovering that 45% of them didn't require such complexity. Shifted to simpler cron jobs or Kubernetes executors for these tasks. 5. Don't code if LLM can generate it. Leveraged LLMs for generating various infrastructure templates, reducing coding requirements. Developed a finely-tuned(local) internal model to address frequently required tasks efficiently.
2
5
69
11,544