Over the years, I’ve regularly seen blog posts or articles talking about “should designers code?” (less of “should developers learn design?” 🤷). I ...
For further actions, you may consider blocking this person and/or reporting abuse
We don't really have designers where I work; it's really just a bunch of developers with different skills and I tend to be the person to ask about any HTML/CSS stuff (sometimes JS stuff too), and from there the process is usually very similar.
I take a chair, sit down at my coworker's desk, and we start editing things live and trying what works; adding and removing elements, resizing the window, clicking through the application, etc.
This usually leads to problems being found quite early because testing on live data (or a copy thereof) in a real browser just exposes more problems than having only the "ideal" case with a reasonable number of elements on a normally sized screen.
i love your approach too. things proceed so much better further down the line if we test the ideas in the browser as early as possible
Yes am web designer
Html CSS and bootstrap
I use to work side-by-side with a designer editing CSS live to help realize their vision, and it was glorious; but for some reason things changed when stuff went fully remote, and it's been a lot harder to convince people that live pairing is worth it.
awww, that's a shame. does it feel very different through screen sharing?
It does feel worse (at least to me), though not so much so that it isn't valuable to live pair remotely. The micro-lag between transactions, only being able to see one person's screen at a time, can't easily exchange control, etc. overall adds enough drag that it feels like it takes more energy to pair through a screen.