zsteinkamp

I'll look into it. Never created a thread (and maybe this is my fourth comment :).

Take the lead on starting it in your team :) Just invite a user to a Zoom call and ask them some questions.

It's a truly phenomenal group of people who are building it too! :D

Hard disagree. Stripe the business decided to cut costs for whatever reasons. While I was shocked the morning of the layoffs, I don't think anyone could have been given a softer landing by the company. I don't think a business needs to be a charity, just as I don't donate my time to the company outside of a normal work week. It's business and I think they handled their business decision very well.

I hope you've found a suitable replacement job! LMK if I can help.

Try it today :)

Thanks for adding these points :)

I should have chosen my words better in the post.

Of course, access is restricted to people whose jobs relate to the data (i.e. developers), and the data that is accessible is also controlled.

The point I was trying to make was that there is a difference from other organizations where I've worked, where access to relevant product data in the warehouse is given by default to dev teams, and is accessible both interactively (for debugging or decision making) and from batch/cron jobs.

I'm happy to hear this isn't a new thing! I just wish more people/companies would embrace the practice. Once you've experienced it, it just feels like common sense. :)

Sorry if I wasn't super clear in the post. There are still controls over visibility of data, and data access is very tightly logged and audited. This is data the team needs to do an excellent job for the customer. The difference from other companies where I've worked is that in other places the dev team would have to create their own mini-warehouse, or suffer through months-long project management flows to get on the data team's roadmap.

Great posts! More engineers should read and write such things :)