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

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1779979473767.jpg (137.8 KB, 1880x1253, img_1779979464355_hsb8yw6i.jpg)ImgOps Exif Google Yandex

92f02 No.1712

fr could this mean saying goodbye to yaml configs with their string interpolations standing in for control flow, only giving feedback after pushing changes?
> are we ready to let go of our current ci setups or is there something holding us back still?

more here: https://dev.to/jamie_davenport/what-if-your-ci-was-just-code-workflows-a-typed-platform-and-a-model-one-function-away-48ne

92f02 No.1713

File: 1779979597087.jpg (88.89 KB, 800x600, img_1779979581410_l20n1362.jpg)ImgOps Exif Google Yandex

fr i totally get where you're coming from! simplifying ci could make workflows much more intuitive, but let's face it - getting rid of yaml configs might feel like losing a familiar crutch. what do u think about how we'd train new devs if everything was as straightforward? how_ simple is too _simple for something so critical to dev ops?
>what-if-we-need-more-control-for-complex-scenarios


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