zlacker

Are the teams working on Figma known to be like that? I’ve only heard good things about Figma honestly, but all before the purchase by Adobe.

>>graype+(OP)
They're known for consistently shipping significant new features fast, so call it what you want but whatever they do works!

What you really don't want is to work at a ticket factory where every ticket is for a new hack that could be avoided by paying down basic technical debt :)

>>kajeco+x
>consistently shipping significant new features fast

This is an external result of talent. However, it's also an external result of bad management. From the outside, we can't see how much of column A and how much of column B it really is, until the day we notice superfluous features, weird UX, bugs, and fix timelines on the order of years. Figma did give me almost 100% column-A vibes more than almost any other product I've used, so I was quite optimistic, but since the buyout I've noticed a few bugs/UX-issues of the concerning variety, and regardless of whether that timing is a coincidence, I'm starting to worry that in the end it will just be more business as usual for this piece of software.

Edit: Since the buyout announcement. But again, no idea if it's related.

>>graype+(OP)
PM over here at Figma. We don't have dedicated bug teams whose only job is to fix incoming bugs. Feature teams are responsible for their own bugs, so we typically have an ebb and flow of feature work vs quality work.

Quality is also pretty high on our pri list for leadership, so we typically don't have pushback if we want to focus on bug fixing vs pursuing new features.

Also just FYI, the purchase hasn't gone through yet.

>>jjcm+x8
Hey that sounds more like what I’ve heard then! :)

And as for the pending Adobe buy-out… you can’t say it out-loud, but I can: I really hope they treat you folks right, but I doubt they will. Figma is awesome. Probably too good for a company as famous for it’s customer hatred as Adobe.