HN user

thisGuysAccount

29 karma
Posts0
Comments58
View on HN
No posts found.

My running form improved greatly, and quickly, when I ran barefoot (or wear 5 finger shoes). Doesn't have to be far, could be a few hundred meters as a part of a warmup. If you're overstriding, slamming your forefeet or heels, it'll hurt. When it stops hurting, you're running with good form.

Finasteride, from what I've read, can have side effects that are worse than the hairloss. I'll take a receding hairline over ED.

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.

I clicked it at work. We're in a temporary space with a few dozen 3 and 4 person offices, all have floor-to-ceiling walls and doors. The acoustics are pretty good. Even the loud talkers are tolerable, for the most part.

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.

Yow, bit by the English as a second language bug.

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.

uh... "most physically fit males - especially ones of Brown complexion - are armed to cause serious physical harm"

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.

Even as recently as mass immigration to America. People who got on the boats across the Atlantic weren't coming back, and communication was slow.

Some people just want to go.

That's part of why it's worth $20.

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?

There are three types of "good architectural choices"

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?"

You sound average-sized, if you can confidently say shirts are standard in size. I know a lot of guys who have a hard time finding shirts 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.

I might be missing what you're not following, but here's a quick explanation (and a reason why it's not a concern)

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.

Everyone's talking about Terry like he's not able to see this...

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.

There might well not be a "managerial archetype".

Each company will have desired traits in their managers, whether they go for the servant leader or the authoritarian delegator, their desired traits will limit who they view as suitable for managerial positions. There will be "manager types," and to people who have worked for that company for 10, 15, 20 years, that is the "manager type" for all companies, in their view.

There are also some traits that _are_ required for managerial work, certainly not enough to define a personality type, but without them, people could not function in a delegating, influencing, or persuading position. They're the traits that allow people to perform those functions.

I'd certainly be willing to concede the point that those aren't even personality traits, but skillful applications of personality that could be developed.

TLDR: I agree with you, but there's enough nuance in what "types" could mean that you're looking at a discussion about very subtle things that many people might not consider at first.

Death threats, death wishes... it's over an init daemon on a software project.

I can't imagine "Someone wants to paint the front door RED?! They should die." happening under any circumstances. It's concerning to me, on many levels, that this is happening over systemd, regardless of the technical benefits or issues.

This comment might not float to the top of the thread, but I'll post it anyways.

When dentistry started out, there likely were more than a few dentists who learned this way. There are still, on occasion, unlicensed dentists found practicing dentistry with decently successful businesses.

Software development doesn't have the Software Development Association protecting the practice like dentistry and medicine do, for their respective associations.

I've been thinking about pasting this news into my Facebook. Three times, erased each time.

"Guy gets multiple death threats because of the program he wants to start his computer is different from another program other people want to start their computers."

This isn't a hilarious nerd fight. This is some really misguided people who don't know how to communicate.

Right, in the case of the roomba and the vending machine, the human decision is 'turn on the roomba' and 'push the vending machine button'

The assumption of the roomba creator is that 'anything on the floor can be vacuumed, living or otherwise.' The moral choice, with regards to the life impacted by the roomba, is to disregard the potential value of the life. It's all debris.

The assumption with the vending machine is similar. The only value considered by the creator is in the transaction involving the operator's money and producing the material the operator wants. Anything else is considered without moral value.

Morality can be as much about the lack of value placed on something as it is about the value placed on something. I'm talking about moral agency, the implications of operating a device, and not about how a robot "feels" about doing something, for the lack of more accurate word.

It's a question of morality in a philosophical sense, not as an application of science or engineering.

The roomba is capable of killing. Whether the operator is aware of this or not, when they use the roomba to clean their floor, they're ceding their moral agency to the device and to its creators.

The logic can be abstracted from the roomba to any other device. This creates the need for device operators, whatever the device, to examine the potential outcomes of device operation and potential assumptions and motivations of the device's creators.

Failure to examine the assumptions and motivations is the same as ceding moral agency, deciding not to decide and throwing hands in the air and saying "well, didn't see that coming" when the creator's assumptions and motivations play out in a way contrary to the operator's morality.

So, yeah, it's about a roomba killing a bug, or a vending machine spilling a soda. It's also about a facial recognition device not noticing a black guy on a black background, or a drone killing a dog because it's barking aggressively.

Gas stations are consumers of the products of oil refineries and oil wells. HP is a consumer of Intel's chips.

Free markets reward business to business sales very well.

I just spent the better part of a month cleaning up some CI issues. By the time I go to bed tonight, I hope to have a CI process completed for two platform implementations of an application that's been under development for some time. Part of the process is static analysis and linting.

I've seen the static analysis and lint results already. Not pretty, but we can clear most of it up as we develop new features.

Definitely a process that anything beyond a trivial app needs in place.

We're kind of talking about two different, but very similar, topics.

One is that Indian work culture is long hours, 6 day weeks, get it done and do it inexpensively. This is true, it's cultural. Some of their practices prefer manual and repetitive work over a style which requires a drawn out preparation involving planning and automation. If you're paying $15/hr for highly skilled labor, that can make sense.

The other is racial, the belief that can become a part of that work culture, where people who do not work like that are inferior workers. Given the rarity of Indian work culture and cultures similar to it, it's still cultural, but more racially limited. Someone of Asian descent, used to working in sweatshop style conditions, sees someone who doesn't look like they're used to it, and they assume the non Asian is an inferior worker, then it's racial. It's anecdotal, but I've been on the receiving end of both unspoken and spoken racism, veiled as cultural differences, about how North Americans are lazy and cheat their employers.

That said, I'm typing this out well aware of how this looks. It's important to note that I know not all Indians are like that. It's just a hard habit for people who spent 5, 10 years working long hours like that to break, and it's not always easy for them to look at a worker creating equivalent output with different methods in less time and say "yeah, that person works as hard as I do."

It's true. It's been my experience that Indians, the few hundred I've worked with, are willing to put in long hours. Many of which were spent playing ping pong, talking, getting coffees. They also were working, but, the long hours in the office weren't all work.

They also held the belief that they were harder workers than non-Indians, and preferred greatly to talk in native languages, likely unintentionally excluding non-Indians.

At some level, race is a factor.

the existing model has been to subsidize newspaper sales with advertising for a very long time. This same model carried forward through radio and television.

The alternative is a pay-per-view service, or subscribing to wires. I haven't done any research into the viability of that type of service, but it is a paradigm shift.

There are things in the world worth more than getting an idea out there. Knowing that the project(s) I've shelved has/have likely kept a few people alive is worth more than being able to say I stuck it to the man.