-
…in reply to @swyx
swyx adamstac jerodsanto Thanks for sharing! This podcast gave lots to chew on. I was especially intrigued by the question about why VPEng and CTO are more likely to be from backend.On twitter.com
❤️ 1 Favorite 2021 Nov 7 Mood +2 🙂
-
…in reply to @ZekeAranyLucas
swyx adamstac jerodsanto However, I think you are also right about some of the biases. I see the split being created in the early web, where anyone could build a webpage with geocities. There was joke that you could hire anyone in college to write HTML for $8/hr.Permalink On twitter.com
-
…in reply to @ZekeAranyLucas
swyx adamstac jerodsanto Before the web, PC developers had to write everything, and UI was usually a smaller proportion and rarely required specialists. Game development was totally different of course.Permalink On twitter.com
-
…in reply to @ZekeAranyLucas
swyx adamstac jerodsanto Personally, that changed after hearing Douglas Crockford (FE architect from Yahoo) talk back in like 2008. He is brilliant.Permalink On twitter.com
-
…in reply to @ZekeAranyLucas
swyx adamstac jerodsanto But I noticed another change when Amazon had to introduce FE as an official role (eliminating WebDev). This was because it was attract and retain talent to make UX for both desktop and mobile.Permalink On twitter.com
-
…in reply to @ZekeAranyLucas
swyx adamstac jerodsanto The simplest explanation I see is org based. Most teams that I see have a ratio of low ratio FE to BE devs. That means more BE devs in your pool to find leaders. It's also more urgent to find people who can manage BE better, including more BE career paths. YMMVPermalink On twitter.com
-
…in reply to @ZekeAranyLucas
swyx adamstac jerodsanto I see data engineers with a similar problem in many orgs, where DEs are a minority, and there isn't support for full data teams, etc. And the opposite in some ML teams, where BE devs are a minority, and it's hard for them to find traction and DEs are critical.Permalink On twitter.com