The "big boxes" architecture presentation is useful starting point, with an emphasis on understanding constraints and flexibilities. If team builds an API/developer tool, writing demo integrations is essential practice.
-
-
Prikaži ovu nit
-
If they have some programming experience, my other advice would be to try to make a few of the simplest possible pull requests (even just changing text, etc) to get a feel for their team's development experience.
Prikaži ovu nit -
More generally I think books like Accelerate, Building Evolutionary Architectures, Philosophy of Software Design, can be helpful without a direct software writing background, although perhaps too abstract.
Prikaži ovu nit -
Novi razgovor -
-
-
Surprising ways the system fails or works are what I key in on. Could you support 10X users that you have now? Why not? Could you add 10% of your total user total tomorrow? If we added 2X devs what would they work on? ^^ those questions can lead to the surprises
-
Love these questions since they can all expose non-obvious constraints
Kraj razgovora
Novi razgovor -
-
-
Phoenix project
-
That is a great one.
Kraj razgovora
Novi razgovor -
-
-
Regardless of programming experience, pair up with engineers on a slice of work through the full process, design, implementation, deployment and monitoring/observation. It will be mutually beneficial even if they are not hitting the keyboard
-
Have you had a product manager do that with you? I've actually not seen this happen, although it seems obvious in retrospect now that you mention it
- Još 1 odgovor
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.
Irrational Exuberance:
An Elegant Puzzle:
CTO 