comment on

I have just recently added the following questions to my list:

Do you have QA/Staging environments that accurately mirror the production environment?
Do you use code review, and if so, must new code be approved by review before going to QA?
Do you use dev and story branches or is it held that master must always be ready to push to production? If the latter, how do you avoid having un-reviewed code or code that has not gone thru a proper QA being pushed by accident?

These questions might seem a bit forward given this stage in your career, but as time goes on you will understand why they could play a role in your deciding to take a given job.

It helps to remember that the primary goal is to drain the swamp even when you are hip-deep in alligators.

In reply to Re: Job Questions by boftx
in thread Job Questions by PerlSufi

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		`&`
	<		`<`
	>		`>`
	[		`[`
	]		`]`

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.