Where the design community meets.
I'm the first to say that we've hit peak jargon related to leadership, but I genuinely have had a nearly 180-degree experience from what this article espouses. After many years of experiencing the full spectrum of leadership (really good to really, really bad), I can say without a shadow of a doubt that it absolutely matters in a profound way. Leadership's presence in a team (or lack thereof) sets the tone for how people work, how they think about work and how they work with others. I've just seen it too many times in actual practice and while I often shudder at leadership catch-phrases, the impact and importance is real
I also have come to believe that culture is not the outcome of success (see: Uber). I've seen great teams build do great work firsthand - only to have a problematic culture slowly erode all that was built. And while I'm uncertain if success and culture are 100% directly related, I can say that a good culture creates an environment that's much more disposed to long-term success. Culture won't fix a lack of talent, but it can definitely bring out more in people as well as create an inviting space to more easily recruit high-level talent.
Don't let the cliché word-babble cause cynicism of the fundamental importance of strong leadership and a team culture that sets people up for success. The words will come and go, but those pillars won't.
I think a lot of the final decision comes down to the depth of features you rely on daily. Are team members mainly checking for basic visual attributes (e.g, placement, color, type treatment, etc.)? If so, Abstract would likely do the trick. Zeplin has been at this game for a long time, so there's a lot of depth to their product. However, I'd be curious how critical a lot of those nitty-gritty features are to product teams.
Have you talked to your dev team to see what the mission-critical features are within Zeplin that they depend on to get their job done? That seems like a pretty good way to determine the potential efficacy of Abstract.
Submitting content from your own blog/property is fraught with conflicts of interest. Given the nature of publishing at this point (DN not being the exception to this), it's hard to ignore and assume it's of an altruistic nature.
If the content is worthy, readers will submit it.
If there's one thing I'm certain of, it's that InVision and Atlassian are perfect for each other.
Can we please stop with the constant Toptal spam?
I humbly disagree with this take. I think the major win for a tool like this is the opportunity to use existing React components Framer X that your team/company has produced for product development. This opens up the possibility for designers to create interfaces from the same UI building blocks used in production - meaning that all teams are working from a single source of truth.
This would be huge. Mind-blowingly huge.
So, yeah, your prototype won't be production-ready. I think that's a safe assumption. However, the ability to design an interface with the same UI components developers use to build them will have a profound impact on how teams work together to make software.
I've bought into the notion that Framer is on the right track concerning design tools - however, everything looks good in a product marketing video. This tool is playing with uncharted territory - which is good, but it means that there's ample room for quirkiness.
Nonetheless, I'm excited that Framer is helping lurch design tools towards this direction - it's needed and the obvious next step (in my opinion). I'm skeptically optimistic.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.