+1
On 30/01/2016 8:14 PM, Kiran Busi wrote:
Agile is really another way to get stuff done, organising a large body
of work into regular deliverables.Â
Why not implement a version of agile in your org you're currently
working in now. Keep the agile principle but modify the process to
suit your org size.
Then next interview you can say "yes" and talk about how you modified it
to xyz and why it made sense to do so.
If you're a good dev who can ship code, and can show it an org shouldn't
turn you away because you haven't done agile. At least it should not be
the make it it break it decision.
On Saturday, 30 January 2016, Brian May <[email protected]
<mailto:[email protected]>> wrote:
Ben Finney <[email protected] <javascript:;>> writes:
> So, the only “tip†there would be to obtain employment with some
> organisation where the applicant *doesn't* need to have that prior
> experience, and then gain the experience on that employer's time.
Then,
> you'll have the experience for the next role.
Then you need to find an organisation that is actually willing to to
invest in your learning and experience. Unlike my previous job, which
was suppose to provide it, but in practise it was a constant battle.
My research of the job market suggests that there aren't many positions
that would be interested in this sort of investment. Including some big
companies. Of course, it is also hard to tell for sure when so much
advertising is from recruiters who don't bother mentioning these
details.
--
Brian May <[email protected] <javascript:;>>
https://linuxpenguins.xyz/brian/
_______________________________________________
melbourne-pug mailing list
[email protected] <javascript:;>
https://mail.python.org/mailman/listinfo/melbourne-pug
_______________________________________________
melbourne-pug mailing list
[email protected]
https://mail.python.org/mailman/listinfo/melbourne-pug
_______________________________________________
melbourne-pug mailing list
[email protected]
https://mail.python.org/mailman/listinfo/melbourne-pug
