All of the properties controls are bound to a network request. This is a big bummer. I don't like having to wait 400ms every time I change a color.

We shouldn't diminish the power of transform here. It's not just one property like opacity. You can animate quite a bit on the compositor with transform

I agree with exactly one sentence in the comment thread so far. "CSS requires experience"

If you're interested in actually learning css, and don't just want to complain about how poorly written css is bad, this website is invaluable and provides concrete examples of how to build layouts and style elements.

https://web.dev/learn/css

I agree, but I'd even say that becoming pro at CSS is orders of magnitude easier than becoming pro at your average programming language. I think engineers just tend to not take the task seriously, and don't apply themselves enough.

You just need to actually understand the box object model and a handful of common gotchas.

CSS is essentially declarative programming for several different black-box systems.

How selectors are written has exponential performance implications. Using the wrong type of transform might make your page forego hardware acceleration, or use more battery on a mobile device.

At least typical programming languages are targeting a known set of environments and devices with known characteristics.

You definitely need to understand a lot more than the box model and a handful of gotchas.

Location: Chicago

Remote: Yes

Willing to relocate: to New York

Resume: https://docs.google.com/document/d/1KT6-A2h77RRVvd4IL__OOv_7...

Email: alex.m.sheehan@gmail.com

Open the resume if you need:

- Any frontend technology built - An engineer with a background in interaction design - An interaction designer who can code - Cloud services stood up - Legacy code modernized - Creative technology

React / NextJS / Angular / Idiomatic JavaScript (Typescript) / Firebase / Postgres / Node / Express / Koa / AWS / GCP / Testing / Interaction Design

Hey, we're looking for a 3rd full-time engineer (Javascript primarily). We're a startup that builds apps on the Salesforce app marketplace. Despite our size, we're generating significant revenue, so it's a very stable role with a lot of growth potential. Here’s the job req: https://bit.ly/ApsonaDeveloper. Let me know if you're interested.

I don't think I'm breaking any NDAs by saying that that is just entirely not what happens.

>" I don't think I'm breaking any NDAs by saying that that is just entirely not what happens. "

Could you please rephrase this? I don't understand that sentence.

Thanks I was wondering too. I think it means “it happens partially” but that can’t be right as it doesn’t seem noteworthy. Although glad that GP isn’t breaking NDAs with that fortune teller statement.

My guess is that it was just a way to rebut the accusation by bragging about working there. I’m not sure that it worked though.

We don't

Naming things is the Vietnam of computer science. I wrote a haiku for it:

A quagmire of bad decisions made in haste, haunting us— years later.

I don't think you read it correctly. What we're doing, indeed what we've done since 2008, was borrow at a historically low interest rate to pay back interest and debt bought at a higher interest rate.

Thank you! We hope so too. There's so much first hand knowledge locked up in inboxes that people would like to share.

Currently we rely on the gmail API, but it is on our roadmap to expand to the other major email providers. Is there one in particular that you would like to see on FWD:Everyone?