Tactic

And yet you can find all the latest episodes for free from many sources via bittorrent.

When enough people find piracy convenient enough to use as their full-time solution the market will evolve a reasonable monetized solution. Until then there is not enough incentive for the content producers.

Sad panda will stay sad for some time.

It is called an opportunity cost.

The employee/employer relationship is a business relationship. As such, think of yourself like a business. Sometimes you have to spend money (time/effort) to make money (paycheck).

To view it any other way seems entitled to me.

Not a big deal because the real use case is a user that doesn't want someone else (say parents or SO) to come along later and find the pictures.

Tangential to the topic, but I can recommend Tixati as a new "I need a small, efficient, unbloated (with additional software) and free torrent client" alternative to what uTorrent has become.

He isn't advising you don't need to lock your house because the locks are insecure. He's just pointing out that you probably shouldn't lose sleep over if someone can break in or not, especially when windows are easily broken.

That is a common concern and as such easily avoided.

Many homeschoolers get together for lessons, field trips and just socializing for this exact reason. They are also generally active in assuring their children have a social network of other children.

From personal experience I think the only thing it lacked for my daughter was teaching her not the social aspect of school but how to navigate authoritarian hierarchies. I am not convinced this is a bad thing.

I wish more sites would use a validation email. I get a good number of emails for people that have my (real) name but use my email address on gmail (since I have the same name) to sign up when they don't want to recieve emails from the site. Thus I get to enjoy them. When the site sends a validation email I just ignore it and never hear from them again.

As a side note, be cautious of using such a tactic. I have recieved their logins, CC and Physcial Address information because of this.

And hence the issue. Those that take advantage of a system never feel that they are.

Look at why it is provided. It's not a prize or a bonus. It is to keep you happy and productive while you work. The company feels that is worth the cost. Where in there does someone drinking soda on the way home figure? It doesn't.

If I were the person providing the free soda I would be upset at being taken advantage of.

Finishing your soda on the way home, sure. Grabbing an unopened one and walking out the door... that seems to me to be a good place to draw a line.

So now I can have a UI with ads overlaid on my TV ads? Fantastic!

Except with an array you can change things programmatically on the fly. Or have it setup in a configuration file or database table. Very useful.

There are adapters and such to use the XBox controller with the PS3 as well as look-alikes.

Form follows function. That said, I find it best to divide the tiers and document where they meet ahead of time. Then develop each tier independently to the spec. That makes it so much easier when it is time to maintain/iterate/swap out one of the parts.

Front end first, back end first... it doesn't really matter. You shouldn't be designing one to the other. Function first :)

I moved from front end work to back end work for some very simple reasons a) in general it pays better and related b) front end guys are far move common so the backend has less competition.

Work, as I have become older, is more and more just a business proposition.

Plus it puts me further away from those guys that think HTML/CSS is programming. :)

Expecting services to continue forever is like expecting that you will never be laid off.

It is a rude awakening when it happens, but it should hardly be surprising for anyone that has been around for a while.

I ran a site (stomped.com) in the late '90s and we did this. We were serving up news items to millions of unique visitors a month and hitting the DB on each page hit. Rather than try to implement a bunch of caching methods we went with generated HTML files. Given how often content changed (a few times an hour at most) it seemed a waste to generate 10s of thousands of db/cache hits when things rarely changed. Simple. Stable.