New ask Hacker News story: Ask HN: What would you do for developer experience
Ask HN: What would you do for developer experience
2 by Atotalnoob | 5 comments on Hacker News.
Hi, I’m a principal engineer and I’ve been put in charge of developer experience at a company I’ve just joined. Currently: - this is a .NET, JavaScript, and python shop with around 100-200 engineers. I don’t know exactly, because they don’t even have a full list!!! - CI/cd is manually configured by a centralized team. - cloud is not meaningfully leveraged (it’s all VMs, including for things like queues (which was manually built in house)) and is also centrally and manually configured. - little to no documentation - no shared libraries - code is siloed off by team My plan is to - create ci/cd templates, starting with a paved path into k8s - create iac templates, starting with the most common patterns - create a shared wiki and require teams to put access directions, openAPI specs, and each environment urls. - scan all repos for secrets and make internal access the default - require linting and security scans on all code. - create a quarterly summary and survey of engineers. - create standardized new app template. What else should I do? What else should I start implementing?
2 by Atotalnoob | 5 comments on Hacker News.
Hi, I’m a principal engineer and I’ve been put in charge of developer experience at a company I’ve just joined. Currently: - this is a .NET, JavaScript, and python shop with around 100-200 engineers. I don’t know exactly, because they don’t even have a full list!!! - CI/cd is manually configured by a centralized team. - cloud is not meaningfully leveraged (it’s all VMs, including for things like queues (which was manually built in house)) and is also centrally and manually configured. - little to no documentation - no shared libraries - code is siloed off by team My plan is to - create ci/cd templates, starting with a paved path into k8s - create iac templates, starting with the most common patterns - create a shared wiki and require teams to put access directions, openAPI specs, and each environment urls. - scan all repos for secrets and make internal access the default - require linting and security scans on all code. - create a quarterly summary and survey of engineers. - create standardized new app template. What else should I do? What else should I start implementing?
Comments
Post a Comment