3 ms·
There's an equally annoying problem in software engineering at large corporations (aka Google), where hundreds of services you need to know about are named with
by seles 6y ago
There's an equally annoying problem in software engineering at large corporations (aka Google), where hundreds of services you need to know about are named with some cute name that gives you no idea what the thing actually is.
- tryauuum 6y agoSo how would you solve it?
- notduncansmith 6y agoI imagine they work around the direct reference issue by having good search algorithms.
- tryauuum 6y agoI guess. I wanted to know what kind of corporate wiki / database is a good choice for storing / retrieving human-readable, verbose information about servers or services. My current employer uses atlassian confluence for that. So if you don't know what is this server "potato1" with 7 docker containers for, you can type "potato1" in confluence and hopefully get an answer. Maybe in big companies they use homebrew solutions for this
- wenc 6y agoFor AWS, there's a website called "AWS in Plain English" that explain what each service does. For instance, it's pretty hard to guess what AWS Route53 does unless you've come across it elsewhere. https://expeditedsecurity.com/aws-in-plain-english/ https://expeditedsecurity.com/aws-in-plain-english/ Azure naming is comparatively more pedestrian.
- matthewfelgate 6y agoThanks for sharing. That's actually really useful.
- b855f1d0ea394ac 6y agoMicroservices: https://www.youtube.com/watch?v=y8OnoxKotPQ https://www.youtube.com/watch?v=y8OnoxKotPQ [this is a link comedy video about microservice architectures, it should be safe for work except maybe for Uber employees] This is how I feel every day in my new job, there are 3 (depreciated) ways to do everything, and the current way is never feature-complete.