hudixt
Joined 11 years ago
Karma
54
Submissions
19
Member since
Sep 26
Recent submissions
Comment · 4 years ago
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.
Comment · 4 years ago
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.
[1] https://www.youtube.com/watch?v=Nc-TlgeKBSE [2] https://github.com/crusherdev/crusher
Comment · 5 years ago
Added one more point on API. Also, you'll probably end up using one more library called classname for better classname management.
https://www.npmjs.com/package/classnames
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.
Comment · 5 years ago
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.
- Dynamic control over style. Basically your stylesheet is JS function returning style. You can do anything here. See this https://github.com/styled-components/styled-components/issue...
- Support for JS reference in color, font sizes, etc with editor support. It'll lead to more consistent design system.
- More cleaner API when using media queries, pseudo states. eg-https://emotion.sh/docs/media-queries
Another alternative is Emotion, also I find it to be much more cleaner in code perspective. (Good performant library in terms of layout and painting).
Why is export option not available for most CSS in JS (some suggested this as solution)?
Read this https://github.com/emotion-js/emotion/blob/bcf40cf2c20153481...
Is it worth it?
- Depends a lot on context and your perfonal objective. Generally I personally feel it's worth it as it's good tooling.
- CSS in JS is lot better than what it used to be. Styled component had good perf bump in last few years.
Comment · 5 years ago
I had done same thing around this in 2019. This doesn't stop at this.
There were quite correlation that I was able to find with basic setup
The results can be quite horrifying as you can predict plethora of things.
- When is someone sleeping.
- When they're working,etc.
- If two person are talking to each other in closed group.
Comment · 5 years ago
This is sleek. Latency is quite good. Is this mjpeg/h264 stream? And are servers hosted globally or in particular region?
Meanwhile a product like this is good competitor to https://mightyapp.com/
Comment · 5 years ago
This should be same for many language. Many Indian languages doesn't have a concept of upper/lower cases.
Comment · 5 years ago
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?
twitter - 1x_engineer