|
|
|
|
|
|
by RogerL
4261 days ago
|
|
|
Bringing this back to the slides, I don't see how this applies to most companies. At most places we are utterly swamped with work; the idea that we can go just build something to allow us to have a conversation is pretty mad. Most companies don't have Google's resources, and I don't see how this advice is remotely possible. I can't build the things I need for what we are already expected to do; I certainly am not going to put that further in the hole to build something that will also not have enough resources to succeed. I'm not arguing with your position, just reflecting on the slides. They seemed to be saying 'this is how you (not google) should be doing it', ignoring the kind of cash flow that is required to make that happen. |
|
|
But one of the key points so far is a 50/50 mix of engineers/other-roles.
If you're swamped with work - especially if it's busywork! - there's a case for an internal product. If it's not busywork - it means you need to hire ;)
If you can't afford to hire, you've got bigger problems.