Minimum Wage just went up to $11.50 in Washington State. The price of milk is $2.68 a Gallon.

[heydaralon]

I know it's morning for the most of you, so what you drinking?

Roomates made some coffee before they went to work, so personally I don't know, but it's good. They like the flavored stuff but hey free coffee is free coffee.

Aside from mooching off the government and taxpayer's tit, you are mooching off your roommates too? Man you are one sick fuck.

[jediuser598]

I know it's morning for the most of you, so what you drinking?

Roomates made some coffee before they went to work, so personally I don't know, but it's good. They like the flavored stuff but hey free coffee is free coffee.

Aside from mooching off the government and taxpayer's tit, you are mooching off your roommates too? Man you are one sick fuck.

How's that?

[Speaker to Animals]

Coke Zero here, to wash down the yohimbe, green tea extract, caffeine pills, and beta alanine I take before I do my fasted run.

[BjornP]

Many of you got no respect for the common man out there breaking his back to make this whole thing possible. You're all back there like "sucker! Work harder not smarter! Retard!" If you could see my face you'd get the expression, "seriously?" Pissing on the common man because you're so divorced from it.

Does this "common man" you speak of try to advance his skillsets through certificates that make him a more specialized, adept, hard-working backbreaking common man?

I'm not saying respect shouldn't be afforded to folks who are upwardly mobile, but shitting on people who work hard, put in their days? I don't see any sense in that. Hard work is hard work regardless. Worthy of respect.

Are you one of those people who don't regard work that does not require heavy lifting as "easy" work, by any chance? I put value in work ethic, not what the work is. Okee's talking about working smart, and you think that that's in opposition to working "hard". Maybe "work hard" is a term that only applies to physical work in the English language, I don't know. I associate it with a person's work effort. Meaning, I don't see any opposition between working hard and working smart. Nevermind that the process of understanding how to work smart, can also involve hard work.

[Speaker to Animals]

In the middle class of America, especially among engineers, there is a kind of often unstated virtue in laziness. Engineers especially tend to frown upon just toiling away at something. It's better to write a small bit of code that generates a lot of code, for example, than to just sit there and robotically write repetitive code. If I am managing some new hires, and I see them doing that, I am supposed to stop them and show them how to do it smarter.

This value is opposed to blue collar working class values that favor the amount of physical effort involved. I am not sure if this value is shared outside of STEM, however.

Laziness is often called the first virtue of programming.

http://threevirtues.com/

[BjornP]

In the middle class of America, especially among engineers, there is a kind of often unstated virtue in laziness. Engineers especially tend to frown upon just toiling away at something. It's better to write a small bit of code that generates a lot of code, for example, than to just sit there and robotically write repetitive code. If I am managing some new hires, and I see them doing that, I am supposed to stop them and show them how to do it smarter.

This value is opposed to blue collar working class values that favor the amount of physical effort involved. I am not sure if this value is shared outside of STEM, however.

Laziness is often called the first virtue of programming.

http://threevirtues.com/

I wouldn't really label that sort of process laziness, tbh. That's using knowledge/experience you've accumulated throughout your education/career, and using it getting your job most efficiently, and hopefully thoroughly.

I have a programmer brother who does fit that bill. He's still what I'd call a hard worker, based simply on how much he's sacrificed for his company - which he is now on the board of directors on. But I can't rule out that what he spent most of his time on was management and leading various projects for their clients, rather than programming.

[Speaker to Animals]

No, really. Software engineers are, as a general rule, quite lazy.

I would not be at all surprised if Hash's prescient for wanting whip people into more productivity comes from his experience at managing software engineers.

[Zlaxer]

In the middle class of America, especially among engineers, there is a kind of often unstated virtue in laziness. Engineers especially tend to frown upon just toiling away at something. It's better to write a small bit of code that generates a lot of code, for example, than to just sit there and robotically write repetitive code. If I am managing some new hires, and I see them doing that, I am supposed to stop them and show them how to do it smarter.

This value is opposed to blue collar working class values that favor the amount of physical effort involved. I am not sure if this value is shared outside of STEM, however.

Laziness is often called the first virtue of programming.

http://threevirtues.com/

Wait - so if I replace a lengthy case statement with recursion I'm lazy? WTF?

[jediuser598]

Does this "common man" you speak of try to advance his skillsets through certificates that make him a more specialized, adept, hard-working backbreaking common man?

I'm not saying respect shouldn't be afforded to folks who are upwardly mobile, but shitting on people who work hard, put in their days? I don't see any sense in that. Hard work is hard work regardless. Worthy of respect.

Are you one of those people who don't regard work that does not require heavy lifting as "easy" work, by any chance? I put value in work ethic, not what the work is. Okee's talking about working smart, and you think that that's in opposition to working "hard". Maybe "work hard" is a term that only applies to physical work in the English language, I don't know. I associate it with a person's work effort. Meaning, I don't see any opposition between working hard and working smart. Nevermind that the process of understanding how to work smart, can also involve hard work.

Who deserves more respect? The woman who is in her 50's, 60's,70's working at a job she hates, but still putting in the time, but she's also working hard and letting no one leave her behind. She's over there leading the pack. Or the 20 year old who is working hard as a paralegal? In a job he loves.

One situation certainly hurts more.

I guess you could say the older woman, on a day to day basis, is lifting more weight, encountering more resistance, but both would be demonstrating solid work ethic which should be applauded, but the paralegal has the better deal, is there any real denying of that? But should that distinction really be made? Why not just respect the work ethic? As the paralegal looks at the woman and the other way around? Just respect the work ethic. But in our current culture? The paralegal gets respect, and the woman does not. That's what bothers me.

Bjorn, I have Okee blocked. I'll display post on his stuff sometimes just to see if he's continuing his belligerency towards me, roll my eyes then continue on about my day. If you notice, all of his posts towards me are always negative, attempting to bait me into responding to his nonsense. Not worth it.

[jediuser598]

In the middle class of America, especially among engineers, there is a kind of often unstated virtue in laziness. Engineers especially tend to frown upon just toiling away at something. It's better to write a small bit of code that generates a lot of code, for example, than to just sit there and robotically write repetitive code. If I am managing some new hires, and I see them doing that, I am supposed to stop them and show them how to do it smarter.

This value is opposed to blue collar working class values that favor the amount of physical effort involved. I am not sure if this value is shared outside of STEM, however.

Laziness is often called the first virtue of programming.

http://threevirtues.com/

Damn.

I remember a fella he was talking about how easy his job was. Said he had to do data input at his job, but instead of doing it manually he wrote a bit of code and all of his job was done in 10 seconds compared to 8 hours. So he'd clock in, run the code, job is done he'd do nothing else the rest of the day. Oh, he certainly look like he was working, but that was his day. He told me, they hired data entry, not a coder. He never told his employer that's what's happening, why would he ever tell his employer, he'd be out of a job then.