News for hackers. Stuff that matters.
Re:How we engineer feedback at Figma with eng crits by nasso_dev on Monday March 11, 2024 @01:17PM (#39670873)
> We’ve been thinking a lot as a team about how to bring AI into Figma and FigJam

i hate how we're not even hiding the fact that we're just looking for excuses to use AI everywhere at this point...

do Figma and FigJam really need AI to solve their problems?? can't the AI use-cases in Figma/FigJam be implemented as plugins? is it okay to not use AI in 2024?

Re:How we engineer feedback at Figma with eng crits by solfox on Monday March 11, 2024 @01:25PM (#39670973)
Why wouldn't they be exploring ways to incorporate a new technology into their product?
Re:How we engineer feedback at Figma with eng crits by mavamaarten on Monday March 11, 2024 @01:27PM (#39671002)
Because incorporating new technologies into a product is not a goal on its own.
Re:How we engineer feedback at Figma with eng crits by itishappy on Monday March 11, 2024 @04:30PM (#39672917)
Depends if you have a budget line for R&D.

If you're flush with cash, investigating potentially game changing technologies can be quite valuable.

Re:How we engineer feedback at Figma with eng crits by jameshart on Monday March 11, 2024 @02:19PM (#39671594)
True. But when a technical capability comes along that makes it possible to get a computer to interact with unstructured human input in ways that would have been impossible to even approach a few years ago, it’s worth having a think about how they could be used in your product.
Re:How we engineer feedback at Figma with eng crits by unclad5968 on Monday March 11, 2024 @01:30PM (#39671034)
Typically you would need a reason to justify spending resources on things.
Re:How we engineer feedback at Figma with eng crits by raziel2p on Monday March 11, 2024 @02:05PM (#39671453)
Agreed, that's why I'm trying to convince my team to ban brain storming sessions.
Re:How we engineer feedback at Figma with eng crits by whywhywhywhy on Monday March 11, 2024 @01:51PM (#39671270)
Honestly tired of being told to use AI in Figjam, tried it once, it sucked. Also tired of turning off Figjam subscriptions that keep getting activated every time one person invites everyone to a figjam document or whatever is causing it to be switched on...

Core Figma is a beautiful product but their tactics to try and milk more revenue out of us are increasingly gross or utterly un-interesting like Figjam.

The tool that surpasses Figma wont take this approach.

Re:How we engineer feedback at Figma with eng crits by emptysea on Monday March 11, 2024 @05:36PM (#39673501)
If you think Figjam is expensive, you should see their new dev mode pricing — I’m sure they’re making a mint!
Re:How we engineer feedback at Figma with eng crits by whywhywhywhy on Wednesday March 13, 2024 @01:12PM (#39694282)
Very clever and sneaky how they positioned "Dev Mode", think I'm the only person on my team who realizes it's a new thing and not just what's always been there and that it also costs extra.
Re:How we engineer feedback at Figma with eng crits by notimpotent on Monday March 11, 2024 @01:30PM (#39671027)
Every tool that I use that doesn't have AI embedded just feels clunky. Any repetitive or predictive task that I have to do should have the option of being automated.
Re:How we engineer feedback at Figma with eng crits by throwway120385 on Monday March 11, 2024 @06:44PM (#39674060)
30 years ago you would have just used a shell.
Re:How we engineer feedback at Figma with eng crits by badcppdev on Tuesday March 12, 2024 @04:38AM (#39677373)
Can you explain which tools are now automated for you?
Re:How we engineer feedback at Figma with eng crits by DecentRecruiter on Thursday March 14, 2024 @05:47AM (#39701947)
It a signaling device to tell the world that you're innovating and/or not falling behind.

Insert the buzzword in your pitch deck, marketing materials, or job posts and you'll see an ROI increase.

Gotta ride the wave, especially to survive or thrive during this tech rut.