Do you develop on GitHub? You can keep using GitHub but automatically sync your GitHub releases to SourceForge quickly and easily with this tool so your projects have a backup location, and get your project in front of SourceForge's nearly 20 million monthly users. It takes less than a minute. Get new users downloading your project releases today!
In my experience, all the people who studied on their own and knew what they wanted to do and before they entered college became distracted and depressed. The filler classes just suck up time, motivation, and money. Then they'd just feel worse and worse for not focusing on their real studies
I delayed my Freshman year until I was 22 just so I could get my parents off my FAFSA only to have those pig fuckers raise the age to 24 on my 21st birthday.
This shit right here is one of the big ways financial aid sucks. Are you a 22 year old who has been living on your own for years? Lulz, your parents are totally going to give you tens of thousands of dollars suddenly to go to school. No need to give you any money.
If there were a good vocational school in my area for finance I'd drop out today.
But that isn't going to happen, so I'll just continue taking bullshit classes to get a piece of paper that says I can start my real education(hopefully) in my last 2 years of college.
Posted
by
samzenpus
from the won't-somebody-please-think-of-the-children? dept.
First time accepted submitter ron-l-j writes "The last few months a digital inheritance idea has been floating around in my head, and I am sure the thought has crossed your mind as well. With Google talking about the inactive account program it made me wonder, how do I make sure my children get my iTunes, and amazon movies? I have plenty of mp4 movies on my server that will just set itself to admin with no password after I do not log in within a 6 month time frame. But what about the huge amount spent on digital content every year? What's the best way to make sure your "digital inheritance" gets passed down?"
At 9am this morning the amendment was withdrawn, and the language of the bill changed to include that employers will be required to pay employees $500 along with any damages should they ask for their social media passwords. So no one is getting their social media passwords taken by employers. See for your self
http://apps.leg.wa.gov/billinfo/summary.aspx?year=2013&bill=5211 It's under "In the house"
http://www.tvw.org/index.php?option=com_tvwliveplayer&eventID=2013041032
If you don't believe that then watch the senate themselves withdraw the amendment and change the language of the bill
This amendment never had a chance in hell, and has been put to death.
An anonymous reader writes "A bill amendment proposed Tuesday could allow employers to ask for a worker's Facebook or other social media password during company investigations. The provision was proposed for a bill that safeguards social network passwords of workers and job applicants. The measure bars employers from asking for social media credentials during job interviews. The amendment says that an employer conducting an investigation may require or demand access to a personal account if an employee or prospective employee has allegations of work-place misconduct or giving away an employer's proprietary information. The amendment would require an investigation to ensure compliance with applicable laws or regulatory requirements."
Posted
by
Soulskill
from the not-the-best-resume-builder dept.
Esther Schindler writes "Last fall, the state of Washington passed a marijuana legalization referendum, and needed to acquire an outside consultant to run the program. 'As it normally does, the state put out a request for proposal for a consultant to run the new legal marijuana program,' writes Ron Miller. 'As word leaked out that there was an RFP open for what essentially was a "pot czar," the floodgates opened. It would be the most popular RFP in the state's history. The Liquor Control Board needed a way to process these requests quickly and cheaply.' In a typical RFP scenario, they would get maybe half a dozen responses. This one got close to 100. Miller writes about the cloud workflow required to solve the task: 'He chose these particular tools because they all had open APIs, which allowed him to mash them together easily into the solution. They were easy to use, so reviewers could learn the system with little or no training, and they were mobile, so users could access the system from any device. In particular he wanted reviewers to be able to use the system on a tablet.' I suppose this could have been written about more mundane RFPs, but I bet you'll find this more interesting than most."