3 ms·
So this is all well and good if you work with a team like this. But I have two questions: (a) How do you find out, before going to work somewhere, whether they
by svdad 15y ago
So this is all well and good if you work with a team like this. But I have two questions:
(a) How do you find out, before going to work somewhere, whether they actually work like this? Are there questions you can ask? Word of mouth? ... ?
(b) If you don't work somewhere like this, how do you start putting professional processes in place? Assuming in particular that you have never actually worked somewhere like this, so you can't speak from experience, only from instinct about what seems to be a good way of working.
- deleted 15y ago[deleted]
- groby_b 15y agoa) You ask. "What is your development process". Places that have a decent process are more than happy to share that with you, usually b) Read. Talk to colleagues at other companies. Find things that improve your process and introduce them locally for yourself. If it seems to work out, share. Careful of politics there, though. Find out if there's anybody who "created" the process, make sure you get them on your side. It's always easiest to introduce change if you have proof ;) If it would be a larger change you can't do by yourself, try to make a compelling case with attached metrics. "If we do FOO, it'll reduce our broken build time by x%". If you can't measure those metrics, start measuring. And if you're making up how much you'll save, be as conservative as possible ;)