It made me realize that I must have never really known what job you were interviewing for. I guess I just assumed it was a programming position, but your description sound more like an admin. I must have been a real slacker, even before you left. I mean, sure, things were moving quickly there at the end, but surely I'd have some idea what you were doing. :(
Of course, even now I only know what you're doing in an abstract way, without any sense of the scope or specifics. :)
I sat down to write a much more technically descriptive entry of what I do - of which daemon-killing is a somewhat small part, but figured it wouldn't be nearly as fun as writing this.
I'll probably follow up with a more detailed description of what I do later, but it's very difficult to explain what I do to most people.
Comments 7
It made me realize that I must have never really known what job you were interviewing for. I guess I just assumed it was a programming position, but your description sound more like an admin. I must have been a real slacker, even before you left. I mean, sure, things were moving quickly there at the end, but surely I'd have some idea what you were doing. :(
Of course, even now I only know what you're doing in an abstract way, without any sense of the scope or specifics. :)
Reply
I'll probably follow up with a more detailed description of what I do later, but it's very difficult to explain what I do to most people.
Reply
1) fun description
2) technical description
3) user-friendly description
Reply
Reply
kill -9 `ps -ef | awk '{print $2}'`
It'll be fun!
Disclaimer: (For those watching at home, do not try this without the expressed, written consent of the sysadmin)
Reply
Reply
Stand strong...
We mindless, ignorant users are behind you 100%.
Reply
Leave a comment