thisGuysAccount
Joined 12 years ago
Joined 12 years ago
OP: Cut it short, shave it all if it's thin, get a thicker neck (serious. It's the biggest improvement you can make to your dressed appearance, in terms of muscles, and often overlooked), and you're better off than most guys with Fabio-hair.
When we had an open office... the acoustics were terrible. Conversations at a normal volume could be heard far away, conference calls were (had to be) done on speakerphone with the volume maxed out to hear. It looked great, but it was awful for everyone who didn't enjoy talking very loudly.
Hoping that the new space has head-high partitions, maybe offices for each team with floor-to-ceiling walls, a ceiling with either pockets to reduce echoes or a proper ceiling.
An office built for working with the people we work with, not being able to talk to someone 50 feet away without walking.
Yeah, that one word really changes the meaning of that phrase.
Yes, absolutely a more reasonable statement knowing that it's the way 'complexion' is similar to 'constitution' in some languages.
It's a good idea to rephrase that.
edit - yes, a lot of black athletes have lower body fat than whites, hispanics, and asians. No, they're not "especially" armed to cause serious physical harm.
Some people just want to go.
There would need to be some brand research done, checking the fitting and sizing of various brands, so you could know that "with a 31 inch waist, measured around the navel, I would fit in 30 inch Gap jeans and 32 inch Wranglers."
That trip to try on those two pairs of jeans cost you what, an hour? two hours?
The first: The ones that can be made after the original, bad ones. The second draft, which is an improvement in the first draft, in every field.
The second: His (or her) own. We all know there are developers out there who think they're the greatest thing to ever write code, and that everyone else's decisions are bad.
The third: The ones that really should have been made, in place of the ones that really shouldn't have been made. As in, "You wrote your own SQL parser using hardcoded strings and no grammar parsers?"
I mail you a list of measurements. You mail me a list of brands and styles that fit.
Shirts, jeans, sweaters, anything... they're all over the place in terms of fit.
With shirts, you've got different torso widths, lengths, arm hole sizes (I don't know the word), depths and widths of the neck hole. A slim fit, an athletic fit, a relaxed fit, will all vary from brand to brand.
With jeans, same thing.
Then you've got the fabric and stitching. I'm not sure I'd buy clothes online. Too many variables.
Correct username, correct password: takes 30ms to execute the code
Correct username, incorrect password: takes 15 ms to execute the code
Incorrect username: Takes 7 ms to execute the code.
You fuzz usernames, you get one that takes 15 ms, you know that's a valid username. You then start working the password.
Not necessary on most systems, because we're working at speeds that are measured in nanoseconds, and since we're using networks for many attacks, the delays are unpredictable and measured in (at least) milliseconds.
Not aiming this message at you, krapp, or anyone, I just realized this while reading your message that Terry's probably read through this thread a few times. Wonder what his thoughts are on the article.
Heads up, limit poker. They've solved a two player game with restricted bets.