This is an "old" thread now, but something that stands out to me here is how damaging things like this must be for Notion's ability and opportunities to recruit

This is an "old" thread now, but something that stands out to me here is how damaging things like this must be for Notion's ability and opportunities to recruit developers. I interviewed with them years ago after sharing a lot of feedback and bug reports in their early years. I was PUMPED about this space and really wanted to help make something like Notion awesome. I wanted it to work for me, I wanted it to work for others, and I knew there would be tons to learn in the space. But my impression of Notion (not their devs specifically) left me feeling like it wouldn't happen there, and I just abandoned the process. This happened with Slite, too. But it's stuff like this which lead me to believe I shouldn't work on those teams. As a dev, I probably can't fix that the company overwhelmingly doesn't care enough about making an important feature work. I noticed a keen interest in my ideas about which features me or my team needed, or how existing features could expand to meet our needs, but not much interest in fixing bugs or limitations. Now we're here, and the export feature doesn't work while the company continues to move forward with other things. I can't help but think this sort of outward appearance has a negative affect on how easily they can hire, and who they can hire. This sort of things is a nail in the coffin for me - I don't want to work somewhere where we deploy day after day after day knowing that things are effectively broken.