Lawyers are people too. Where do you think his loyalties lie?
In particular, do they lie with Article I, Section 8, Clause 8, or with its natural enemies, those for whom he has already committed numerous ethical breaches?
Sorry, but for my taste, given his background he has too much experience representing the interests of the scum of the earth. His motives are suspect from the get-go, so of course the reason for his appointment is suspect.
It sure would be nice if public money -> public property. All this contracting out of services by govt without the responsibilities of govt is really annoying. There's a trap there though, in that those with scholarships would be disadvantaged compared to those with rich parents or a job to pay for university.
However, at a university you pay them. Your use of university equipment should be covered by your tuition (and fees!), and thus the university should have no rights to your thoughts.
Now if you're employed by a university, that's another matter entirely.
Well clearly then, we need better models as managers.
You're right of course, but keep in mind that it is the manager's job to be engaged enough to tell the difference. If PHB can't tell the difference, then he's not doing his job and *his* manager should notice. Or maybe the top brass' demand to cut 20% of every team was stupid and PHB was dumb/naive enough to not have padded with some slackers against such ahead of time.
It's not about operating efficiently. They've backed themselves into a position where they can't operate intelligently. If for instance they'd rebase to any of several different superior OS kernels they could get rid of much maintenance headache; turn the antivirus dept into an in-depth QA team mostly doing basic research into hardening an OS; and sell their "qualified resellers" new qualifications.
But they won't do so willingly, so watch out when their long bets come due. They will fall down in a mess, and because it's "unexpected" we US taxpayers will be stuck with yet another game of 52-card pickup.
Okay, so don't blindly rely on imperfect models. Their managers should know who the slackers are, what they do and what the consequences are of firing their ass. That's their *job*. Otherwise, fire the oblivious boss and promote Wally. Then fire Wally and repeat until sanity is visible.
Integrate the rails hacking into your release process.
* import rails into your scm -- one that has good branching and merging
* regularly update your scm rails trunk to recent upstream release
* branch rails locally as part of your release process. that includes using the branched release in QA.
* get as much of your local changes as possible merged upstream! it's a pita to start, but your effort will be rewarded.
Use the right tool for the job.
* use standard APIs so you can switch back and forth between your implementation and others' easily. when possible, of course; not all commonly used APIs are well thought out.
* if rails doesn't do something well, use another tool that does. examples:
** regenerating content all the time? look at memcached.
** need local disk-backed storage? sqlite, not mysql/pg/etc.
* are you sure rails is your bottleneck? not disk-wait for your database?
If the information exists, you can bet your freedom that law enforcement will attempt to use it to secure your conviction.
And if its use can be automated, you can be similarly certain that its use will be automated, whether appropriately or otherwise. After all, the courts are there to sort it all out.
Back when ebcdic was relevant, the basic encoding of characters wasn't a mature technology. Now it is. ASCII will be in use as the lowest common denominator for a long time, if only as a subset of utf.
Go ahead and rely on ascii for your word processing needs. Vim is heavy-weight enough as it is -- no sense weighing down your whole machine with something gargantuan like ooo or emacs.
Many of those poor out of work bankers etc who lost my retirement funds could be put to work watching the content. That would please all the upstanding citizens of decency trying to reign in the pesky civil liberties those hippies won over the years.
Put it in tv format with two buttons, yea and nay. Add a third button for buy, and everybody wins.
Just because lefties think [asinine action of the week] is a righty conspiracy doesn't imply that it's not a conspiracy. And vice versa.
Just because righties deny that [convenient coincidence of the week] is a conspiracy doesn't imply that it is a conspiracy. And vice versa.
And vice versa.
Applying critical thought to what each side says is not unbalanced reporting. Reporters, in general, are in a much better position to connect the dots than is the general public.
Not giving the other side a chance to rebut, on the other hand, is unbalanced reporting. However, the rebuttal does not have to be in the same article. Ideally, there would be N+1 articles, one for each side and one where critical thought is applied.
Or in addition to. It gives them a "nice" option. As you suggest, there is of course no guarantee they'll use it in a way you or I might find acceptable.
Think of it as a way for the NSA to publish prior art without giving up any top secret status or saying when they first implemented it.
It is still a bit annoying that they get the patents starting at disclosure date rather than at filing date. Oh well, at least this way they might actually file instead of suppressing the tech via goons.
Teach thinking. Not a language, and not a paradigm.
SICP lays good foundations. An intro course is basically a survey course -- intro to concepts with some basic practice thrown in to help cement the concepts with repetition. Remember, you're laying the foundations for Computer Science, not for programmer-tradesman.
Unless you're teaching CS at a trade school of course, in which case go through some basic concepts with pencil and chalk, then use something like python and work your way from simple logic controls (if-then), to functions, to objects. The second course can teach Cobol -- I mean Java, or whatever it's called these days.
Or the community college version: html to get the toes wet, followed by css and perhaps javascript for the "gifted" students.
Slashdot Mirror
Hey, I don't care about his sexual proclivities. I just want him to act responsibly and ethically.
So did Obama not do his research, or is this a demonstration of to whom he owes favors?
Lawyers are people too. Where do you think his loyalties lie?
In particular, do they lie with Article I, Section 8, Clause 8, or with its natural enemies, those for whom he has already committed numerous ethical breaches?
And this guy's client is whom exactly?
Sorry, but for my taste, given his background he has too much experience representing the interests of the scum of the earth. His motives are suspect from the get-go, so of course the reason for his appointment is suspect.
It sure would be nice if public money -> public property. All this contracting out of services by govt without the responsibilities of govt is really annoying. There's a trap there though, in that those with scholarships would be disadvantaged compared to those with rich parents or a job to pay for university.
However, at a university you pay them. Your use of university equipment should be covered by your tuition (and fees!), and thus the university should have no rights to your thoughts.
Now if you're employed by a university, that's another matter entirely.
Well clearly then, we need better models as managers.
You're right of course, but keep in mind that it is the manager's job to be engaged enough to tell the difference. If PHB can't tell the difference, then he's not doing his job and *his* manager should notice. Or maybe the top brass' demand to cut 20% of every team was stupid and PHB was dumb/naive enough to not have padded with some slackers against such ahead of time.
It's not about operating efficiently. They've backed themselves into a position where they can't operate intelligently. If for instance they'd rebase to any of several different superior OS kernels they could get rid of much maintenance headache; turn the antivirus dept into an in-depth QA team mostly doing basic research into hardening an OS; and sell their "qualified resellers" new qualifications.
But they won't do so willingly, so watch out when their long bets come due. They will fall down in a mess, and because it's "unexpected" we US taxpayers will be stuck with yet another game of 52-card pickup.
Fire those who most unconstructively game the system?
Okay, so don't blindly rely on imperfect models. Their managers should know who the slackers are, what they do and what the consequences are of firing their ass. That's their *job*. Otherwise, fire the oblivious boss and promote Wally. Then fire Wally and repeat until sanity is visible.
Psst. Don't tell my boss I'm here.
Integrate the rails hacking into your release process.
* import rails into your scm -- one that has good branching and merging
* regularly update your scm rails trunk to recent upstream release
* branch rails locally as part of your release process. that includes using the branched release in QA.
* get as much of your local changes as possible merged upstream! it's a pita to start, but your effort will be rewarded.
Use the right tool for the job.
* use standard APIs so you can switch back and forth between your implementation and others' easily. when possible, of course; not all commonly used APIs are well thought out.
* if rails doesn't do something well, use another tool that does. examples:
** regenerating content all the time? look at memcached.
** need local disk-backed storage? sqlite, not mysql/pg/etc.
* are you sure rails is your bottleneck? not disk-wait for your database?
If the information exists, you can bet your freedom that law enforcement will attempt to use it to secure your conviction.
And if its use can be automated, you can be similarly certain that its use will be automated, whether appropriately or otherwise. After all, the courts are there to sort it all out.
I see. So, "ASCII Forever!" you say?
Back when ebcdic was relevant, the basic encoding of characters wasn't a mature technology. Now it is. ASCII will be in use as the lowest common denominator for a long time, if only as a subset of utf.
Go ahead and rely on ascii for your word processing needs. Vim is heavy-weight enough as it is -- no sense weighing down your whole machine with something gargantuan like ooo or emacs.
Many of those poor out of work bankers etc who lost my retirement funds could be put to work watching the content. That would please all the upstanding citizens of decency trying to reign in the pesky civil liberties those hippies won over the years.
Put it in tv format with two buttons, yea and nay. Add a third button for buy, and everybody wins.
Look to the market to see its wants -- then give them that. Nobody wants to be extorted.
The extortion that you see is only the tip of the iceberg. The real corruption hides.
They already have those huge spinning things. Why not just enclose them and suck out all the air?
Put back in the externalized costs, so's to compare real costs. Then we'll talk.
Agreed. Use Perl unless undef.
Lack of experience checking/balancing a power-mad executive branch?
Not to be biased or anything :)
Scared of jumping the gun like in the jism pogrom?
Just because lefties think [asinine action of the week] is a righty conspiracy doesn't imply that it's not a conspiracy. And vice versa.
Just because righties deny that [convenient coincidence of the week] is a conspiracy doesn't imply that it is a conspiracy. And vice versa.
And vice versa.
Applying critical thought to what each side says is not unbalanced reporting. Reporters, in general, are in a much better position to connect the dots than is the general public.
Not giving the other side a chance to rebut, on the other hand, is unbalanced reporting. However, the rebuttal does not have to be in the same article. Ideally, there would be N+1 articles, one for each side and one where critical thought is applied.
The collections of essays called Programming On Purpose, by PJ Plauger is well worth overlooking the poor choice of typeface on the covers.
There are three volumes, all well worth internalizing.
Sorry, I don't loan mine.
Or in addition to. It gives them a "nice" option. As you suggest, there is of course no guarantee they'll use it in a way you or I might find acceptable.
Ah, a way to force disclosure of NSA documents!
Think of it as a way for the NSA to publish prior art without giving up any top secret status or saying when they first implemented it.
It is still a bit annoying that they get the patents starting at disclosure date rather than at filing date. Oh well, at least this way they might actually file instead of suppressing the tech via goons.
Teach thinking. Not a language, and not a paradigm.
SICP lays good foundations. An intro course is basically a survey course -- intro to concepts with some basic practice thrown in to help cement the concepts with repetition. Remember, you're laying the foundations for Computer Science, not for programmer-tradesman.
Unless you're teaching CS at a trade school of course, in which case go through some basic concepts with pencil and chalk, then use something like python and work your way from simple logic controls (if-then), to functions, to objects. The second course can teach Cobol -- I mean Java, or whatever it's called these days.
Or the community college version: html to get the toes wet, followed by css and perhaps javascript for the "gifted" students.
The problem in US schools is engagement. Computers will not magically solve that.
That's engagement by both students and parents, BTW.