Conversation

Notices

1. Embed this notice
   Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jul-2024 12:13:02 JST Marco Rogers

   This was a great read. It gave me a lot of thoughts about how we overbuild a lot of things these days. "Boring" technology still works really well even up to pretty high scale.

   "Serving a billion web requests with boring code"
   https://notes.billmill.org/blog/2024/06/Serving_a_billion_web_requests_with_boring_code.html

   • Embed this notice
     Bill Mill (llimllib@hachyderm.io)'s status on Wednesday, 10-Jul-2024 12:12:57 JST Bill Mill

     in reply to

     @polotek That’s accurate, I kicked off the front-end then handed it off to teammates. A lot of the decision was choosing what they would be comfortable and familiar with.

     There’s a lot of value for engineering teams to be able to work independently on the front-end and the back end, it lets you bring more people to work with less communication overhead.

     Also I was coming from working on a rails app on healthcare.gov which was a terrible MPA plus rails asset pipeline mess, and the idea of…

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jul-2024 12:12:59 JST Marco Rogers

     in reply to

     FWIW, I wouldn’t make this assumption that the frontend is simple. I think it’s way more likely that the author has a bias towards backend and just didn’t give as much detail about the frontend. https://toolsforthought.social/@billseitz/112759270193346522

     esmevane, sorry repeated this.
   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jul-2024 12:13:00 JST Marco Rogers

     in reply to

     In many ways, the most "boring" technology is the one your team already knows well. Always bet on existing experience and expertise before asking your team to learn something new.

     However, I think it's a huge problem that we currently live in a world where there is no equivalent to "boring technology" for frontend. As an industry, we've lost the collective knowledge of what the boring alternative looks like.

   • Embed this notice
     Marco Rogers (polotek@social.polotek.net)'s status on Wednesday, 10-Jul-2024 12:13:01 JST Marco Rogers

     in reply to

     Yep. I noticed that. It's worth noting that he basically says "I didn't want to choose this. But building a multi page site would've taken longer."

     That's a hell of a statement. I disagree in general of course. But the context is important. Essentially he makes an assessment of his team and what they would able to get up to speed with. Building a SPA with react is the only thing they knew well enough to give them confidence. There is a lot to unpack there.
     https://toolsforthought.social/@billseitz/112759194466807431