[dundee] Defcon-16 Media Archives

[gordon dunlop]

2009/3/12 Rick Moynihan <rick.moynihan at gmail.com>

>
> I offer a small improvement:
>
> If you're going to write a shell script you might as well include the
> user commands before hand as part of the script.  At least that's what
> I first thought; however in this simple case you're better writing it
> on as a one liner:
>
> wget -qO - https://www.defcon.org/podcast/defcon-16-video.rss | grep
> m4v | cut -d '"' -f2 | wget -i -
>
> Redirecting everything through stdout/stdin has the advantage of not
> leaving temporary files on your disk.
>

That's great Rick if you are writing everything for yourself to enable
efficiency but when you are writing instructions on the TayLUG for others to
follow, Nick's more long winded version is preferred. This is due to people
having different levels of knowledge and experience, you want to write
instructions that is easy to follow and so that people have a reasonable
idea of how things are being derived i.e. showing your working, so that they
can apply this knowledge in other areas. This is only my personal opinion,
but I prefer doing things so that understanding is achieved in addition to
an objective being achieved.

Gordon




>
> R.
>
> _______________________________________________
> dundee GNU/Linux Users Group mailing list
> dundee at lists.lug.org.uk  http://dundee.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/dundee
> Chat on IRC, #tlug on dundee.lug.org.uk
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.lug.org.uk/pipermail/dundee/attachments/20090312/ec7ea19f/attachment.htm