sorry about the bad formatting, this time in plain old text:
I recognize this to, altough i do get enough sleep and spend time doing other stuff.
I usually try to work until i reach a good "stopping point". e.g. a (couple) of bugs solved, a new feature ready, etc. This way its easier to take your mind of it and get some rest.
If you dont do that, the problems you describe do occur: you keep on going because everything goes well and smooth, and its fun. But after a couple of days you get tired, sick , exhausted, have trouble sleeping, dream about code etc. At this point you get inproductive and make mistakes, or even have to take a day or 2 'rest' to 'recover'.
Especially dreaming about code is bad, you have to prevent that, by stopping a hour or 2 earlier, and do other non-computer related stuff. Otherwise your brain wont rest enough and the same problems might reoccur.
Some tips: -whenever you need a short break or are compiling, clean up your house and do the other 'dumb' stuff you normally dont do. This way you move and stuff gets done. Just cleanup a few things at a time. -dont go to bed right after coding, build in some relaxing time. -try to stop at a good point so your mind doesnt have any problem left it wants to solve: this means sometimes you work longer, but sometimes you work SHORTER and DONT start working on a new problem. very important: once you started a new problem, its too late and you're locked in;) -what also helps a lot is meditation: but you have to take time for it and have to ease into it. Its not something you should schedule and rush.:) -if you work together with someone, get together at least once a week when the weather is nice, and take a walk, talking about work, code, or other stuff. -try to do meetings you have with 1 or 2 persons outside while walking or sitting outside somewhere.
But its true: its always hard to keep the right balance between coding and 'the rest'.:) I'm always had this problem a bit, nice to see i'm not the only one.
I recognize this to, altough i do get enough sleep and spend time doing other stuff.
I usually try to work until i reach a good "stopping point". e.g. a (couple) of bugs solved, a new feature ready, etc. This way its easier to take your mind of it and get some rest.
If you dont do that, the problems you describe do occur: you keep on going because everything goes well and smooth, and its fun. But after a couple of days you get tired, sick , exhausted, have trouble sleeping, dream about code etc. At this point you get inproductive and make mistakes, or even have to take a day or 2 'rest' to 'recover'.
Especially dreaming about code is bad, you have to prevent that, by stopping a hour or 2 earlier, and do other non-computer related stuff. Otherwise your brain wont rest enough and the same problems might reoccur.
Some tips:
-whenever you need a short break or are compiling, clean up your house and do the other 'dumb' stuff you normally dont do. This way you move and stuff gets done. Just cleanup a few things at a time.
-dont go to bed right after coding, build in some relaxing time.
-try to stop at a good point so your mind doesnt have any problem left it wants to solve: this means sometimes you work longer, but sometimes you work SHORTER and DONT start working on a new problem. very important: once you started a new problem, its too late and you're locked in;)
-what also helps a lot is meditation: but you have to take time for it and have to ease into it. Its not something you should schedule and rush.:)
-if you work together with someone, get together at least once a week when the weather is nice, and take a walk, talking about work, code, or other stuff.
-try to do meetings you have with 1 or 2 persons outside while walking or sitting outside somewhere.
But its true: its always hard to keep the right balance between coding and 'the rest'.:) I'm always had this problem a bit, nice to see i'm not the only one.
Someone else has any tips like these?
is it possible to create pepetium mobiles now?;)
most of the the 'free energy' designs are based around non-existing monopoles, and tricks to 'emulate' monopoles.
I wonder when the aircrack-ng team comes up with a solution to use this power to bruteforce wpa keys.
Elcomsoft already does this: http://mobile.slashdot.org/article.pl?sid=08/10/12/1724230
The already claimed a 100x speed increase, so i wonder what can be done with this new card.
The goal of the bait-and-switch is to convince some buyers to purchase the substitute good as a means of avoiding disappointment over not getting the bait, or as a way to recover sunk costs expended to try to obtain the bait.
Perl 6 promises to put the "regular" back into regular expression.
"We have more powerful primitives in Perl 6," Wall said. "There's no more/x switch to enable extended syntax. No more mode switches like/s and "dot" (.) now means match any character. There's no/m modifier and we've regularised the brackets so {} always mean embedded code."
Re:So let the flame wars begin!
on
The Birth of vi
·
· Score: 2, Informative
You might want to try mcedit, for that oldskool dos-edit feeling.:) (part of midnight commander)
"What can a $1000 laptop do that the $100 version can't? Not much. The plan is for the $100 Laptop to do almost everything. What it will not do is store a massive amount of data. What it will have is a level of robustness found on very few laptops of any price; a display that works indoors and out; an order of magnitude improvement in power consumption; and an exceptional wifi antenna design."
"What about connectivity? Aren't telecommunications services expensive in the developing world? When these machines pop out of the box, they will make a mesh ether network of their own, peer-to-peer. This is something initially developed at MIT and the Media Lab. Connectivity to the Internet will be from the mesh through gateways at the schools. (We are working with the local governments and the private sector regarding how to reduce the cost of Internet access. The Motoman project is an example of how you can make a little connectivity go a very long way.)"
So the $100 can do some stuff a regular laptop cant do. Also, a regular laptop probably has a lot of features that are not needed, nor desired in those countrys. (IEEE, utp networking, cdrom drives that break easily, moving parts like fans and disks, screens that brake and arent usable in the sun) Some specs of the laptop are even Military grade. Its expected that the laptop will last years longer than a normal consumer laptop.
So in the end its not about building a laptop as cheap as possible, or one that has many features and software. Its about building a DEVICE that helps kids to learn, communicate, share and express their creativity in countries like rwanda and Uruguay, for years and years to come.
I've spend hours reading the wiki, and i think some time in the future schools in our own countrys will also start providing a similar laptop to all young students, instead of books.
Yep, that, and the fact that the desktop doesnt look/feel like anything we're used to at all. The price is not the only thing that makes this laptop so special; its a revolutionary new concept of computing.
Perhaps, but keep in mind that the hardware and software is custom tailorred for this project. For example, they've stripped unnessesary connectors and controllers, the casing is shock/water/dust proof, the screen is usable in sunlight, and the kernel and user space software is heavily adjusted.
On the wiki you will see things like: "Marcelo Tosatti, one of the Red Hat OLPC staff has recently made the 'tickless' patches work on the Geode. He's now at of order 50 interrupts/second and investigating further. He also cleaned up the USB-EHCI driver to stop polling and become interrupt driven, again reducing wakeup overhead."
So the hardware and software are both very focussed on a particular usecase. Off-the-self hardware and software just isn't usable.
Why got the parent modded up??
Did you actually took the time to look at the OLPC wiki, to see whats going on??? Or did you just started googling for 'cheap laptop hardware'? This project has NOTHING to do with huge amounts of ram or big harddrives. This project is focussed on building a CHEAP laptop from scratch, to be used by childeren in poor countries.
It's not about l33ching pr0n and playing WoW.
Bloat, and dependencys. This should be a very MINIMALISTIC system, with out any bloat like XML. Furthermore the main document-exchanging will be between those laptops.
Most of the software they use will be created specially for this project, using python/pango/i18n. The minimalistic desktop environment focusses ONLY at the features that are needed. It also seems to use a lot of icons, so it probably doesnt need a lot of internationalization.
I think this will be a very promissing project. I just spended an hour or so reading a lot of stuff at the wiki. A lot of the difficult work already has been done.
I think the "OLPC" is just a first wave in a new corporate strategy to "legitimately" dump difficult-to-dispose-of old hardware and then sell new hardware in developing countries. Please read the OLPC wiki before you start rambling, especially this page: http://wiki.laptop.org/go/OLPC_myths
That news page is more than a year old. Besides, that kind of 'hobnobbing' is probably part of his job: figuring out what kind of software to use and whats best for his country/wallet.
I wonder what percentage of Microsofts resources is outsourced to India.
Maybe that job position _requires_ good communication skills with Indian people. (alltough they may not make that clear to you in a direct way)
Slashdot Mirror
Nobody mentioned rob gongrijps cryptophone yet. It uses regular cellphone calls. Instead of voip. You both need to have that phone tough.
The force is strong in this one, it is!
sorry about the bad formatting, this time in plain old text:
I recognize this to, altough i do get enough sleep and spend time doing other stuff.
I usually try to work until i reach a good "stopping point". e.g. a (couple) of bugs solved, a new feature ready, etc. This way its easier to take your mind of it and get some rest.
If you dont do that, the problems you describe do occur: you keep on going because everything goes well and smooth, and its fun. But after a couple of days you get tired, sick , exhausted, have trouble sleeping, dream about code etc. At this point you get inproductive and make mistakes, or even have to take a day or 2 'rest' to 'recover'.
Especially dreaming about code is bad, you have to prevent that, by stopping a hour or 2 earlier, and do other non-computer related stuff. Otherwise your brain wont rest enough and the same problems might reoccur.
Some tips: ;) :)
-whenever you need a short break or are compiling, clean up your house and do the other 'dumb' stuff you normally dont do. This way you move and stuff gets done. Just cleanup a few things at a time.
-dont go to bed right after coding, build in some relaxing time.
-try to stop at a good point so your mind doesnt have any problem left it wants to solve: this means sometimes you work longer, but sometimes you work SHORTER and DONT start working on a new problem. very important: once you started a new problem, its too late and you're locked in
-what also helps a lot is meditation: but you have to take time for it and have to ease into it. Its not something you should schedule and rush.
-if you work together with someone, get together at least once a week when the weather is nice, and take a walk, talking about work, code, or other stuff.
-try to do meetings you have with 1 or 2 persons outside while walking or sitting outside somewhere.
But its true: its always hard to keep the right balance between coding and 'the rest'. :) I'm always had this problem a bit, nice to see i'm not the only one.
Someone else has any tips like these?
I recognize this to, altough i do get enough sleep and spend time doing other stuff. I usually try to work until i reach a good "stopping point". e.g. a (couple) of bugs solved, a new feature ready, etc. This way its easier to take your mind of it and get some rest. If you dont do that, the problems you describe do occur: you keep on going because everything goes well and smooth, and its fun. But after a couple of days you get tired, sick , exhausted, have trouble sleeping, dream about code etc. At this point you get inproductive and make mistakes, or even have to take a day or 2 'rest' to 'recover'. Especially dreaming about code is bad, you have to prevent that, by stopping a hour or 2 earlier, and do other non-computer related stuff. Otherwise your brain wont rest enough and the same problems might reoccur. Some tips: -whenever you need a short break or are compiling, clean up your house and do the other 'dumb' stuff you normally dont do. This way you move and stuff gets done. Just cleanup a few things at a time. -dont go to bed right after coding, build in some relaxing time. -try to stop at a good point so your mind doesnt have any problem left it wants to solve: this means sometimes you work longer, but sometimes you work SHORTER and DONT start working on a new problem. very important: once you started a new problem, its too late and you're locked in ;)
-what also helps a lot is meditation: but you have to take time for it and have to ease into it. Its not something you should schedule and rush. :)
-if you work together with someone, get together at least once a week when the weather is nice, and take a walk, talking about work, code, or other stuff.
-try to do meetings you have with 1 or 2 persons outside while walking or sitting outside somewhere.
But its true: its always hard to keep the right balance between coding and 'the rest'. :) I'm always had this problem a bit, nice to see i'm not the only one.
Someone else has any tips like these?
is it possible to create pepetium mobiles now? ;)
most of the the 'free energy' designs are based around non-existing monopoles, and tricks to 'emulate' monopoles.
I wonder when the aircrack-ng team comes up with a solution to use this power to bruteforce wpa keys. Elcomsoft already does this: http://mobile.slashdot.org/article.pl?sid=08/10/12/1724230 The already claimed a 100x speed increase, so i wonder what can be done with this new card.
The goal of the bait-and-switch is to convince some buyers to purchase the substitute good as a means of avoiding disappointment over not getting the bait, or as a way to recover sunk costs expended to try to obtain the bait.
thats just...recursive
Perl 6 promises to put the "regular" back into regular expression. "We have more powerful primitives in Perl 6," Wall said. "There's no more /x switch to enable extended syntax. No more mode switches like /s and "dot" (.) now means match any character. There's no /m modifier and we've regularised the brackets so {} always mean embedded code."
You might want to try mcedit, for that oldskool dos-edit feeling.:) (part of midnight commander)
You can find all this information on the wiki. For example: http://wiki.laptop.org/go/Our_technology
:)
"What can a $1000 laptop do that the $100 version can't?
Not much. The plan is for the $100 Laptop to do almost everything. What it will not do is store a massive amount of data. What it will have is a level of robustness found on very few laptops of any price; a display that works indoors and out; an order of magnitude improvement in power consumption; and an exceptional wifi antenna design."
"What about connectivity? Aren't telecommunications services expensive in the developing world?
When these machines pop out of the box, they will make a mesh ether network of their own, peer-to-peer. This is something initially developed at MIT and the Media Lab. Connectivity to the Internet will be from the mesh through gateways at the schools. (We are working with the local governments and the private sector regarding how to reduce the cost of Internet access. The Motoman project is an example of how you can make a little connectivity go a very long way.)"
So the $100 can do some stuff a regular laptop cant do. Also, a regular laptop probably has a lot of features that are not needed, nor desired in those countrys. (IEEE, utp networking, cdrom drives that break easily, moving parts like fans and disks, screens that brake and arent usable in the sun) Some specs of the laptop are even Military grade. Its expected that the laptop will last years longer than a normal consumer laptop.
So in the end its not about building a laptop as cheap as possible, or one that has many features and software. Its about building a DEVICE that helps kids to learn, communicate, share and express their creativity in countries like rwanda and Uruguay, for years and years to come.
I've spend hours reading the wiki, and i think some time in the future schools in our own countrys will also start providing a similar laptop to all young students, instead of books.
I would urge people that have their doubts about this project to read the FAQ and Myth pages on the wiki:
http://wiki.laptop.org/go/Faq and http://wiki.laptop.org/go/OLPC_myths .
Maybe some of you even are willing to help.
Yep, that, and the fact that the desktop doesnt look/feel like anything we're used to at all. The price is not the only thing that makes this laptop so special; its a revolutionary new concept of computing.
Perhaps, but keep in mind that the hardware and software is custom tailorred for this project. For example, they've stripped unnessesary connectors and controllers, the casing is shock/water/dust proof, the screen is usable in sunlight, and the kernel and user space software is heavily adjusted.
On the wiki you will see things like:
"Marcelo Tosatti, one of the Red Hat OLPC staff has recently made the 'tickless' patches work on the Geode. He's now at of order 50 interrupts/second and investigating further. He also cleaned up the USB-EHCI driver to stop polling and become interrupt driven, again reducing wakeup overhead."
So the hardware and software are both very focussed on a particular usecase. Off-the-self hardware and software just isn't usable.
Why got the parent modded up?? Did you actually took the time to look at the OLPC wiki, to see whats going on??? Or did you just started googling for 'cheap laptop hardware'? This project has NOTHING to do with huge amounts of ram or big harddrives. This project is focussed on building a CHEAP laptop from scratch, to be used by childeren in poor countries. It's not about l33ching pr0n and playing WoW.
Bloat, and dependencys. This should be a very MINIMALISTIC system, with out any bloat like XML. Furthermore the main document-exchanging will be between those laptops.
Most of the software they use will be created specially for this project, using python/pango/i18n. The minimalistic desktop environment focusses ONLY at the features that are needed. It also seems to use a lot of icons, so it probably doesnt need a lot of internationalization. I think this will be a very promissing project. I just spended an hour or so reading a lot of stuff at the wiki. A lot of the difficult work already has been done.
That news page is more than a year old. Besides, that kind of 'hobnobbing' is probably part of his job: figuring out what kind of software to use and whats best for his country/wallet.
I wonder what percentage of Microsofts resources is outsourced to India. Maybe that job position _requires_ good communication skills with Indian people. (alltough they may not make that clear to you in a direct way)