While leadership did half-heartedly backtrack on this when we pointed this out to them, the writing was on the wall.

Myself and the other FE principal took voluntary redundancy and left of our own volition since it was clear that FE was undervalued (barely valued?) within the organisation.

I’ve never seen anyone state it as explicitly as you did in this post, but I agree that this bias does exist within the industry.

@collinsworth Fantastic post, and I couldn’t agree more.

In my last role I was one of only two Principal FE devs compared to 19 Principal BE devs.

When layoffs hit in December we were shown the 11 roles that would be remaining for the 21 principals and it was immediately clear leadership had completely forgotten about the front-end discipline when planning these roles as there was no mention at all of FE at any point. Design system, FE tooling, all forgotten about.

@jakelazaroff @brad_frost Ditto, and I absolutely want to be involved in making it, but my worry is that there will be lots of people agreeing but no-one leading the charge to set things in motion, set up a working group, etc.

I read and listen to a lot of very clever people in this community (your good selves included) who are working hard to educate, communicate, and push the web forward. Do you think this needs to be actively led by someone already well-known and respected in the community?

@brad_frost I’m a few days late to this, but I’m another on the “I’ve been saying this for years, you have my sword” list. The collective effort we’re all putting in to rebuilding the same components over and over again is staggering.

I’ve wanted to work on this problem for a while and even spun up a Lit-based playground last year to start trying to figure it out, but it’s a massive problem and the complexity doesn’t lie in the code itself but in the decisions leading up to that