Everything is a people problem - even code review. SWE who choose to not grow (by refusing to learn) are going to create awful culture.

If you find this, please let me know.

Not necessarily. The market determines the price. The company may be overpriced (according to the market) if no one wants to buy it.

It's the truth.

While I was working at Earthlink in 1999, they had a similar clause and I had a similar thought.

Although not around a sex tape, I though about a computer virus released from my Earthlink corporate email account. If I sent it out the virus technically belonged to Earthlink and not me. However, after talking to a lawyer about it years later, he explained there is ways the corporation could get out of the clause.

Awesome. Two requests:

1. No sound. It's distracting. 2. Support of markdown?

I should be more clear. The scary thing is having malicious sites exploit the functionality. URI overflow attacks and Gifar attacks can be exploited at the website level. Exposing this functionality to the developers is unnecessary. If a developer wants to run as a native application, then they should. Not run as a chrome plugin pretending to be a native application.

In other news, water is wet.

I found these two passages interesting:

"The best programmers are always self-motivated: just give them opportunity to rock and stay out of the way."

and

"Programmers also complain a lot and can be incredibly lazy which is a good thing as it forces them to find ways to make things easier."

Self motivation needs to be greater than laziness. :)

Laziness is the motivation :)

I've always felt "laziness" in programmers is often "I don't want to do this tedious crappy task, I'm going to do fuck all until an elegant solution pops into my head at which point I'll at least partially automate it"

Or at least it does with me.

I know that feeling. So often, especially when things are busy or deadlines are tight, I feel bad for wasting time surfing the internet or slowly tinkering on some unimportant task no one cares about. The big job is getting no attention. "The programming" is just gone, I'm hanging around killing time.

And then something flips and you get that flash of inspiration; and you dig into the program as fast as you can. In the end, you come out with a little piece of code that's relatively clean and maybe extensible and it works.

And you know... you did it... that's why you're here. Moments like that keep you going and boil your blood if you're in the world of TPS reports and their ilk.

"An engineer is someone who will expend as much effort as necessary to do as little work as possible."