This is probably the big reason that commercial OSs are popular. When traditional businessmen hand over information to another company they can accompany that with a contract that can through the legal system leverage some pain against the other business if the information is used against the company rather than for it. How are you going to do that against open-source? It is their job to protect the company from the competition. If they fail to do that then they can lose thier paycheck. To convince them that it is an opportunity means you need a briefcase, a suit, and a good proposal, not an email or even a thousand emails...
I'm not being an arrogant snob. I've spent my time in minimum wage. There isn't much motivation to do anything. So far whenever we have needed an employee at the theater to look into anything they are nowhere to be found. I couldn't get a manager to talk to me, when I lost my credit card in the theater. You have the employees manning the registers who can't leave their place and the ticket takers who can't leave their place. Maybe it isn't the fact they are paid next to nothing but they haven't exactly inspired confidence that anything barring the building disappearing around them will bring them out of their little role.
That will teach me to respond to an email and respond to a post at the same time...
should read: the liability of their blocker failing to let an emergency call through when they promise to let them through.
Yep I'm sure that theaters who won't pay for someone to stay in the theater to prevent disruption from its patrons are going to expose themselves to the liability of what their blocker not letting an emergency call through.
For a long time I agreed with this but then I realized the last place I want my phone blocked in an emergency is someplace with minimum wage workers (and probably managers.) And as obnoxious as a phone is in the theater, those are the same idiots who talk to the people they come with during the film anyways.
Also like convicts, the students are not allowed recording devices to document bullying because recording devices are disruptive. I'm still unclear how bullying is unbelievable but retaliation is intolerable.
Re:Certainly beats carrying the stuff up
on
Beer Lift
·
· Score: 1
When was the proper time to have resolved bullying? It has been an issue for years and has resulted in some pretty nasty retaliation. Noone has cared about it till someone stuck cyber in front of it. Thats it I'm adding cyber to the front of my name so everyone cares about me...
Oh we had are fair share of uselessness but we had plenty of useful stuff too. The problem is although pretty narrow for an applied science it is still pretty broad. We spent our first few classes learning to program (with plenty of bad real world habits with an academic purpose), then we expanded out. I took a database class, a couple of classes close to the hardware, an operating systems class with assignments in proper multithreading, an assembly class, some more theoretical mathy stuff. It was a good base to build from. In several of my classes I had to write papers and review current material from the IEEE and ACM journals. It is nice to have professors with day jobs in industry.
And you forgot the most important thing, now they can port linux to flash and appease all the slashdot haters with one question and one answer: Does it run linux? and Yes, it does.
And before someone responds to this as if it were a serious post: I very sincerely hope this is and will remain a joke.
Yep experience matters and some times in a bad way. A can-do attitude? Yes. Technical aptitude? Yes. Experience? Maybe. If a person isn't willing to work with the team then you don't want them on your team. I've met plenty of people that are unwilling to listen to a good answer from a young person because the young person is young and by extension inexperienced. But that young person is closer to school, meaning they learned from not just your mistakes but the mistakes of the industry over the past 30 years and very likely the youngsters were playing with real-world code long before they ever could have counted it experience. Not that that is all there is to experience but don't ignore the youngsters.
I've been writing software for nearly 15 years and real world stuff for almost 10 and I was supporting friends and relatives with IT stuff long before that. On my resume you see 5 years professional employment. Plenty of kids getting out of school now have been writing stuff since I started, have no "professional" experience, but have been cutting their teeth on open source for years.
That is a tough call. It could be the code is doing processing on the zip-code at 30 hz and it is important to make that trade off and just deal with the formatting on display even with the potential for error if someone else displays it. Maybe not for zip code, but I've had similar cases where senior developers wanted to use string where they just didn't need to. I think the real key is having a developer that can make a sane choice there, back up their decision making process, and deal with it when their solution isn't the best one or even the chosen one.
Agile isn't about providing methodologies to deal with changing specs; it is about tying the stakeholders into the project so they know when, why, and how much they can change their product and providing an open communication structure to rapidly shift to new requirements. Agile change management: Put your customer on your team and don't overdesign your system because it may change.
I agree that those two rules are useful, but I think that traditional leans heavy on #1 and agile leans heavy on #2 and a successful manager knows where to put the emphasis to make a successful(not necessarily perfect) project.
Must be nice to live in a world with clearly defined requirements. Traditional processes are a big fail if you are dealing with customers who won't know your full requirements until 90% of your development time is gone. Here is my separation between the two methodologies:
1) Traditional - get everything working, time and money are flexible(to a degree)
2) Agile - Hit our deadline, how much needs to be working can be changed as we go along(to a degree)
Even the approaches by the customers aren't the same. If you think that every project is a nail because you have your traditional hammer, you are at best a bad software engineer and I don't want to be on your project. Conversely agile doesn't fit everything either. If you can't be bothered to know all the tools relevant to your job, you have already been promoted too high for the team's good.
Good, fast, cheap. Choose two. is an good old adage. You aren't doing things wrong if your customer wants the last two and you are giving it to him. You are only being bad project managers when you aren't matching your customer's set.
You need to update your economics model. Monopolies are the natural product of an increasing demands industry like software. They aren't bad as long as there is room in the market for alternatives to provide a better fit product, which are clearly present with both Linux and Mac OS surviving. Ever since I read the following paper, I've gotten a bit leary on how much we should attack the natural formations of the market.
http://www.santafe.edu/~wbarthur/Papers/Pdf_files/HBR.pdf
This is the problem with not properly promoting scientific education within American schools. If you can't get good scientists internally then you are putting your secure projects at risk.
Quite frankly those who will suffer from reduced education are not the people Tennessee is interested in having in its state, because they are in a much lower tax bracket than the artists and more importantly the executives...
Slashdot Mirror
This is probably the big reason that commercial OSs are popular. When traditional businessmen hand over information to another company they can accompany that with a contract that can through the legal system leverage some pain against the other business if the information is used against the company rather than for it. How are you going to do that against open-source? It is their job to protect the company from the competition. If they fail to do that then they can lose thier paycheck. To convince them that it is an opportunity means you need a briefcase, a suit, and a good proposal, not an email or even a thousand emails...
Tell that to the RIAA.
to see Shatner can still find work.
They say stop in the US but you probably already knew that...
3 is get caught by the media in this case.
I'm not being an arrogant snob. I've spent my time in minimum wage. There isn't much motivation to do anything. So far whenever we have needed an employee at the theater to look into anything they are nowhere to be found. I couldn't get a manager to talk to me, when I lost my credit card in the theater. You have the employees manning the registers who can't leave their place and the ticket takers who can't leave their place. Maybe it isn't the fact they are paid next to nothing but they haven't exactly inspired confidence that anything barring the building disappearing around them will bring them out of their little role.
That will teach me to respond to an email and respond to a post at the same time...
should read: the liability of their blocker failing to let an emergency call through when they promise to let them through.
Yep I'm sure that theaters who won't pay for someone to stay in the theater to prevent disruption from its patrons are going to expose themselves to the liability of what their blocker not letting an emergency call through.
For a long time I agreed with this but then I realized the last place I want my phone blocked in an emergency is someplace with minimum wage workers (and probably managers.) And as obnoxious as a phone is in the theater, those are the same idiots who talk to the people they come with during the film anyways.
Also like convicts, the students are not allowed recording devices to document bullying because recording devices are disruptive. I'm still unclear how bullying is unbelievable but retaliation is intolerable.
Looking at the lifts where would you be?
When was the proper time to have resolved bullying? It has been an issue for years and has resulted in some pretty nasty retaliation. Noone has cared about it till someone stuck cyber in front of it. Thats it I'm adding cyber to the front of my name so everyone cares about me...
Oh we had are fair share of uselessness but we had plenty of useful stuff too. The problem is although pretty narrow for an applied science it is still pretty broad. We spent our first few classes learning to program (with plenty of bad real world habits with an academic purpose), then we expanded out. I took a database class, a couple of classes close to the hardware, an operating systems class with assignments in proper multithreading, an assembly class, some more theoretical mathy stuff. It was a good base to build from. In several of my classes I had to write papers and review current material from the IEEE and ACM journals. It is nice to have professors with day jobs in industry.
And you forgot the most important thing, now they can port linux to flash and appease all the slashdot haters with one question and one answer: Does it run linux? and Yes, it does.
And before someone responds to this as if it were a serious post: I very sincerely hope this is and will remain a joke.
Crysis 2, here I come...
Yep experience matters and some times in a bad way. A can-do attitude? Yes. Technical aptitude? Yes. Experience? Maybe. If a person isn't willing to work with the team then you don't want them on your team. I've met plenty of people that are unwilling to listen to a good answer from a young person because the young person is young and by extension inexperienced. But that young person is closer to school, meaning they learned from not just your mistakes but the mistakes of the industry over the past 30 years and very likely the youngsters were playing with real-world code long before they ever could have counted it experience. Not that that is all there is to experience but don't ignore the youngsters.
I've been writing software for nearly 15 years and real world stuff for almost 10 and I was supporting friends and relatives with IT stuff long before that. On my resume you see 5 years professional employment. Plenty of kids getting out of school now have been writing stuff since I started, have no "professional" experience, but have been cutting their teeth on open source for years.
That is a tough call. It could be the code is doing processing on the zip-code at 30 hz and it is important to make that trade off and just deal with the formatting on display even with the potential for error if someone else displays it. Maybe not for zip code, but I've had similar cases where senior developers wanted to use string where they just didn't need to. I think the real key is having a developer that can make a sane choice there, back up their decision making process, and deal with it when their solution isn't the best one or even the chosen one.
Agile isn't about providing methodologies to deal with changing specs; it is about tying the stakeholders into the project so they know when, why, and how much they can change their product and providing an open communication structure to rapidly shift to new requirements. Agile change management: Put your customer on your team and don't overdesign your system because it may change.
I agree that those two rules are useful, but I think that traditional leans heavy on #1 and agile leans heavy on #2 and a successful manager knows where to put the emphasis to make a successful(not necessarily perfect) project.
Someone should take his /. card.
Must be nice to live in a world with clearly defined requirements. Traditional processes are a big fail if you are dealing with customers who won't know your full requirements until 90% of your development time is gone. Here is my separation between the two methodologies:
1) Traditional - get everything working, time and money are flexible(to a degree)
2) Agile - Hit our deadline, how much needs to be working can be changed as we go along(to a degree)
Even the approaches by the customers aren't the same. If you think that every project is a nail because you have your traditional hammer, you are at best a bad software engineer and I don't want to be on your project. Conversely agile doesn't fit everything either. If you can't be bothered to know all the tools relevant to your job, you have already been promoted too high for the team's good.
Good, fast, cheap. Choose two. is an good old adage. You aren't doing things wrong if your customer wants the last two and you are giving it to him. You are only being bad project managers when you aren't matching your customer's set.
You need to update your economics model. Monopolies are the natural product of an increasing demands industry like software. They aren't bad as long as there is room in the market for alternatives to provide a better fit product, which are clearly present with both Linux and Mac OS surviving. Ever since I read the following paper, I've gotten a bit leary on how much we should attack the natural formations of the market. http://www.santafe.edu/~wbarthur/Papers/Pdf_files/HBR.pdf
Inadvertant and Casual attempts?
Oops. I tripped over my computer and hacked your system. Sorry.
[sic] - strafing incoming chair
This is the problem with not properly promoting scientific education within American schools. If you can't get good scientists internally then you are putting your secure projects at risk.
Quite frankly those who will suffer from reduced education are not the people Tennessee is interested in having in its state, because they are in a much lower tax bracket than the artists and more importantly the executives...