blue paints/colors tend to be the worst culprits.
Been writing code for a good while. Will probably continue writing code for a while longer.
blue paints/colors tend to be the worst culprits.
50,000? thems rookie numbers.
only way to be sure…
not so much for understanding but, fight club is a different movie the second time around.
do it often. you may end up with 150 conflicts to have to wade through.
fond memories for BeOS
unless you inherit a large base written by someone who is bad at it where their approach seemed to be to write new bad rules in attempt to cover up previous bad rules and so on. we all know how supportive employers are at addressing technical debt. (site redesign cant come soon enough)
I’ve had pretty good luck with radeon-profile. I’ll have to give this one a go
tarsnap makes use of S3. does a decent deduplication job as well
that game brought hours of fun back in the days of yore. that fuckin smiley face tho…
“your failed business model is not my problem”
eterm because I’m old skool. now get off my lawn.
“algorithm” is a little too fine grained for what you describe. “software design patterns” is probably what you are looking for.
unfortunately, not all projects call out the patterns they employ.
PICNIC. problem in chair, not in computer.
just tell them there is a black man at the moment of theft, they will get on it lickety split!
making them better would mean more work, stress and ill conceived requirements for the programmers. I’m more in favor of marketing thrashing about on their own.