Hi Thank you for the great advice, I can come to a conclusion to train a team internally from ground up
-Dan On Sun, May 31, 2015 at 11:21 PM, Mirko Friedenhagen < [email protected]> wrote: > Hello Dan, > > I started as a "normal" Python developer, then built and led a team of test > automation engineers while the management decided to switch to Java 10 > years back and inherited CruiseControl, which we dropped for Hudson. I had > some small scale operating experience as well (email server/router). One of > my nowadays colleagues has been test automation engineer as well, the other > one was always into building completely. > > I think because release processes are often very company/product specific > (at least when you got a huge legacy baggage), building engineers are > easiest trained or formed internally. However, without input from the > outside, you might miss fresh ideas. > > Regards > Mirko > -- > Sent from my mobile > Am 01.06.2015 02:59 schrieb "Dan Tran" <[email protected]>: > > > > > > > > > > I'm sure I've said it before, but part of Maven's problem is that this > is > > > all magically taken care of behind the scenes and less people need to > > know > > > how it works to make it work. > > > The downside is that there are then less people who can fix things when > > > they need fixing. > > > > > > > Exactly, it is hard to learn magical thing > > > > I used to train a QA turned dev with java j2ee server testing backround, > > and > > it took a couple of years > > > > is it norm here by slowly training internally from start ( ie java)? > > > > Thanks > > > > -Dan > > > > BTW, i full understand that this type of discussion my be touchy, so I > also > > very appreciated to any one who is able to share with private email > > >
