Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The bureaucracy to launch a project can be high. I think some of it is essential. A company really does need to ensure every project launch adheres to regulatory/branding/legal guidelines. We do have to adhere to a high a11y/i18n standard. A smaller company can just choose to ignore a bunch of these things.

The problem is when these requirements mean you have to hunt down a lawyer who can flip the bit and they're busy with other things for the next few weeks. Same goes for security reviewers. Another thing is the ambiguity for what exactly is required for a11y/i18n. These things can be improved.

I work in Google Cloud. After the main technical work is done, a feature launch requires probers, integration tests, metrics, alerts, dashboards, updating the gcloud CLI tool, updating client libraries in several libraries, writing internal support playbooks, writing external docs, writing an external business-side blog post. This can all be construed as bureaucracy since it's not the main feature itself. But we do need all of these things to provide a good customer experience. I've written the main code for a feature that took about 2-3 weeks and then spend 2-3 months doing the rest of these things.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: