You just can't appreciate how painful device-based development can be relative to desktop development until you experience it firsthand.
You ain't kidding. Being able to read the source of the firmware I have issues with, or the SDK components that blow up in specified and version-dependent ways on a daily basis, would cut my development time by 90%.
Here, you are talking about happier developers - happier developers with faster development times make successful companies.
Well, laws don't always make sense. In this case, it's not illegal to give a bad reference per se, but there are laws establishing the liability of involved third parties for lost business, employment, contracts, or the reasonable expection of such.
Guess what folks; you are expected to be capable of coping with vehicle problems while traveling at the phenomenal rate of "highway speed". Tires blow, people fuck up, things fly off randomly; deal with it.
Of course, because there are road conditions and events which occur outside the range of the human ability to respond in time, if there is even a conceivably good response, there may be no way to deal with it and survive. Which is a good argument for taking possible new categories of vehicle malfunction seriously.
The real problem, from my point of view, is the fact that we have a country divided enough that we have 51/49 elections. There's just no way to win with any sort of majority-rules system.
Of course, this could just as easily represent a nation of individuals, each torn individually between two parties and two candidates difficult to distinguish in morally ambiguous times.
I completely agree. The stylistic device is so much more tied up in artifice than it is helpful to a reader or reflecting of actual speech. Authors, take heed!
Even if this were true, I doubt the need for C programmers to port to BeOS would put even the tiniest dent in the supply of currently underemployed C/C++ programmers, so your friend may be out of luck.
On the other hand, like donating to charities, learning C is a worthwhile occupation no matter what ridiculous motive one has.
This is probably being said elsewhere in the thread, but it's worth noting that in addition to periodic workbreaks, and exercises to keep your wrists warm, which everyone knows about, wrist-specific stretches can greatly reduce strain and injury.
I know this from my experience as a geek, musician, hockey player, and acrobat.
I said the same thing for years, but then I had an epiphany. That teaching HS is everyone's backup plan is what gives us so many uninspired, uninspiring teachers. Teaching is hard, and I respect my friends who are dedicated to it too much to consider it my backup.
You know, I've heard about how dynamic this ride is, and all about the highs and lows, but I've been standing in line for months and don't seem to be moving.
Better be confident that you are legally permitted to tell your children about your former coding life before settling down with them at bedtime with the KNR book. i don't think restrictions on free speech so as to prevent the unauthorized dissemation of software skills necessary for the creation of "circumvention devices" are beyond the current scope of our dystopia. But yeah, i'd much rather be explaining complex & outdated notions such as IP ownership consolidation than have to explain that once, we were allowed to make our friends something known as a "mix tape".
Riiight. i think, rather than make MS and other corporations less amazingly blase about the security of their users, OR make the gov't mandate OSS, this kind of catastrophe would be used to strengthen the power of corporations. Probably, the poor schmuck who made the math error causing the crash would be blamed, and we as coders would become liable, leading to coding insurance and probably, compiler licenses. Henceforth from this moment, ONLY MS would be able to sell software to the gov't, as they could afford the "mission critical" insurance, rather than just the lawsuit for lost playtime insurance that, say, EA would need. Rather than force code to be made well, i think it would just mandate the establishment of liability, so when something breaks, we know who to sue.
If technology has progressed far enough to give us the positives of very effective law enforcement and monitoring without the baggage, well more power to it!
Also being against murder, i can see where you're coming from. However, "very effective law enforcement" is bad to the extent that laws are poorly written, oppressive, or otherwise unjust. We need limited means of technological enforcement of crimes until the laws that define them are deserving of "very effective enforcement".
There's a reason the abolition movement was closely tied with the (then illegal) Underground Railroad. If people-chipping tech had been available back then, social forces for change would have been greatly hampered. No Frederick Douglas, for example, whose freedom was a result of breaking an unjust law. Remember forced sterilization in VA? Japanese internment? This was all within the last hundred years - many people now living remember these things. i expect that the War on (Some) Drugs will come to be seen the same way. Technology in law enforcement is a major threat to our civil rights.
Now, your post was pretty reasonably written, as you said, "depends on how much you trust your government". But how much can one trust a government in principle?
Question (possibly stupid): Why can't we just heave it into space? Is it due to sheer volume? Do we have plans to produce a whole lot more of it?
If so, i'll want to find another planet, but i'll probably be barred from entry due to our reputation. We need a legal system which allows people to be sued by their hypothetical descendants.
This is really no different from the patent and investment follies of the Internet bubble.
No kidding. It's just like emails that delete themselves, and all those companies with supposedly 'unbreakable' proprietary encryption. i remember when word of this guy first spread - i thought, he can magically compress video but he won't tell anyone how? Mmmhmm.
Charisma really has to be the secret ingredient. i not only couldn't have pulled this scam, i can't even fast-talk my way to extended deadlines.
i'd love to actually get a legal opinion on this. What recourse is available to an employee in this position? Could you at least recoup the >=3.6% loss before having to look for another job in june?
However, in practice, most of it indeed works as advertised. You shouldn't have much problem.
This first statement is literally true. But the second statement doesn't always follow, and just one exception can be a major roadblock to development. In one case, an STL hashmap acquired sporadic memory loss somewhere around 700,000 entries. Identifying the cause of this application malfunction swallowed large amounts of QA and developer time, and made our department responsible for pushing back a release date. With extensive testing, if you have the time for such testing, the STL can be a good tool. But in retrospect, whipping up our own quick hashed map would have been the stitch in time.
Emulating a speak'n'spell would simply consist of writing the various spelling games - the speak'n'spell used a common and public available speech synthesis algorithm, and the phonemes are publicly available. You could write a C speak'n'spell to be adapted for a variety of PDAs.
Slashdot Mirror
No no, Lisp was the question. And I doubt that Excel macros or VB script was the answer.
If Brian Behlendorf wants non-developers to write code, he's better have another BASIC up his sleeve.
Couldn't Lisp be the answer? For simple spreadsheet expressions the syntax would be at least as simple and easy-to-learn as Excel macros.
You just can't appreciate how painful device-based development can be relative to desktop development until you experience it firsthand.
You ain't kidding. Being able to read the source of the firmware I have issues with, or the SDK components that blow up in specified and version-dependent ways on a daily basis, would cut my development time by 90%.
Here, you are talking about happier developers - happier developers with faster development times make successful companies.
Squeeze as I can, I just can't fit in em.
Well, laws don't always make sense. In this case, it's not illegal to give a bad reference per se, but there are laws establishing the liability of involved third parties for lost business, employment, contracts, or the reasonable expection of such.
Age cannot wither her, nor custom stale
Her infinite variety; other women cloy
The appetite they feed, but she makes hungry
Where most she satisfies.
Guess what folks; you are expected to be capable of coping with vehicle problems while traveling at the phenomenal rate of "highway speed". Tires blow, people fuck up, things fly off randomly; deal with it.
Of course, because there are road conditions and events which occur outside the range of the human ability to respond in time, if there is even a conceivably good response, there may be no way to deal with it and survive. Which is a good argument for taking possible new categories of vehicle malfunction seriously.
The real problem, from my point of view, is the fact that we have a country divided enough that we have 51/49 elections. There's just no way to win with any sort of majority-rules system.
Of course, this could just as easily represent a nation of individuals, each torn individually between two parties and two candidates difficult to distinguish in morally ambiguous times.
I completely agree. The stylistic device is so much more tied up in artifice than it is helpful to a reader or reflecting of actual speech. Authors, take heed!
Even if this were true, I doubt the need for C programmers to port to BeOS would put even the tiniest dent in the supply of currently underemployed C/C++ programmers, so your friend may be out of luck.
On the other hand, like donating to charities, learning C is a worthwhile occupation no matter what ridiculous motive one has.
This is probably being said elsewhere in the thread, but it's worth noting that in addition to periodic workbreaks, and exercises to keep your wrists warm, which everyone knows about, wrist-specific stretches can greatly reduce strain and injury.
I know this from my experience as a geek, musician, hockey player, and acrobat.
I said the same thing for years, but then I had an epiphany. That teaching HS is everyone's backup plan is what gives us so many uninspired, uninspiring teachers. Teaching is hard, and I respect my friends who are dedicated to it too much to consider it my backup.
You know, I've heard about how dynamic this ride is, and all about the highs and lows, but I've been standing in line for months and don't seem to be moving.
Better be confident that you are legally permitted to tell your children about your former coding life before settling down with them at bedtime with the KNR book. i don't think restrictions on free speech so as to prevent the unauthorized dissemation of software skills necessary for the creation of "circumvention devices" are beyond the current scope of our dystopia.
But yeah, i'd much rather be explaining complex & outdated notions such as IP ownership consolidation than have to explain that once, we were allowed to make our friends something known as a "mix tape".
If you think a lawsuit destroyed hiphop, you're more than white, you're missing the point.
Riiight. i think, rather than make MS and other corporations less amazingly blase about the security of their users, OR make the gov't mandate OSS, this kind of catastrophe would be used to strengthen the power of corporations. Probably, the poor schmuck who made the math error causing the crash would be blamed, and we as coders would become liable, leading to coding insurance and probably, compiler licenses. Henceforth from this moment, ONLY MS would be able to sell software to the gov't, as they could afford the "mission critical" insurance, rather than just the lawsuit for lost playtime insurance that, say, EA would need. Rather than force code to be made well, i think it would just mandate the establishment of liability, so when something breaks, we know who to sue.
Exactly my question. Why do you need to use a laptop during a show again?
Even film critics typically just use a 'light pen.'
If technology has progressed far enough to give us the positives of very effective law enforcement and monitoring without the baggage, well more power to it!
Also being against murder, i can see where you're coming from. However, "very effective law enforcement" is bad to the extent that laws are poorly written, oppressive, or otherwise unjust. We need limited means of technological enforcement of crimes until the laws that define them are deserving of "very effective enforcement".
There's a reason the abolition movement was closely tied with the (then illegal) Underground Railroad. If people-chipping tech had been available back then, social forces for change would have been greatly hampered. No Frederick Douglas, for example, whose freedom was a result of breaking an unjust law. Remember forced sterilization in VA? Japanese internment? This was all within the last hundred years - many people now living remember these things. i expect that the War on (Some) Drugs will come to be seen the same way. Technology in law enforcement is a major threat to our civil rights.
Now, your post was pretty reasonably written, as you said, "depends on how much you trust your government". But how much can one trust a government in principle?
Z-trip - i really like his b-boy breaks.
Question (possibly stupid): Why can't we just heave it into space? Is it due to sheer volume? Do we have plans to produce a whole lot more of it?
If so, i'll want to find another planet, but i'll probably be barred from entry due to our reputation. We need a legal system which allows people to be sued by their hypothetical descendants.
Maybe music shouldn't be protected because all that gangster rap just talks about killing cops.
Maybe this is a troll, but i'll bite.
This line stands out from all your other examples, because this is precisely why certain rap should be protected.
This is really no different from the patent and investment follies of the Internet bubble.
No kidding. It's just like emails that delete themselves, and all those companies with supposedly 'unbreakable' proprietary encryption. i remember when word of this guy first spread - i thought, he can magically compress video but he won't tell anyone how? Mmmhmm.
Charisma really has to be the secret ingredient. i not only couldn't have pulled this scam, i can't even fast-talk my way to extended deadlines.
i'd love to actually get a legal opinion on this. What recourse is available to an employee in this position? Could you at least recoup the >=3.6% loss before having to look for another job in june?
However, in practice, most of it indeed works as advertised. You shouldn't have much problem.
This first statement is literally true. But the second statement doesn't always follow, and just one exception can be a major roadblock to development. In one case, an STL hashmap acquired sporadic memory loss somewhere around 700,000 entries. Identifying the cause of this application malfunction swallowed large amounts of QA and developer time, and made our department responsible for pushing back a release date. With extensive testing, if you have the time for such testing, the STL can be a good tool. But in retrospect, whipping up our own quick hashed map would have been the stitch in time.
Emulating a speak'n'spell would simply consist of writing the various spelling games - the speak'n'spell used a common and public available speech synthesis algorithm, and the phonemes are publicly available. You could write a C speak'n'spell to be adapted for a variety of PDAs.