4 ms·

Such great feedback, Tom. Thank you for taking the time. I'm definitely going to distill all your notes and thoughts on this. It's funny you mentioned Microsof

Such great feedback, Tom. Thank you for taking the time. I'm definitely going to distill all your notes and thoughts on this. It's funny you mentioned Microsoft FrontPage. Alexis Ohanian [0] also made the same comment :) [0] https://twitter.com/alexisohanian/status/1448288261172989960?s=20 https://twitter.com/alexisohanian/status/1448288261172989960...

tomhallett 5y ago
Thought experiment below -- Setup: In the data warehouse world, there is a very interesting trend happening with the rise of the "Analytics Engineer". Historically, all data transformations had to happen with "handwritten python/hadoop/spark code" by a software engineer. This process is expensive and slow, because they are often translating SQL code written by a Data Analyst into python/spark code. But with dbt [1], we see Data Analysts becoming Analytics Engineers. They know a lot about SQL, a lot about the dbt framework, a bit about jinja macros, a bit about yaml, and a bit about the command line - now they can create some really powerful data transformations which is the underpinning of the "Modern Data Stack". Thought experiment: Right now, we have a problem where any change to a figma design requires a software engineer to update the react application. What about if tools like makers enabled a "dbt-like" workflow, where a "Component Engineer" can turn a figma component into a "simple react component". A component engineer's work flow would be based on makers, storybook, and a cloud IDE. The goal being that designers start to become "Component Engineers", in the same way that many "Data Analysts" have become "Analytics Engineers". [1]: https://discover.getdbt.com https://discover.getdbt.com
- johndamaia 5y ago
  This is brilliant! We designers like freedom of thought, and Figma give us that. The goal with makers.so is: inside the same tool I use to lay out ideas, I can also publish them (i.e. use makers.so components) without ever depending on a developer or third party app. A "Component Engineer" is this second stage of the process (after playing around, I can now publish this with some rules).
  - tomhallett 5y ago
    Congrats on makers - I think this will be very very cool! I'll give it a spin and show it to our designer.
    - johndamaia 5y ago
      Thanks Tom. I'd love to hear yours and your designer's thoughts about the plugin. Happy to answer any questions you might have.

tomhallett 5y ago

Thought experiment below -- Setup: In the data warehouse world, there is a very interesting trend happening with the rise of the "Analytics Engineer". Historically, all data transformations had to happen with "handwritten python/hadoop/spark code" by a software engineer. This process is expensive and slow, because they are often translating SQL code written by a Data Analyst into python/spark code. But with dbt [1], we see Data Analysts becoming Analytics Engineers. They know a lot about SQL, a lot about the dbt framework, a bit about jinja macros, a bit about yaml, and a bit about the command line - now they can create some really powerful data transformations which is the underpinning of the "Modern Data Stack". Thought experiment: Right now, we have a problem where any change to a figma design requires a software engineer to update the react application. What about if tools like makers enabled a "dbt-like" workflow, where a "Component Engineer" can turn a figma component into a "simple react component". A component engineer's work flow would be based on makers, storybook, and a cloud IDE. The goal being that designers start to become "Component Engineers", in the same way that many "Data Analysts" have become "Analytics Engineers". [1]: https://discover.getdbt.com https://discover.getdbt.com

johndamaia 5y ago
This is brilliant! We designers like freedom of thought, and Figma give us that. The goal with makers.so is: inside the same tool I use to lay out ideas, I can also publish them (i.e. use makers.so components) without ever depending on a developer or third party app. A "Component Engineer" is this second stage of the process (after playing around, I can now publish this with some rules).
- tomhallett 5y ago
  Congrats on makers - I think this will be very very cool! I'll give it a spin and show it to our designer.
  - johndamaia 5y ago
    Thanks Tom. I'd love to hear yours and your designer's thoughts about the plugin. Happy to answer any questions you might have.