This message was deleted.
# general
s
This message was deleted.
l
Whenever I hear anything to do with pipeline infrastructure, I think of the old 3D background Windows used to use, would be neat to have a name that calls back to that!

https://www.youtube.com/watch?v=MKqrLGFoK9E

j
Continuous Delivery Team?
a
Development Infrastructure
b
k
I want to say that's what "gitops" does, but "sysadmin" has split into so many terms and flavors that I am not entirely sure on the accuracy of my own statement.
c
We referred to this team as Delivery Engineering at my last company.
k
this but the nickname is RelEng 🙃
k
@KirstinS - pronounced "real eng?" hahahaha
r
My first gig was in an org called “Software Integration and Release”. We were addressed as SIR, of course.
p
I thought it would be interesting to ask this to chatgpt, here are the answers: 1. CI Wizards: Highlighting their expertise in Continuous Integration. 2. Pipeline Pioneers: Emphasizing their work on pipeline infrastructure. 3. GitLab Gurus: Focusing on their proficiency with GitLab. 4. RegTech Innovators: Combining "Registry" and "Technology" to signify their work with registries. 5. Code Flow Architects: Highlighting their role in managing the flow of code. 6. DevOps Enablers: Indicating their support for the DevOps culture. 7. Automation Artisans: Emphasizing their automation skills. 8. Release Orchestrators: Signifying their role in orchestrating releases. 9. Codeflow Catalysts: Highlighting their impact on the code deployment process. 10. DevOps Maestros: Emphasizing their mastery in the DevOps domain. 11. Pipeline Pros: Focusing on their expertise in pipeline management. 12. CI/CD Commandos: Combining Continuous Integration and Continuous Deployment for a dynamic team name. 13. Repo Rulers: Signifying their influence over repositories. 14. InfraMasters: Indicating their mastery over infrastructure. 15. Version Virtuosos: Emphasizing their role in managing software versions. 16. Release Rigging Crew: Using "rigging" to suggest their involvement in setting up configurations. 17. Code Surgeons: Highlighting their precision in handling code deployments. 18. InnoFlow Engineers: Combining "Innovation" and "Flow" to suggest their innovative approach to code deployment. 19. TechTranscenders: Signifying their transcendence of technical challenges. 20. Agile Artificers: Emphasizing their adaptability and skill in crafting efficient processes
b
thank you all for the ideas! this is great. i really appreciate the feedback
k
"DevOps Enablers" is my personal favorite, tho it might be tied with "Repo Rulers"
b
repo rulers 😍
a
My advice is that this name matters more than you’d expect - i’d steer away from anything that gives a sense of divisiveness
Its a central team that needs respect from engineering as its an extremely serious role thats cross cutting. You want a name that invokes stability, sense of purpose, and competency.
b
steer away from anything that gives a sense of divisiveness
-yes that seems huge. thanks for pointing that out
a
@Brandon Vicinus it depends on what the team is doing. Release engineering i feel is the correct terms as it is a Site Reliability Engineering area of responsibility https://sre.google/sre-book/release-engineering/ You could wrap it up as a capability of a platform team E.g. Software Quality Platform