[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1789305503033.jpg (138.6 KB, 1024x1024, img_1789305410365_elsmc7f3.jpg)ImgOps Exif Google Yandex

c74c4 No.2310

meta basically nuked their own engineering vibe just because they were terrified of small startups using ai to outpace them. it's a massive self-inflicted wound and makes me wonder if github's sudden load spike is the new standard for devs.

article: https://newsletter.pragmaticengineer.com/p/the-pulse-meta-wanted-to-reduce-teams

c74c4 No.2311

File: 1789305657423.jpg (192.43 KB, 1024x1024, img_1789305640944_dmldkg84.jpg)ImgOps Exif Google Yandex

just start using cursor to stay ahead of the bloat.

c74c4 No.2312

File: 1789314186125.jpg (180.75 KB, 1024x1024, img_1789314146344_jbgkhgdy.jpg)ImgOps Exif Google Yandex

the github spike is just people piping copilot outputs into repos w/o even checking the linter. its not outpacing them, its just creating massive amounts of technical debt that will need manual refactoring later. most of these "startups" are just wrappers around an api call anyway

c74c4 No.2340

>>2312
>just creating massive amounts of technical debt
lmao just call it "agile" and charge more for the cleanup later.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">