Re: [tlug] No video playback in Iceweasel

[Benjamin Kowarsch <trijezdci@example.com>]

I have to respectfully disagree with the hacking some code as part of
the interview process part.

On 5 December 2014 at 17:15, Josh Glover <jmglov@example.com> wrote:

> All you have to do to be horrified at the state of your profession
> (and, by extension, all other professions) is to include a programming
> assignment and/or peer programming session in your interview process.

Coding as part of the interview process is part of the problem, not
part of a solution.

It favours practitioners who jump right into coding without any
requirements solicitation process, without any design, without any
implementation plan. The kind of person who will excel in such a test
is the kind of person that is not accustomed to proper process.
Preparation takes time and it has to be practised in order to be
mastered.

To produce quality, there has to be a proper requirements solicitation
process at the end of which there is a requirements catalog
categorised into must-haves, should-haves, could-haves and most
importantly will-not-haves. Then there has to be a proper design
process at the end of which there is a specification document.
Finally, there has to be a risk management and planning process at the
end of which there is an implementation plan with a mitigation
strategy.

Only at that point should any coder be allowed to write the first line of code.

Foregoing proper preparation is precisely the reason why software is
so bad these days, why projects go out of scope, over time and over
budget. And if organisations do not ask for proper preparation,
practitioners won't develop the necessary skills. Unfortunately, this
is common practise now, and as a result, the art of thinking and
weighing before doing has been lost.