#shittyprogrammingtips search results

Always code when you really have to pee. A full bladder makes you work faster, and therefore more efficiently! #shittyprogrammingtips


List bugs as features on changelists. #shittyprogrammingtips


Don't use transactions when modifying production tables, they just slow down your query. #ShittyProgrammingTips


Do a pack of caffeine powder before writing code to push to production. Chances you'll die before anything breaks. #shittyprogrammingtips


Streams are hard to work with, just load the contents of a file directly into memory! #shittyprogrammingtips


Always test against production. The added impact of failure will make you work better. #shittyprogrammingtips


Write bad code, so you have something to do when you go back to refactor later. #shittyprogrammingtips


If your make file can't find the library headers, just add symbolic links #shittyprogrammingtips


why the fish would you use an existing framework for your next project? roll your own. #shittyprogrammingtips #javascript


Don't commit too often to SVN. If you do, there'd be far too many revisions to look through when you need to revert! #shittyprogrammingtips


start naming variables based on family member names. you'll remember them well #shittyprogrammingtips


Don't ever fully empty your bladder. Having to pee makes you code at least 80% faster. #shittyprogrammingtips


#shittyprogrammingtips I read this shit everywhere, everyday(2/2)


Don't worry about naming conventions, just call it whatever. #shittyprogrammingtips


always query for a dom element when using @jquery . never cache. because who does that? #shittyprogrammingtips


Loud #Music + Lot of #Alcohol + @Windows = Best Development Environment Setup Ever. #shittyprogrammingtips


If your make file can't find the library headers, just add symbolic links #shittyprogrammingtips


Don't worry about naming conventions, just call it whatever. #shittyprogrammingtips


Loud #Music + Lot of #Alcohol + @Windows = Best Development Environment Setup Ever. #shittyprogrammingtips


always query for a dom element when using @jquery . never cache. because who does that? #shittyprogrammingtips


why the fish would you use an existing framework for your next project? roll your own. #shittyprogrammingtips #javascript


#shittyprogrammingtips I read this shit everywhere, everyday(2/2)


start naming variables based on family member names. you'll remember them well #shittyprogrammingtips


List bugs as features on changelists. #shittyprogrammingtips


Do a pack of caffeine powder before writing code to push to production. Chances you'll die before anything breaks. #shittyprogrammingtips


Don't use transactions when modifying production tables, they just slow down your query. #ShittyProgrammingTips


Always test against production. The added impact of failure will make you work better. #shittyprogrammingtips


Always code when you really have to pee. A full bladder makes you work faster, and therefore more efficiently! #shittyprogrammingtips


Streams are hard to work with, just load the contents of a file directly into memory! #shittyprogrammingtips


Don't commit too often to SVN. If you do, there'd be far too many revisions to look through when you need to revert! #shittyprogrammingtips


Write bad code, so you have something to do when you go back to refactor later. #shittyprogrammingtips


Don't ever fully empty your bladder. Having to pee makes you code at least 80% faster. #shittyprogrammingtips


No results for "#shittyprogrammingtips"
No results for "#shittyprogrammingtips"
Loading...

Something went wrong.


Something went wrong.


United States Trends