Noob developer or seasoned vet?

Content Re: Regression - prockmsg does not ... From Jukka Ollila Greg KH Jukka Ollila Alan Cox Linus Torvalds Tallen Allie. Sent On Jul 6, 2012 10:45 am Jul 6, 2012 10:54 am Jul 6, 2012 11:45 am Jul 6, 2012 12:34 pm Jul 6, 2012 1:30 pm 1ul a 3019 2.05 nm Subject: Re: Regression - prockmsg does not (always) block for 1-byte reads From: Linus Torvalds (torvlinux-foundation.org) Date: Jul 6, 2012 1:30:01 pm List: org. kernel. vger.linux-kernel Kay, this needs to be fixed. Suggested fix: just use the 'seg printf0' interfaces, which do the proper buffering, and allow any size reads of various packetized data. Of course, I'd also suggest that whoever was the genius who thought it was a good idea to read things ONE FCKING BYTE AT A TIME with system calls for each byte should be retroactively aborted. Who the fck does idiotic things like that? How did they noty die as babies, considering that they were likely too stupid to find a tit to suck on? Linus

The six horsemen of desperation in debugging: First panel: Drowning in log files like an archaeological dig through digital garbage. "Maybe the answer is in line 4,372!" Second panel: Setting breakpoints with the strategic planning of a toddler playing Jenga. "Let's stop at EVERY. SINGLE. LINE." Third panel: Pair programming with a rubber duck that judges your life choices harder than your parents ever did. "This code is quacked up" is the understatement of the century. Fourth panel: StackOverflow - where you copy-paste solutions with the blind faith of someone following a cake recipe written in hieroglyphics. "It worked for that guy from 2011, surely nothing has changed!" Fifth panel: Making a pact with the devil because selling your soul seems reasonable when you've been debugging for 16 straight hours. "Eternal damnation? Still better than this bug." Final panel: Rebranding the bug as a "feature" - the intellectual equivalent of sweeping dirt under a rug and calling it interior design. Pure genius.

Content GOD, WHY IS QUANTUM MECHANICS SO WEIRD? IN ORDER TO MAKE A RAINBOW, YOU HAVE TO 'BREAK" LIGHT INTO WAVELENGTHS WHEN IT ENCOUNTERS A NEW MEDIUM. AFTER THE FLOOD, I WANTED TO MAKE A RAINBOW FOR HIM. IT'S NOAHS FAULT. WELL, IT TURNS OUT THAT IF YOU WANT THAT, YOU HAVE TO TWIDDLE WITH A BUNCH OF ASPECTS OF THE UNIVERSE, ADDING WEIRD STUFF LIKE PHOTON SUPERPOSITION AND PROBABILITY AMPLITUDES. BUT, EVERY TIME I FIXED ONE THING, SOMETHING ELSE SEEMED TO BREAK. SO. I KEPT CHANGING THINGS AND CHANGING THINGS AND THE SYSTEM GOT MORE AND MORE HACKY AS TIME WENT ON. FINALLY, IT GOT SO FUNDAMENTALLY UGLY, I ADDED UNCERTAINTY SO NOBODY COULDI LOOK TOO CLOSE THAT EXPLAINS ALL OF PHYSICS AND WHAT YOU SAID TO NOAH AFTER THE FLOOD. EXACTLY. 4,000 YEARS EARLIER NEVER AGAIN. smbc-comics.com ProarammerHumor.io

Content Raycasthit hit; Quick Fix... Racist it(tr Vect

THE ABSOLUTE DRAMA of nighttime coding! Look at these nocturnal code warriors riding the rollercoaster of insanity while daytime programmers scream in horror! Midnight coders are literally TRANSFORMING into code-drunk skeletons fueled by nothing but energy drinks and desperation! Meanwhile, the 9-to-5 normies are clutching their ergonomic keyboards in absolute terror at what their codebase will look like tomorrow morning! That pull request review is going to be a NIGHTMARE of "why did you commit this at 3:47 AM?!" The duality of programmer existence has never been so spectacularly represented by a haunted rollercoaster metaphor!

Content 8:19 AM builds seem to be failing https:jenkins due to this test https:githubl lest.lava I believe its failing due to daylight savings ending. The test assumes a day 86400 seconds, but that is not true for yesterday? LOL 3 Proaran