21–30 of 39 posts
MySQL: You want answers? htop: I think I'm entitled. MySQL: You want answers? htop: I want the truth! MySQL: You can't handle the truth! Son, we live in a world that has data, and those data have to be queried by processes that takes load. Who's gonna do it? You? You, Lieutenant htop? I have a greater responsibility than you can possibly fathom. You weep for 4 cores and you curse the Queries. You have that luxury. Yo…
MySQL: You want answers? htop: I think I'm entitled. MySQL: You want answers? htop: I want the truth! MySQL: You can't handle the truth! Son, we live in a world that has data, and those data have to be queried by processes that takes load. Who's gonna do it? You? You, Lieutenant htop? I have a greater responsibility than you can possibly fathom. You weep for 4 cores and you curse the Queries. You have that luxury. Yo…
Loved it! Absoolutely hilarious!
(spoiler alert) - https://www.youtube.com/watch?v=9FnO3igOkOk
Sometimes it's difficult to be objective when you write your own, maybe it would be good to have a friend or associate proofread your piece before you publish to get more objectivity.
It's rather obvious to the reader you think a lot of yourself from the 2 phrases below:
. . . as a highly trained academic researcher . . . .
. . . when I’m not producing incredible scientific breakthroughs, . . .
Usually, these are the kinds of comments it's a bit safer/less appearing boastful, for other people to write about you - - not for you to write these comments about your self.
I would suggest there are a sizeable number of comp sci. folks, perhaps even some racist zombies out there who will read your piece that are are quite aware that the tech industry places what they consider an "annoying bias" on hiring women and minorities with little or no regard for skillset/ability just so they can "look good" to the Feds and the liberal media - - - and who publish stories that the Facebooks and the Googles of our world are dominated by male WASP employees - - - - and that somehow - - - for some reason - - - they should be ashamed of that.
In other words, you don't want to attract the wrong kind of attention by appearing to be boasting about your abilities to a world which is overwhelmingly dominated by male WASPs for a reason, and likely will be for the foreseeable future.
Just my 2 cents.
Regards,
A note to James: Sometimes it's difficult to be objective when you write your own, maybe it would be good to have a friend or associate proofread your piece before you publish to get more objectivity. It's rather obvious to the reader you think a lot of yourself from the 2 phrases below: . . . as a highly trained academic researcher . . . . . . . when I’m not producing incredible scientific breakthroughs, . . . Usual…
A note to James: Sometimes it's difficult to be objective when you write your own, maybe it would be good to have a friend or associate proofread your piece before you publish to get more objectivity. It's rather obvious to the reader you think a lot of yourself from the 2 phrases below: . . . as a highly trained academic researcher . . . . . . . when I’m not producing incredible scientific breakthroughs, . . . Usual…
Mickens has some great material. He gave a talk at Monitorama a few years ago that's one of my favourites: https://vimeo.com/95066828 The article paints the plight of systems programmers in a hilarious way. I think programmer humour is rarely this well written, although a recent piece comes to mind by aphyr: https://aphyr.com/posts/340-acing-the-technical-interview
I was impressed until about this: As a systems hacker, you must be prepared to do savage things, unspeakable things, to kill runaway threads with your bare hands, to write directly to network ports using telnet and an old copy of an RFC that you found in the Vatican. So if I can use netcat and ethereal, I'm ready for the zombie apocalypse? I can sleep better then. :-P
Mickens has some great material. He gave a talk at Monitorama a few years ago that's one of my favourites: https://vimeo.com/95066828 The article paints the plight of systems programmers in a hilarious way. I think programmer humour is rarely this well written, although a recent piece comes to mind by aphyr: https://aphyr.com/posts/340-acing-the-technical-interview
Mickens is my favorite. His piece about theoretical vs practical security in tech is awesome.
My first job in California started out with two 6-foot stacks of octal dumps of operating system crashes, for a mainframe OS that was running 1-2 hours between crashes. I worked through those slowly, with colored pencils and highlighting markers, figuring out what had gone wrong, then putting a fix into the OS, in assembler. Gradually the stacks got shorter and the time between crashes increased. When I left that job, we were going a month between crashes.
Then I changed jobs to work on operating system design and proof of correctness.
This is why I'm so negative on unsafe code in Rust. Memory safety is essential. There are programmers who think they are so good that they don't need bounds checking. They are wrong. The most recent CERT advisory of a security hole for a buffer overflow was 8 days ago.[http://www.kb.cert.org/vuls/id/214283]
Earlier quoted context omitted.
Mickens is my favorite. His piece about theoretical vs practical security in tech is awesome.
Link?