yogo

It's not really crazy, it comes down to what data you have from upstream. It's not like you are swiping a card and have access to the magstripe data. With AVS it's only Amex that bothers with the cardholder's name.

Then maybe jack of some trades, master of a handful or in the process of mastering a handful? If you take front and back end development as an example, you have many different ways to go about things on both sides. However, in terms of simply building software you can probably limit your focus for either side and deliver effective solutions. After all, the end user usually just cares about accomplishing what they need to, right?

Hopefully it stays around and isn't axed like Arch was :)

And for you downvoting fucks, wake up and smell what real world competition is like.

Uber has balls. No matter where you stand you've gotta love that.

I haven't had any problems with import and compositing. My setup is very basic though: xcompmgr -c

This is also what I use on a daily basis. One case where it falls through is where you are trying to capture a screenshot for something that has a certain UI state, like a mouseover. For those cases you can have PrintScreen set to capture your desktop and save it to a file. In OpenBox you would set up a key binding for Print that executes: import -window root filename.png

That should be a good thing, understanding what you are about to fix should be most important. I don't think rushed fixes pan out too well in the real world.

You can just sell it off on a site like judgmentmarketplace.com. sometimes trying to collect could end up costing you more.

Same username as HN, no Facebook account.

What does one have to do with the other? If you can afford it and it's something you need then you buy it. It's only innovation if there is some significant improvement.