@itsjoenaso Profile picture

Joe Naso

@itsjoenaso

I help companies fix their data problems. Writing stuff here: https://t.co/vmm07g0Jx4

Joined September 2011
Similar User
Lauren Balik photo

@laurenbalik

Rahul Jain photo

@rahulj51

Vivek S P photo

@viveksp

Kev S photo

@Sparkey234

Ahmad Abdalla 🇨🇦 photo

@axabdalla

Kevin Melgarejo photo

@KevinMelgarejo

Pinned

Trimmed a client’s Snowflake spend from ~$180/day to ~$50/day just by consolidating warehouses. >70% cost reduction. This takes only minutes to do and has immediate results. Low hanging fruit abounds.


ORMs are **fine**. But if you rely on your client to generate timestamps like created_at or updated_at, you're going to cause headaches later on. Push the work the DB.


Forced to work on multiple things at once/ context switch and forget which branch has your most recent changes? This is a lifesaver git log —oneline —branches — your_file.py


Does anyone have a good take on the root cause of complexity in data engineering? or even "perceived" complexity?


Gotta love when a new Python notebook demo shows each new cell getting added to the top and the imports get pushed further and further down the screen. Gave me flashbacks to a past job debugging model building Jupyter notebooks written by Stats PhDs


Lambdas are cool but no one ever mentions that you'll spend more time waiting for CloudFormation updates than writing code. What are the best ways to speed up Serverless deployments?


You’re in for a smoother ride if your analysts are contributing to your data model, not just consumers of it


When all you have is a hammer, everything is a nail. What’s the next wave of “hammers” in data tooling? At one point everyone wanted to solve their problems with Spark. Then for a while it swung over to dbt. Is there a post-dbt hammer?


Is it worth it (possible, even) to run Airflow locally with the Astro CLI if you're not deploying Airflow with Astronomer? Or should I just stick with setting up docker/ docker-compose and skip out on Astro?


Optimal complexity in data systems is under acknowledged. Some level of complexity is necessary and not a bad thing. But not all complexity is justified or needed


Vertical SaaS is cool, but when it comes to those in the data ecosystem it always seems they are BI tools with an integration layer. Nothing wrong with that, just not much differentiation other than industry. What are some unique vertical SaaS products in the data space?


TIL this is valid postgres syntax? I feel weird SELECT * FROM A JOIN B JOIN C ON C.id = A.c_id ON B.id = A.b_id


United States Trends
Loading...

Something went wrong.


Something went wrong.