A tweet-sized debugger for visualizing your CSS layouts. Outlines every DOM element on your page a random (valid) CSS hex color.
One-line version to paste in your DevTools
Use $$
if your browser aliases it:
~ 108 byte version
Finally this time, I'm sold on tmux after I used tmuxinator to configure tmux layouts. The default layout didn't work for me, I wanted more control on the split panes. Here's how you can fine tune your tmux layout:
~/.tmux.conf
-> set -g mouse-resize-pane on
tmux list-windows
to list active tmux windows and their layouts(I wrote a bit about why Emacs and Vim on my blog and thought it might be nice to give some starting point for people that want to try it.)
If you just want to play around with Emacs & Evil mode do the following:
mkdir ~/.emacs.d/
init.el
into ~/.emacs.d/
(by @andrestaltz)
If you prefer to watch video tutorials with live-coding, then check out this series I recorded with the same contents as in this article: Egghead.io - Introduction to Reactive Programming.
Hey All, | |
I am P.B.Surya.Subhash, a 17 Year coder,hacker and a student. | |
Recently I happen to see so many posts regarding this " Google XSS Challenge " and i was fortunate enough to complete them.. | |
These are the solutions for the challenges ;) | |
############################################################################## | |
Level 1: Hello, world of XSS | |
https://xss-game.appspot.com/level1/frame | |
query=<script>alert('xss')</script> |
THIS GIST WAS MOVED TO TERMSTANDARD/COLORS
REPOSITORY.
PLEASE ASK YOUR QUESTIONS OR ADD ANY SUGGESTIONS AS A REPOSITORY ISSUES OR PULL REQUESTS INSTEAD!
RDBMS-based job queues have been criticized recently for being unable to handle heavy loads. And they deserve it, to some extent, because the queries used to safely lock a job have been pretty hairy. SELECT FOR UPDATE followed by an UPDATE works fine at first, but then you add more workers, and each is trying to SELECT FOR UPDATE the same row (and maybe throwing NOWAIT in there, then catching the errors and retrying), and things slow down.
On top of that, they have to actually update the row to mark it as locked, so the rest of your workers are sitting there waiting while one of them propagates its lock to disk (and the disks of however many servers you're replicating to). QueueClassic got some mileage out of the novel idea of randomly picking a row near the front of the queue to lock, but I can't still seem to get more than an an extra few hundred jobs per second out of it under heavy load.
So, many developers have started going straight t
/////////////////////////////////////////////////////////////////////////////////////////// | |
#pragma mark - Warn if we KVO a weak property | |
// Doesn't support key paths. | |
static BOOL PSPDFIsWeakProperty(id object, NSString *keyPath) { | |
objc_property_t property = class_getProperty([object class], keyPath.UTF8String); | |
if (property) { | |
// https://developer.apple.com/library/mac/documentation/cocoa/conceptual/objcruntimeguide/articles/ocrtpropertyintrospection.html | |
const char *attributes = property_getAttributes(property); | |
return attributes && strstr(attributes, ",W"); |
Rule 0: Do not make a framework.
Ask yourself if you should be making a framework given that you are not in the business of making frameworks. Believe it or not, most of us have the urge to solve problems completely and in the general case as our first inclination, but getting things done requires not doing so almost all of the time.
Rule 1: Do not have dependencies on other 3rd party frameworks.
Frameworks should be modular and standalone. They should require nothing but the standard system libraries in order to run. If the framework relies on other functionality, it should encompass it entirely. If it cannot, it probably violates Rule 3.
Rule 2: Use a non-viral open-source license like MIT or Apache, NOT GPL.