>>>When the majority of the best and brightest in the country all lean towards a particular political philosophy, what should that tell you?
Don't know. I bet you could find examples in history of periods in time where the majority of the best and brightest in a country all leaned towards a particular political philosophy, and yet that political philosophy was terrible.
"guy" rolls out in conversation too easily as male gender tends to be the default in spoken english. So I'd cut some slack on the word "guy" (unless he was specific and said "no, really, hire a male etc")
To me that's just politics of fear the corporate world. An employee can "sue the shit" (or try to) out of a company for anything, therefore the company requires every employee to insert an rfid anal probe before entering the building. I don't buy it. I work at a place where it's part of some employees' jobs to view soft and hard core porn. She'd have to complain to management first. -Then- management can warn the employee and escalate from there by starting to monitor the -specific- employee's traffic. It's back to the practice of trust your employees -first-; not, "we don't trust our employees from, therefore everyone gets an anal probe" or to quote the original article, "if you don't think your threat exists from the inside... your just not looking".
>>>So remember this when you bitch about security. The behavior above was detected by security tools. And this type of behavior in corporate America costs companies lots and reduces the security of your job. Security is to enable you to do your job AND is there to prevent the 1/100 bad asses from getting inside to do your company harm. And the opposite is true, to prevent the 1/100 bad asses you have hired from compromising your company.
>>>And if you don't think your threat exists from the inside, your either a very small trustworthy group or your just not looking.
Pretty much with you except that last sentence pisses me off. It's saying our employees are suspect up front and we've hired "security" to monitor and catch them. Go ahead and work to keep the bad stuff out, but I'd much prefer you stop watching every page I hit because I'm a suspect, and deciding which urls I should never be allowed to see. Give everyone decent net access and trust them first. Watch traffic for disruptive loads before asking the user "did you need to be downloading so much?" Then escalate from there based on the user's behavior.
I don't see any justification for setting up a system that effectively pages you if a user decides to look at a naked woman/man where the actual net effect is a handful of web requests among 10's of 1000's. (streaming a 500kbs video is different). Management that is doing it's job will have other other proper ways of measuring an employee's productivity/contribution.
I see about the root/reboot access, if your point is you don't want to have root access in order to reboot his systems. You don't need "root" to reboot windows. And your "IT" user account on his nix box can be given reboot ability without root. Though I concede having to reboot at all in order to get at the other system is overhead that 2 machines doesn't have.
While I'm all for having 2 machines over 1 dual boot, I don't follow your logic points for why 2 machines are better for you as the IT person...
* One side is always down, meaning network monitors need special work
If you give the guy 2 machines, one side could still be "always" down as he may turn on only the one he needs while working. The fact that he can work now with a dual boot machine means exactly this.
* Either both sides share one IP address, or each gets its own. Either figure out which one is running, or figure out which address to use.
If you gave him 2 machines, you'd have probably 2 IPs as well. Though not necessarily if he has one in use at a time. Maybe he switched the single network cable allowed in his cube when he switches machines.
* It requires physical intervention (or extraordinary hacks) to reboot remotely to the other OS
Why would you be remotely rebooting his machine? And changing the lilo ini file (or windows boot.ini) to default to the other os before rebooting doesn't seem like an "extraordinary hack" anyway. I'm sure you're probably a couple of clicks away from a boot-to-other-OS script/tool too.
* I can't just wax the whole thing if something goes wrong
And if you gave him 2 machines, you -can- just wax the whole thing?
* Rebooting implies root access for whoever is around
But if you gave him 2 machines, you'd still need this implied root access to reboot them.
How do you recommend planning for the eventual drive failure that happens in 2 years? Don't these raid controllers want the drives to be the exact same model? One of my drives is "failing" (going offline periodically but not dead yet). I bought it a couple years ago and don't think I can find it for sale anymore (at least new).
Seems like a home raid solution would want as a feature the ability to stick in incrementally bigger drives. Either that, or you buy 1 or 2 extra drives and figure that'll last you for 5-10 years and by then you'll want to swap the whole thing out with something that's 10x faster and 3x cheaper.
1. an evil ET that wants to affect our global network 2. a good ET that wants to affect our global network
And the proposition is to do new work on the SETI system beyond trying to detect a signal. The decision is then one of:
- New Work: to quarantine the net to make sure ET code cannot be executed - New Work: to open the net to make sure ET code CAN be executed
Without addressing the affects of simply discovering ET, we have one of 5 possible outcomes:
A. status quo B. humanity screwed C. humanity advanced forever D. humanity Misses The Boat (ala Pascal's Wager) E. interstellar war
The normalized probabilities of the above outcomes are:
Opened Net Quarantined Net ---------- --------------- A = 9/36 A = 12/36 B = 9/36 B = 8/36 C = 9/36 C = 8/36 D = 0/36 D = 4/36 E = 9/36 E = 4/36
These flow from the following possible events:
1. net opened, ET good: outcome C 2. net quarantined, ET good: ET penetrates net, goto 1 3. net quarantined, ET good: ET doesn't penetrate, D 4. net opened, ET evil: outcome B 5. net quarantined, ET evil: ET penitrates net, goto 4 6. net quarantined, ET evil: ET doesn't penetrate, goto 8 7. net opened, ET not there: outcome A 8. net quarantined, ET not there: goto 7 9. net opened, ET1 good, ET2 evil: outcome E 10. net quarantined, ET1 good, ET2 evil: both ETs penetrate net, goto 9 11. net quarantined, ET1 good, ET2 evil: neither penetrate net, goto 8 12. net quarantined, ET1 good, ET2 evil: ET1 penetrates net, goto 2 13. net quarantined, ET1 good, ET2 evil: ET2 penetrates net, goto 5
>>Chinese is not Chinese. I worked at a company that employed several Chinese engineers. While they could all read the same newspaper, they couldn't all talk to each other. Those from the south (Hong Kong and surrounding area) couldn't understand those from the north.
I worked for a company that employeed several California engineers. They could all read the same newspaper. Those from the north couldn't understand those from the south.
It is impossible to prove a negative. When you do something like failing to flip a taxi with a jet engine and claim that busts the myth that a taxi can be flipped with a jet engine, do you feel you're misleading the public as to how science and logic work?
I did all of those things on a very large team at a very large company for a very large project that was very late.
Wasn't called "Scrum" back then. Was called "Crunch Time". And the reason you have it is you've mismanaged your very large project over the months and now there's a buttload of stuff to do (called a "backlog or prioritized work") that you promised your bosses and the outside world.
Hardware vendors MUST write (or supply) drivers at least for Windows. That's the reality. Sure they could release specs and hope someone in the open source windows kernel driver world codes it up. But that ain't going to happen.
Having actually done windows driver co-development in partnership with a Japanese hardware vendor before, I can tell you they do consider interfaces and protocols into their hardware proprietry. Remember some "hardware" products are actually computers in and of themselves with mini OSs and complicated protocols for communication with the host PC. This isn't your father's PIO serial port stuff. Even as a true blue co-developing partner the best we could get were software APIs to a binary library that we had to link into our drivers.
So that means that because you have apps that aren't written in house, the business logic for the apps that *are* written in house must therefore be completely in the DB. That sucks in my opinion.
I totally agree with the private-office = more productivity thing in as far as that productivity refers to an individual working alone for periods of time.
I don't agree that offices are roughly the same cost to install as cubes. As others have said here, cubes are easier to light, ventilate and electrify. I think you also may use less space per person with cubes than offices.
But most importantly, remember with software developers you need to encourage a certain degree of chatter/communication as part of team productivity. With fewer barriers to communication between developers on a team (ie fewer walls and doors), you increase knowledge sharing, juniors learning from seniors, coordination.
If you have a decent team of people working together and isolated enough from the rest of the world, you can evolve amongst yourselves have to handle music and other noises. eg, come up with a "silence token" of some sort (like a stuffed bill gates doll) that you put on your monitor when people shuld be quiet. Or wearing headphones is a universal symbol of "quiet, please".
Also cubes allow people to work in broader more open spaces. eg, if you have a space with 15-20 foot ceilings and sunlight coming in properly, it can be a plus to take advantage of that over being in a box with an 8ft ceiling which may or may not have a window.
Of course it's a balance. I think management in our industry has been trying to find the sweet spot here forever.
Slashdot Mirror
I want to see the DRM code
>>>When the majority of the best and brightest in the country all lean towards a particular political philosophy, what should that tell you?
Don't know. I bet you could find examples in history of periods in time where the majority of the best and brightest in a country all leaned towards a particular political philosophy, and yet that political philosophy was terrible.
"guy" rolls out in conversation too easily as male gender tends to be the default in spoken english. So I'd cut some slack on the word "guy" (unless he was specific and said "no, really, hire a male etc")
So a large company. And a manager of a manager is saying hire a certain color. That's pretty sad.
>>You'd rather hire a Caucasian directly from Sweden or African directly from South Africa instead? Is this supposed to be pro-American?
I think he was saying he'd rather hire a Caucasian African directly from South Africa.
To me that's just politics of fear the corporate world. An employee can "sue the shit" (or try to) out of a company for anything, therefore the company requires every employee to insert an rfid anal probe before entering the building. I don't buy it. I work at a place where it's part of some employees' jobs to view soft and hard core porn. She'd have to complain to management first. -Then- management can warn the employee and escalate from there by starting to monitor the -specific- employee's traffic. It's back to the practice of trust your employees -first-; not, "we don't trust our employees from, therefore everyone gets an anal probe" or to quote the original article, "if you don't think your threat exists from the inside... your just not looking".
>>>So remember this when you bitch about security. The behavior above was detected by security tools. And this type of behavior in corporate America costs companies lots and reduces the security of your job. Security is to enable you to do your job AND is there to prevent the 1/100 bad asses from getting inside to do your company harm. And the opposite is true, to prevent the 1/100 bad asses you have hired from compromising your company.
>>>And if you don't think your threat exists from the inside, your either a very small trustworthy group or your just not looking.
Pretty much with you except that last sentence pisses me off. It's saying our employees are suspect up front and we've hired "security" to monitor and catch them. Go ahead and work to keep the bad stuff out, but I'd much prefer you stop watching every page I hit because I'm a suspect, and deciding which urls I should never be allowed to see. Give everyone decent net access and trust them first. Watch traffic for disruptive loads before asking the user "did you need to be downloading so much?" Then escalate from there based on the user's behavior.
I don't see any justification for setting up a system that effectively pages you if a user decides to look at a naked woman/man where the actual net effect is a handful of web requests among 10's of 1000's. (streaming a 500kbs video is different). Management that is doing it's job will have other other proper ways of measuring an employee's productivity/contribution.
I see about the root/reboot access, if your point is you don't want to have root access in order to reboot his systems. You don't need "root" to reboot windows. And your "IT" user account on his nix box can be given reboot ability without root. Though I concede having to reboot at all in order to get at the other system is overhead that 2 machines doesn't have.
While I'm all for having 2 machines over 1 dual boot, I don't follow your logic points for why 2 machines are better for you as the IT person...
* One side is always down, meaning network monitors need special work
If you give the guy 2 machines, one side could still be "always" down as he may turn on only the one he needs while working. The fact that he can work now with a dual boot machine means exactly this.
* Either both sides share one IP address, or each gets its own. Either figure out which one is running, or figure out which address to use.
If you gave him 2 machines, you'd have probably 2 IPs as well. Though not necessarily if he has one in use at a time. Maybe he switched the single network cable allowed in his cube when he switches machines.
* It requires physical intervention (or extraordinary hacks) to reboot remotely to the other OS
Why would you be remotely rebooting his machine? And changing the lilo ini file (or windows boot.ini) to default to the other os before rebooting doesn't seem like an "extraordinary hack" anyway. I'm sure you're probably a couple of clicks away from a boot-to-other-OS script/tool too.
* I can't just wax the whole thing if something goes wrong
And if you gave him 2 machines, you -can- just wax the whole thing?
* Rebooting implies root access for whoever is around
But if you gave him 2 machines, you'd still need this implied root access to reboot them.
* In short, they're a PITA
I'm not quite conviced.
How do you recommend planning for the eventual drive failure that happens in 2 years? Don't these raid controllers want the drives to be the exact same model? One of my drives is "failing" (going offline periodically but not dead yet). I bought it a couple years ago and don't think I can find it for sale anymore (at least new).
Seems like a home raid solution would want as a feature the ability to stick in incrementally bigger drives. Either that, or you buy 1 or 2 extra drives and figure that'll last you for 5-10 years and by then you'll want to swap the whole thing out with something that's 10x faster and 3x cheaper.
A lot tongue in cheek here...
Assuming there may be:
1. an evil ET that wants to affect our global network
2. a good ET that wants to affect our global network
And the proposition is to do new work on the SETI system beyond trying to detect a signal. The decision is then one of:
- New Work: to quarantine the net to make sure ET code cannot be executed
- New Work: to open the net to make sure ET code CAN be executed
Without addressing the affects of simply discovering ET, we have one of 5 possible outcomes:
A. status quo
B. humanity screwed
C. humanity advanced forever
D. humanity Misses The Boat (ala Pascal's Wager)
E. interstellar war
The normalized probabilities of the above outcomes are:
Opened Net Quarantined Net
---------- ---------------
A = 9/36 A = 12/36
B = 9/36 B = 8/36
C = 9/36 C = 8/36
D = 0/36 D = 4/36
E = 9/36 E = 4/36
These flow from the following possible events:
1. net opened, ET good: outcome C
2. net quarantined, ET good: ET penetrates net, goto 1
3. net quarantined, ET good: ET doesn't penetrate, D
4. net opened, ET evil: outcome B
5. net quarantined, ET evil: ET penitrates net, goto 4
6. net quarantined, ET evil: ET doesn't penetrate, goto 8
7. net opened, ET not there: outcome A
8. net quarantined, ET not there: goto 7
9. net opened, ET1 good, ET2 evil: outcome E
10. net quarantined, ET1 good, ET2 evil: both ETs penetrate net, goto 9
11. net quarantined, ET1 good, ET2 evil: neither penetrate net, goto 8
12. net quarantined, ET1 good, ET2 evil: ET1 penetrates net, goto 2
13. net quarantined, ET1 good, ET2 evil: ET2 penetrates net, goto 5
good post. but can't help levitizing here...
>>Chinese is not Chinese. I worked at a company that employed several Chinese engineers. While they could all read the same newspaper, they couldn't all talk to each other. Those from the south (Hong Kong and surrounding area) couldn't understand those from the north.
I worked for a company that employeed several California engineers. They could all read the same newspaper. Those from the north couldn't understand those from the south.
Thanks for making my point. THAT's the proper response to those questions by a "senior sys admin". An entry level would have used my answers.
Don't you consider knowing the things he was asking in the interview to be entry level:
that port 25 is smtp
that SSH is encrypted and telnet isn't
that you once forgot the root pwd on your own machine or helped a friend who had
And I know what he means when he says he sees resumes with "senior sys admin" on them who can't answer these.
That just means "no object that is not an object exists". It cancels out.
Umm, chapter 11 is a company reorganization, not personal bankruptcy.
It is impossible to prove a negative. When you do something like failing to flip a taxi with a jet engine and claim that busts the myth that a taxi can be flipped with a jet engine, do you feel you're misleading the public as to how science and logic work?
Which chapter 14?
s c_sup_01_16_10_14.html
Were you age discriminated?
http://www.law.cornell.edu/uscode/29/ch14.html
Or were you a whaler?
http://www.law.cornell.edu/uscode/html/uscode16/u
Skynet? No I rather think it sounds and looks more like WOPR.
How about a nice game of chess?
I did all of those things on a very large team at a very large company for a very large project that was very late.
Wasn't called "Scrum" back then. Was called "Crunch Time". And the reason you have it is you've mismanaged your very large project over the months and now there's a buttload of stuff to do (called a "backlog or prioritized work") that you promised your bosses and the outside world.
Being in Crunch Time is a *bad thing*.
Hardware vendors MUST write (or supply) drivers at least for Windows. That's the reality. Sure they could release specs and hope someone in the open source windows kernel driver world codes it up. But that ain't going to happen.
Having actually done windows driver co-development in partnership with a Japanese hardware vendor before, I can tell you they do consider interfaces and protocols into their hardware proprietry. Remember some "hardware" products are actually computers in and of themselves with mini OSs and complicated protocols for communication with the host PC. This isn't your father's PIO serial port stuff. Even as a true blue co-developing partner the best we could get were software APIs to a binary library that we had to link into our drivers.
So that means that because you have apps that aren't written in house, the business logic for the apps that *are* written in house must therefore be completely in the DB. That sucks in my opinion.
Downloaded, ran install. All looked happy. Run the app, instant dialog comes up saying something about can not run, refer to install.txt.
Look at install.txt, bunch of jibberish in there about installing java and dlls being in the same directory.
I'm running Windows XP.
I have Java installed.
I write Java code with Eclipse all the time.
Uninstall. Try again people when they have it right.
I totally agree with the private-office = more productivity thing in as far as that productivity refers to an individual working alone for periods of time.
I don't agree that offices are roughly the same cost to install as cubes. As others have said here, cubes are easier to light, ventilate and electrify. I think you also may use less space per person with cubes than offices.
But most importantly, remember with software developers you need to encourage a certain degree of chatter/communication as part of team productivity. With fewer barriers to communication between developers on a team (ie fewer walls and doors), you increase knowledge sharing, juniors learning from seniors, coordination.
If you have a decent team of people working together and isolated enough from the rest of the world, you can evolve amongst yourselves have to handle music and other noises. eg, come up with a "silence token" of some sort (like a stuffed bill gates doll) that you put on your monitor when people shuld be quiet. Or wearing headphones is a universal symbol of "quiet, please".
Also cubes allow people to work in broader more open spaces. eg, if you have a space with 15-20 foot ceilings and sunlight coming in properly, it can be a plus to take advantage of that over being in a box with an 8ft ceiling which may or may not have a window.
Of course it's a balance. I think management in our industry has been trying to find the sweet spot here forever.
I'm not