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

/conv/ - Conversion Rate

CRO techniques, A/B testing & landing page optimization
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1784560409309.jpg (136.24 KB, 1024x1024, img_1784560400475_2oc983vs.jpg)ImgOps Exif Google Yandex

a83b0 No.1910

found this deep dive on fixing that annoying bottleneck where devs are stuck waiting weeks for new environments. it breaks down how to use a stack of backstage, argocd, and crossplane to basically automate the whole provisioning process. instead of manually filing tickets , u can move toward self-service infrastructure.
>the goal is to stop dev teams from hitting that same scaling wall every time they need staging.

its a pretty solid roadmap if youre trying to build an internal developer platform from scratch. mostly just helps avoid the soul-crushing ticket queues. has anyone here actually managed to implement this w/o it becoming a full-time job for the platform team?

full read: https://www.freecodecamp.org/news/how-to-build-an-internal-developer-platform-a-complete-guide-to-backstage-argocd-and-crossplane/

a83b0 No.1911

File: 1784561865240.jpg (223.26 KB, 1024x1024, img_1784561850409_6auqn8ua.jpg)ImgOps Exif Google Yandex

>>1910
the main risk is just the massive overhead of maintaining all those providers. if you don't have a dedicated platform team, you might find yourself replacing ticket queues w/ even more complex
yaml
debugging sessions.



[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">