Wrong. If the boss thinks you do a good job. Unfortunately, the amount of brainpower used when debugging can't really be measured, and wildly varies based on outside factors, like your API working correctly, the quality of the bug report, the type of bug (ever had one of those that only come out when you gave up looking for it?) etc.
Bragging and blaming will let the boss know about those factors, so he may appreciate your 3 fixed heisenbugs where you had to hunt down the reporter who was on vacation more than your coworkers' 10 off-by-ones taking 5 minutes each. If you ignore office politics, you'll be on the wrong end of it.
However, a $300 Dell laptop is more than enough for a degree in software, and students are pretty much assumed to have one already for an online course. Maybe we should start there first.
Spreading news is cheap. Gathering news is expensive.
You might want to decide which side of the business you are in, and how much profit you expect from it. News is by definition severely affected by the internet, and will change along with it.
Twitter spread the panic about swine flu much faster than any news site, maybe we can recreate the effect without panic.
What am I supposed to pay for, exactly? What is the value they bring to my news-reading experience that is so good that the free sites can't keep up? And if the free ones start to disappear, a fully distributed p2p news network isn't hard to create. All you need is to combine rss with a p2p protocol and throw in some search and filter options.
News is cheap. You don't need a whole website for 300 words of text and maybe a link to an image hosting site or youtube.
If money is your only motivation for writing books, don't.
If you can't write a book in the age of the internet purely for the joy that other people might read and appreciate it, or use a searchable database of books to market yours, go get a real job. I cannot help you.
I'd like to see the article providing proof of that level of monitoring by the NSA (or any other government agency for that matter).
I'd like to see the summary at least hinting at what Facebook actually did. Some of us don't care enough to RTFA, but it would be nice to know.
Also, that level of monitoring would require them to connect "every email, teyt message, blog post, and Slashdor comment" to be attached to real people. Jurily is not traceable to me.
Also the part about "even those who find manuals 'difficult to read and understand.'" makes me wonder just how much "expert knowledge" will actually survive the transition.
Define "reasonable" - reasonable according to the end-user (okay, somewhat geeky end-user), or "reasonable" to Comcast, Verizon, AT&T...
Here's my take: if you provide service to the end-user, you only take money from the end-user. When providing said service, you don't look at where a packet is coming from, only where it goes.
If your network can't handle it, you upgrade your network.
Whatever the case, defrag-on-file-change is certainly an interesting approach. Unfortunately we'd have to rewrite damn near everything to make it happen without serious performance problems, while teaching every programmer out there to write new software accordingly. Also, you can just buy SSD's and get on with your life, so we missed this boat by a couple of decades.
In future computers I expect re-bootless updates and always on machines that don't use much power. And batteries that can suspend to RAM for weeks on end. Booting will become less common.
My first mp3 player was like that. Unfortunately, it didn't have a reset button and it retained state even across battery changes. Guess what happened after the first freeze. 5 years later, it still displays the same scrambled screen whenever powered up. I keep it around to remind me never to get too arrogant about my code.
As for suspend to RAM, I dual boot Gentoo and Vista, and ditching either one is not an option. Neither is virtualization (development and testing on both, with games added on Vista).
(was so aggresive with putting files in contiguous blocks that a defrag script back then just renamed forth and back all files to do the work)
While this might be a decent idea if the whole system knew about it, introducing it to modern Linux would be a catastrophe at best. Fill an ext3/ext4 up to 50% with typical desktop usage patterns (download-delete-move-copy-edit-etc), turn this feature on, and try to torrent a 4Gb file. You'll have plenty of time to think about the merits of your idea, I promise.
Now, think about all the programs that were written with the knowledge that renames are fast. Go no further: the standard toolchain is more than enough to demonstrate this. Is it absolutely necessary that temporary files, however big, are contiguous?
Now, add in SSD's and realize the whole debate is getting pointless.
In a modern pc, with current memory/clock speeds, if you manage that it work with all the hardware, would fly.
Nope. In a modern PC, we're taught to optimize for development speed. Make it run, make it right, and then make it fast. Which means programs get bloated, and nobody cares because computers can keep up. Note how the choice of OS does not affect this process. This is why it's still considered acceptable for a desktop computer to boot in more than 5 seconds.
tons of data self-documented by its own users...
So, there is absolutely no problem with this. I'm told people over 18 are mature enough to make these kinds of decisions for themselves.
As for minors, I don't see the value in mining their data, but it's still wrong.
I have control over my information. And that is why you wont find be on Facebook.
How about your friends?
If you do a good job, you will be rewarded.
Wrong. If the boss thinks you do a good job. Unfortunately, the amount of brainpower used when debugging can't really be measured, and wildly varies based on outside factors, like your API working correctly, the quality of the bug report, the type of bug (ever had one of those that only come out when you gave up looking for it?) etc.
Bragging and blaming will let the boss know about those factors, so he may appreciate your 3 fixed heisenbugs where you had to hunt down the reporter who was on vacation more than your coworkers' 10 off-by-ones taking 5 minutes each. If you ignore office politics, you'll be on the wrong end of it.
However, a $300 Dell laptop is more than enough for a degree in software, and students are pretty much assumed to have one already for an online course. Maybe we should start there first.
FS2 already has a B5 mod, along with many others.
Spreading news is cheap. Gathering news is expensive.
You might want to decide which side of the business you are in, and how much profit you expect from it. News is by definition severely affected by the internet, and will change along with it.
Twitter spread the panic about swine flu much faster than any news site, maybe we can recreate the effect without panic.
What am I supposed to pay for, exactly? What is the value they bring to my news-reading experience that is so good that the free sites can't keep up? And if the free ones start to disappear, a fully distributed p2p news network isn't hard to create. All you need is to combine rss with a p2p protocol and throw in some search and filter options.
News is cheap. You don't need a whole website for 300 words of text and maybe a link to an image hosting site or youtube.
Apple accepted the app, and then rejected it later, and asked that Google reimburse everyone who bought the app before that.
Now why exactly would Google need to do that? Apple fucked up, either by accepting it or by rejecting it later. They should reimburse their customers.
There are a few games I would like to write.
What I would like to see is a space fighting game, but with real physics. Something like this, but from the inside.
I think Freespace 2 would be a good start, it's already Open Source.
They used up all their creativity coming up with "i7-820QM".
Funny world we live in. Car noise became so ubiquitous, we "need" them.
I don't like cars sneaking up on me when I'm on foot. Do you?
Living next to the highway will be very entertaining.
Someone at RIAA just had a great idea.
I already am. I'm not responsible for marketing at work, and my fun projects are Open Source.
If money is your only motivation for writing books, don't.
If you can't write a book in the age of the internet purely for the joy that other people might read and appreciate it, or use a searchable database of books to market yours, go get a real job. I cannot help you.
Summary: OMG searchable books! Think of the copyright holders!
I'd like to see the article providing proof of that level of monitoring by the NSA (or any other government agency for that matter).
I'd like to see the summary at least hinting at what Facebook actually did. Some of us don't care enough to RTFA, but it would be nice to know.
Also, that level of monitoring would require them to connect "every email, teyt message, blog post, and Slashdor comment" to be attached to real people. Jurily is not traceable to me.
Also the part about "even those who find manuals 'difficult to read and understand.'" makes me wonder just how much "expert knowledge" will actually survive the transition.
Personally I would rather them downgrade the P2P priority of other people so that my Skype call doesn't break up.
I see what you did there.
Define "reasonable" - reasonable according to the end-user (okay, somewhat geeky end-user), or "reasonable" to Comcast, Verizon, AT&T...
Here's my take: if you provide service to the end-user, you only take money from the end-user. When providing said service, you don't look at where a packet is coming from, only where it goes.
If your network can't handle it, you upgrade your network.
Too bad the cops didn't shoot him. This would've made a great Darwin award.
Steve, is that you?
This looks like a poor attempt at Google Code, but with a lot more politics, beaurocracy and legal problems involved.
Whatever the case, defrag-on-file-change is certainly an interesting approach. Unfortunately we'd have to rewrite damn near everything to make it happen without serious performance problems, while teaching every programmer out there to write new software accordingly. Also, you can just buy SSD's and get on with your life, so we missed this boat by a couple of decades.
In future computers I expect re-bootless updates and always on machines that don't use much power. And batteries that can suspend to RAM for weeks on end. Booting will become less common.
My first mp3 player was like that. Unfortunately, it didn't have a reset button and it retained state even across battery changes. Guess what happened after the first freeze. 5 years later, it still displays the same scrambled screen whenever powered up. I keep it around to remind me never to get too arrogant about my code.
As for suspend to RAM, I dual boot Gentoo and Vista, and ditching either one is not an option. Neither is virtualization (development and testing on both, with games added on Vista).
(was so aggresive with putting files in contiguous blocks that a defrag script back then just renamed forth and back all files to do the work)
While this might be a decent idea if the whole system knew about it, introducing it to modern Linux would be a catastrophe at best. Fill an ext3/ext4 up to 50% with typical desktop usage patterns (download-delete-move-copy-edit-etc), turn this feature on, and try to torrent a 4Gb file. You'll have plenty of time to think about the merits of your idea, I promise.
Now, think about all the programs that were written with the knowledge that renames are fast. Go no further: the standard toolchain is more than enough to demonstrate this. Is it absolutely necessary that temporary files, however big, are contiguous?
Now, add in SSD's and realize the whole debate is getting pointless.
In a modern pc, with current memory/clock speeds, if you manage that it work with all the hardware, would fly.
Nope. In a modern PC, we're taught to optimize for development speed. Make it run, make it right, and then make it fast. Which means programs get bloated, and nobody cares because computers can keep up. Note how the choice of OS does not affect this process. This is why it's still considered acceptable for a desktop computer to boot in more than 5 seconds.