You're spreading misinformation :

That's false. I quoted the bill in a post above. It's linked to the article and classifies providers as publishers only if they promote health misinformation through a non-neutral algorithm.

Nothing in it will stop me from posting health misinformation on my page or you from viewing that health misinformation if you navigate specifically to my page. What this is trying to address is the case where Facebook shows my health misinformation to a billion users passively watching their feed.

I actually think this is a good modification of S230. Here's a copy-paste quote from the bill :

A provider of an interactive computer service shall be treated as the publisher or speaker of health misinformation that is created or developed through the interactive computer service during a covered period if the provider promotes that health misinformation through an algorithm used by the provider (or similar software functionality), except that this subparagraph shall not apply if that promotion occurs through a neutral mechanism, such as through the use of chronological functionality.

I have used two monitors, but I prefer a single widescreen monitor with 6 virtual desktops in KDE. Mind you, I program in gvim and konsole, not an IDE.

At he height of of our prosperity, the top marginal tax rate varied from about 70% to about 90%. I feel about 50% is fair, and I also support a new bracket beginning at somewhere between $500,000 to $1 million annually to which the 50% marginal rate would apply. Moreover, Social Security contributions should not be capped. Spending should then be reduced below revenues until the debt is paid off.

Thanks for your great work. I've used the "System Activity" thing for monitoring memory and CPU usage of different processes and to kill unresponsive ones. I really like the graphical display, but often resize the columns to get it just right. You should consider lack of feedback a good thing. Yours is an application that does its job well, and I have not found any bugs in it.

Compiling my code base from scratch takes long enough on real hardware.

Windows computer for Outlook and company sites that require IE; Linux computer for getting work done with gvim, g++, gdb, valgrind, find, grep, etc. I have to say it's quite nice to literally turn your back on email when you are coding. It's also nice to use the gdb/valgrind combination, but have Visual Studio as an option if I have to troubleshoot a problem with our software running on Windows.

Not that I've spent more than a day in New England, but I feel the opposite. I've lived in Florida, Iowa, British Columbia, Minnesota, Alabama, Mississippi, Pennsylvania, and currently live in Washington, DC. I've visited England, Wales, the Netherlands, France, Spain and Thailand (and the airport in Tokyo). In contrast to your experience, I have found these places to be strikingly similar. Yes, language, level of education (Mississippi ranks lowest), and level of technology in public view (Thailand astonished me on this one) vary, but in terms of culture, values, personal interaction, day to day life, for me, every place I've been is basically the same and I never once thought "this is not my home, these are not my people".

A good programmer writes clean code that can handle errors and accommodate typical spec changes without having to be completely re-written.

FTA:

No, I don't forgive them for writing obfuscated spaghetti code and leaving it for me to maintain. Also FTA:

I laughed out loud when I read this. I write in C++. It's my favorite language. But I can't stand these Duct Tape Programmers who are the ones casting to void * because they can't be bothered with templates. Now I know nothing of COM or CORBA, but multithreading is generally not something you have a choice about. Avoid it if you can, think very carefully about when you need to use it because of the application requirements.

Your strategy is the perfect way to maximize your income if you are jumping from company to company. I replaced a guy that worked like this. If you are working on not getting fired, it is a bad strategy because code quality is vital when it comes to application stability. No one likes an application that is constantly crashing.

Thus spake the master programmer:

Perhaps "Mean Time To Failure" is some measure of bug frequency.

From wikipedia:

When I check out code from cvs to update it, I think of that as a fork. When I check it back in, I merge my fork back onto the trunk or a branch. Two slightly different definitions. I would call what you are referring to as a fork as a permanent fork.

Really? accepted conventional wisdom over the laws of physics? really? I quit