Conversation

Notices

Embed this notice
Marco Rogers (polotek@social.polotek.net)'s status on Monday, 05-Aug-2024 03:54:00 JST Marco Rogers

My frontend villain origin story was when I started asking people why we needed this complexity. People agreed it was complex. But when I asked people to tell me what we bought for ourselves, the answers were vague and unclear. That’s when I knew we had gone astray.
https://mastodon.social/@tef/112903811292290724
In conversation about 4 months ago from social.polotek.net permalink
Attachments
1. No result found on File_thumbnail lookup.
  
  tef (@tef@mastodon.social)
  
  from tef
  
  look i know there's reasons behind "we bundle the entire thing up only then to split it back out into pieces, automatically" but so much of web dev feels like "complex ways to do what you did before for no meaningful benefit other than the satisfaction of solving a harder problem than you needed to" at some point you have to ask why there are webapps that send over a docker container's worth of code to insert html into a web page, where the html is rendered server side for speed, of course
- clacke likes this.
- Embed this notice
  esmevane, sorry (ironchamber@mastodon.esmevane.com)'s status on Monday, 05-Aug-2024 03:53:58 JST esmevane, sorry
  in reply to
  
  @polotek I've done a few rescue missions for clients which turned into sort of "front-end ops" gigs, more or less just wrangling these toolchains sort of like how Kent describes here: https://kentcdodds.com/blog/tools-without-config
  I've found that each team does need a subset of what these kits offer. There isn't always a clear cross-team overlap. Open-source doing it all is definitely why the kits are huge.
  OTOH the bespoke shop-specific way really is costly to invest in. It can turn into a full-time support role.
  In conversation about 4 months ago permalink
  Attachments
  1. Untitled attachment
- Embed this notice
  Marco Rogers (polotek@social.polotek.net)'s status on Monday, 05-Aug-2024 03:53:59 JST Marco Rogers
  in reply to
  
  I mean we know there was ostensibly a reason for every esoteric “feature” in these frameworks and ungodly toolchains. But I’m also pretty sure it wasn’t based on problems that most teams were actually having with any real frequency.
  
  In conversation about 4 months ago permalink
- Embed this notice
  Marco Rogers (polotek@social.polotek.net)'s status on Monday, 05-Aug-2024 09:38:12 JST Marco Rogers
  in reply to
  
  We know this because when we ask engineers on these teams, they have no idea how to use most of this shit. The average dev is thoroughly confused by most of this stuff. And they’re still somehow worried that their app is not good because they aren’t using the more advanced stuff. Complexity is becoming the substitute for expertise. And that’s very bad.
  
  In conversation about 4 months ago permalink
  
  clacke likes this.

Public

Notices

Feeds