I.e. in a vertical layout, a rectangle at Y=0 and another just south of it at Y=100, the first should be at Z=0 (top in layer sidebar) and the second southernmost at Z=1 (bottom in layer sidebar.)
Addendum: internally I believe the Z values are actually inverse. I.e. Z=0 is behind Z=1, like in HTML, so technically what mechanic I'd prefer is more accurately described with this example: Y=0⇒Z=0, Y=100⇒Z=-1, Y=200⇒Z=-2, ...
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Re building tools: I strongly believe that tools — software libraries, utilities, etc. — should only be created to solve an issue which you have a direct relationship to. History has proven this to be an excellent measure of success.
[Thread ...]
Most of us have probably experienced the "CRM system made for other people" that sucks, because the creators of it didn't use it themselves and thus couldn't relate to the problems their thing was solving.
So here's some good terminology:
- "Me ware"
- "Us ware"
- "Them ware"
"Them ware" is the worst possible thing; a "none of the roads taken" kind of compromise. You build something for someone else without a need of yourself. It will be incredibly hard to make something good this way since you will essentially fly blind.
Although this article is a bit too extreme and an overreaction, I must say that as a non-Chrome user it seems more and more websites only work in chrom{e,ium}. At least once a week I have this experience (I use Safari.) Thread →
The contemporary idea of a web browser is an abstraction layer for technology to allow some document or software to be available to anyone using a web browser. If your website only works in Chrome it’s really not different from say only working on macOS.
There’s a cost to everything and with web development a big chunk of cost is in quality (making a UI reliable and behave the way a user expects it to.) An increasing cost area is also writing & testing browser-specific code and that seems really backwards to me.
We're growing our Editor engineering team here at @figmadesign. This is an amazing opportunity to work on OS-level engineering challenges together with a wonderful, small and diverse team of passionate humans.
Are you a person who identifies with a group that is often underrepresented in software engineering? Then we are particularly interested in talking! We strongly believe that diverse minds, opinions and perspectives makes for a better life and better software.
@fionaosaurusrex@figmadesign Another example from Figma's initial community & plugins launch in 2019. One file with one page that documents every part of the design, synced daily between PM, Eng and D.
@fionaosaurusrex@figmadesign Some more diagramming examples from the community & plugins Figma feature from 2019.
To me, “design” is a very broad subject. In the case of industrial design—what my peers usually think of when we say “design”—is mainly about constraints. Here’s another way of viewing the practice:
Here’s an overly idealized view of what you might thing design is: