Putting your work on GitHub probably is the best decision you can make to build your portfolio.
But what makes a good project stand out?
A good README.
Here are 4 ways to make a good README: ๐งต
guardrails: small warehouses per workload, 60s auto-suspend, query tags for cost. roles per layer + masking policies for PII. simple rules, big savings.
@via_marketing_ yep, most teams want fewer vendors. but they also want an exit door. my rule: portability first (sql, dbt core, warehouse-native). convenience second.
Dumping your data into S3 doesnโt make it a data lake.
A real data lake has:
- โ A catalog (what's in there)
- โ Permissions (who can access what)
- โ Structure (partitioning, schema)
- โ Query tools (Athena, Redshift, etc)
Without these you just have expensive storage.
Pretty dashboards are great โ they should be visually appealing.
But if they arenโt helping your team make better decisions, whatโs the point?
A good dashboard doesnโt just look good.
It drives action.
It answers real business questions.
Are your dashboards helping your team make better decisions?
@ibn_wittig You need to define learn. Learning syntax is one thing, concepts are another. When you get the concepts down (when you would need a join, what type of data structure is needed) to tackle the problem you face takes a much longer time than just syntax.
Want to break into Data Analytics?
Hereโs your ultimate guide to learning the skills, building a portfolio, and landing your first job as a Data Analyst. ๐งต๐
Upskill with Cloud & Advanced Tools:
As you grow, learn tools that can give you an edge:
โขCloud Platforms: AWS, GCP, or Azure.
โขData Warehousing: Snowflake, Redshift, BigQuery.
โขAdvanced SQL: Learn window functions, CTEs, and joins.