blakeburch

20 ms·

1. 61.▲
   by blakeburch 4y ago

   This is the dirty secret of the industry. Companies hire data roles without knowing what to do with them. It's not that data work is worthless. It's that most people aren't very good at trying to figure out how to tie data to
2. 62.▲
   by blakeburch 4y ago

   I've been using it for the same thing. Super helpful for building sample datasets for a class I'm putting together.
3. 63.▲
   by blakeburch 4y ago

   I've thought on this for a bit and I think it's because the applicant tracking systems (ATS) (Greenhouse, Lever, Breezy, etc.) are built for the employer, not the applicant. This one-sided process is dehumanizing due to a lack of
4. 64.▲
   by blakeburch 4y ago

   Great post and really resonates with my experience. Good to have some confirmation that most organizations aren't using their large swaths of data. Although I don't think most organizations are blaming lack of actionable insights
5. 65.▲
   by blakeburch 4y ago

   The problem is that no tool alone can make data useful. It requires human ingenuity to come up with a theory, gather the required data, then test and verify the theory. We've gotten to a point where the first and last step get skipped.
6. 66.▲
   by blakeburch 4y ago

   That looks like a huge undertaking, but kudos for taking the time. I'll be following along. Totally agree that all data should be tied to the business value that it's driving. Unfortunately, I've found that many data teams fo
7. 67.▲
   by blakeburch 4y ago

   Shipyard ( https://www.shipyardapp.com ) | Integration Engineer (Python), Full Stack Engineer (Golang), Sales Development Lead, Growth Marketing Lead, Data Advocate | Full Time | REMOTE (US Only) Shipyard is a data orchestration p
8. 68.▲
   by blakeburch 4y ago

   Just wanted to say that I had no idea some of my favorite board games were designed by the same person... who also runs one of the publishing companies. Fun to learn and see the personal side of that story! I would love to know what the ear
9. 69.▲
   by blakeburch 4y ago

   This is fantastic and exactly where our team at Shipyard is expecting the data space to go. Context aware, AI driven. Great work on this! We were just talking last week about how we should create a feature to describe transformations you wa
10. 70.▲
    by blakeburch 4y ago

    I currently use a pi-hole. In a home of 2, we have 74k queries per day. That would effectively be a 4 day trial... so I can understand the other person's frustration.
11. 71.▲
    by blakeburch 4y ago

    Really appreciate this side-by-side guide. Didn't realize Polars could still be used with Python, and the speed improvements seem to be drastic. May need to scope if it's worth updating our open-source connectors.
12. 72.▲
    Transform Your Data Team into a Performance Powerhouse(bytesdataaction.substack.com)

    1 points by blakeburch 4y ago|0 comments
13. 73.▲
    by blakeburch 4y ago

    Cool interactions on mobile. But the poor vs rich game ended up with the poor person going up to $1000 and the rich person going down below $100. I recognize it's just chance... but it's funny that the results directly conflicted
14. 74.▲
    by blakeburch 4y ago

    Agreed that most of the solutions are still tough to implement in production. Plus, a lot don't have built-in logging, error-handling, notifications, version control, package management, etc. Those are the "gotchas" that you
15. 75.▲
    by blakeburch 4y ago

    One of the main benefits we hear from people using dbt Cloud is the IDE + scheduler. The price increase can make that main benefit a bit less palatable, especially when you can develop locally and orchestrators allow you to run more than ju
16. 76.▲
    by blakeburch 4y ago

    Love the idea! I really see the value in shifting the conversation towards the vendor themselves being responsible for pushing the data to customers and it makes a lot of sense to do it directly from DB -> DB. However, building a data pr
17. 77.▲
    by blakeburch 4y ago

    This is awesome to see! Our team at Shipyard [1] has been creating a lot of solution videos on YouTube recently to show teams how they can build A -> B solutions in a few minutes. We've been meaning to provide captions or transcript
18. 78.▲
    by blakeburch 4y ago

    I really agree with Shift 2 (“We unblock analysts” to “We enable everyone”). The problem is that Airflow (and most other OSS orchestrators) are overkill for the majority of data practitioners. They lock workflow development into Python, for
19. 79.▲
    by blakeburch 4y ago

    Shipyard ( https://www.shipyardapp.com ) | Solutions/Integration Engineer, Full Stack Engineer (Golang), Sales Development Lead, Growth Marketing Lead | Full Time | REMOTE (US Only) Shipyard is building modern data orchestrat
20. 80.▲
    by blakeburch 4y ago

    If I'm understanding your question correctly, it sounds like you're just generating cache tables for each variant of the root table with a different set of group bys (although I'm curious why you wouldn't want live views
21. 81.▲
    by blakeburch 4y ago

    Shipyard ( https://www.shipyardapp.com ) | Solutions/Integration Engineer, Full Stack Engineer (Golang), Sales Development Lead, Growth Marketing Lead | Full Time | REMOTE (US Only) Shipyard is building modern data orchestrat
22. 82.▲
    by blakeburch 4y ago

    Lots of the comments here seem to be commenting on their own experiences of complexity and frustration with Airflow, but I'd venture to say that's most data orchestration tools. In fact, that sort of feedback is so consistent that
23. 83.▲
    by blakeburch 4y ago

    I've had really great success from engaging with the Locally Optimistic Slack community. Also, Cristophe Blefari has an excellent data newsletter. https://www.blef.fr/ And Modern Data Stack has a newsletter, tool infor
24. 84.▲
    by blakeburch 4y ago

    Love your observation about tying the workflow to Airflow. One of my biggest annoyances in the orchestration space is that teams are mixing business logic with platform logic, while still touting "lack of vendor lock-in" because i
25. 85.▲
    by blakeburch 4y ago

    Shipyard ( https://www.shipyardapp.com ) | Solutions/Integration Engineer, Full Stack Engineer (Golang), Sales Development Lead, Growth Marketing Lead | Full Time | REMOTE (US Only) Shipyard is building modern data orchestrat
26. 86.▲
    by blakeburch 4y ago

    We do the same. It makes the puzzle have variety while still allowing healthy competition since we're always starting with the same word.
27. 87.▲
    by blakeburch 5y ago

    Shipyard ( https://www.shipyardapp.com ) | Solutions/Integration Engineer, Full Stack Engineer (Golang), Sales Development Lead, Growth Marketing Lead | Full Time | REMOTE (US Only) Shipyard is building modern data orchestrat
28. 88.▲
    by blakeburch 5y ago

    Shipyard ( https://www.shipyardapp.com ) | Data Community Advocate, Solutions/Integration Engineer, Full Stack Engineer (Golang), Sales Development Lead, QA Engineer | Full Time | REMOTE (US Only) Shipyard is building modern
29. 89.▲
    by blakeburch 5y ago

    Biggest factors in dbt adoption are: - Automatic DAG generation based on dbt-QL declared dependencies. - The structure of where (db/schema) and how (table/view/temporary) things are built is defined in a YAML configuration, n
30. 90.▲
    by blakeburch 5y ago

    Shipyard, Prefect, Dagster are all good options. Lots of newcomers in the orchestration space.