Project -WATCHING YOUR BACK- backing track player

[the_bertrum]

Great progress Rock! I for one vote for Novice status if you've written and executed scripts.

[TheOldPresbyope]

Great progress Rock!  I for one vote for Novice status if you've written and executed scripts.

Actually, I'd vote for a new status: Tinkerer, which to me connotes someone who perhaps hasn't yet learned all the technology but keeps trying different things until "it works". A novice would stop at the first significant roadblock.

Regards,
Kent

[TheOldPresbyope]

@Dorffen

Incidentally, saying “my English isn’t good enough” seems unnecessarily modest. About the only thing I can accomplish in Danish is order another beer.

Regards,
Kent

[Dorffen]

@the_bertrum and @TheOldPresbyope

Thank you very much.

Maybe a mixed rank/status, but ‘stubborn novice tinkere’ might be too excessive? x-D

Thinking about it, starting with near zero knowledge, i’ve actually learned more these past weeks, than i can wrap my head around. Even though it consumes a lot of time, it’s VERY rewarding in the end!

Well Kent, looks like you already have the most important danish in place. ;-D

It might seem like my english is reasonable good, but i take my time to produce correct and understandable sentences, often with a little help from Google and Mrs. Dorffensmirtz.

Kind regards
Rock

[Tim Curtis]

Official Linux skill levels ;-)

Noob: Starting from scratch
Not noob: Tries almost anything to gain knowledge
Novice: Has acquired knowledge and done some cool things with it
Dangerous: Has acquired enough knowledge to destroy things and does so all to often
Expert: Knows everything but still on occasion, wipes a system with a mistyped command due to being momentarily distracted by the family cat or dog

@Dorffen is not Dangerous yet and he's done some cool things with his newly acquired skills so that get him promoted to "Novice" status ;-)

[Dorffen]

Official Linux skill levels ;-)

Noob: Starting from scratch
Not noob: Tries almost anything to gain knowledge
Novice: Has acquired knowledge and done some cool things with it
Dangerous: Has acquired enough knowledge to destroy things and does so all to often
Expert: Knows everything but still on occasion, wipes a system with a mistyped command due to being momentarily distracted by the family cat or dog

@Dorffen is not Dangerous yet and he's done some cool things with his newly acquired skills so that get him promoted to "Novice" status ;-)

Haha  

Thank you very much for the promotion @Tim Curtis. 

Kind regards
Rock

[Dorffen]

Great progress Rock!  I for one vote for Novice status if you've written and executed scripts.

Actually, I'd vote for a new status: Tinkerer, which to me connotes someone who perhaps hasn't yet learned all the technology but keeps trying different things until "it works". A novice would stop at the first significant roadblock.

Regards,
Kent

Kent, i see your tinkerer status argument viable and will use it regarding Electronics, thanks.

Kind regards
Rock

[the_bertrum]

You ask what makes dangerous.  I think I qualified when on my first day in a new job I did something like this:

Code:

idiot@host:> pwd
/opt/bin
idiot@host:> ls /var/log
file1 file2 file3

Ah that's all garbage I thought, next thing:

Code:

idiot@host:> rm -rf

Oh dear....

[TheOldPresbyope]

You ask what makes dangerous.  I think I qualified when on my first day in a new job I did something like this:

Code:

idiot@host:> pwd
/opt/bin
idiot@host:> ls /var/log
file1 file2 file3

Ah that's all garbage I thought, next thing:

Code:

idiot@host:> rm -rf

Oh dear....

Oops. You'd have to earn a top of attaboys to make up for that one if it was a shared system 


If it was a solo system you might get away with claiming a corrupt file system forced you to reformat the disk. That wasn't an uncommon event in the good old days.

Regards,
Kent

[the_bertrum]

You ask what makes dangerous.  I think I qualified when on my first day in a new job I did something like this:

Code:

idiot@host:> pwd
/opt/bin
idiot@host:> ls /var/log
file1 file2 file3

Ah that's all garbage I thought, next thing:

Code:

idiot@host:> rm -rf

Oh dear....

Oops. You'd have to earn a top of attaboys to make up for that one if it was a shared system 


If it was a solo system you might get away with claiming a corrupt file system forced you to reformat the disk. That wasn't an uncommon event in the good old days.

Regards,
Kent

Thankfully it was a cluster, so I managed to copy it back from another node...