I refer to these people as the "glue" between two departments.
At big companies, this is mostly a management issue.
Questions like these are common
1.) Is this person part of the design team or engineering team?
2.) Who does this person report to, and how is his sprint planned?
And, as a company grows in size, managing people becomes a more important issue than focusing on minor product details.
We have built something along these lines, Crusher [1] (demo [2]) is an e2e framework, you can trigger test with click of a button. It's built on top of playwright.
We’re thinking of adding watch mode in the coming months - running tests continuously in real-time. Sending you an email to exchange ideas.
P.S.- there might be few typos. It’s work in progress.
In the end, I generally prefer to use tailwind + emotion. My goals usually is to save time and make system more consistent rather than perf gains, which isn't that much on new systems.
A 4 year experienced react dev here. I have had decent time working with different styling
I'll try to answer few common things for everyone's context
Why even use CSS in JS?
- SPA bundling usually loads all CSS at once and all styles collide. You need to be super good at naming stuff/or load CSS based on module. So your CSS will be conflicting, so scoping is helpful here.
- Not having to jump from your component file to CSS file. Save some context switching or few strokes.
Love you're using WA and it's Apache2.0. I do get the sense of idea but felt it's not clear on it for whom it's targeted, business or consumer?
If it was for consumer and integrated with existing tool, I would love to try it. Had pain point where even big zip file would quite good amount of time to generate. Not sure if FB, google does that to introduce friction in the process.
On Dev front, why would companies like Google, Uber, Linkedin be willing to adopt this standard?
It teaches coding to kids of age 6 charging upto 1500$ for 100 clases.
To sum up, this is very high amount from any standar, parents take loan to fund this. Second, they use black hat marketing tactics claiming 10year old student now earns million of dollars.
I'm not sure if there tactics are even legal. Platforms like FB, Google should fact-check on ads.
Seriously how can you believe a kid is earning 10mn$ a year. And has no mention anywhere on the web.
We're also to building SAAS produt which is very similiar[1].
Things we are supporting
- No-code test creation. Both playwright-cli and QAwolf supports it.
- Much more control over elements. We're using native chrome extension to achieve it. Integrated ChaiJS on top of it.
- Automated screenshot capturing, video + all debug info (console, network, DOM) when test fails.
We're looking for early beta users. If you're interested in trying it out + pizza send along your way, please fill this form https://bit.ly/2FU2Vc4.
P.S.- We're planning to start beta testing in couple of days.
At big companies, this is mostly a management issue.
Questions like these are common 1.) Is this person part of the design team or engineering team? 2.) Who does this person report to, and how is his sprint planned?
And, as a company grows in size, managing people becomes a more important issue than focusing on minor product details.