Follow the trail of money to the overly expensive tests done on relatively inexpensive machines, funded by your premiums to in$urance companies and your copayment$.
Good for the programmers. 8x10 cubicle with it's own bathroom. Wired for high speed cablemodem. Has a door that closes so nobody can sneak up behind you while you are working. Good for the managers. Control smoke breaks and general working hours from a master control system. Video surveillance is taken to a whole new level.
I do agree - we need language to think about things. Similarly, we use the language of physics math to describe and understand things more precisely. If we don't have the language to think about it, it becomes difficult to describe.
Personally, I've found that it's a combination of drawing and words to most effectively communicate a concept.
Most of the software failures that I've witnessed are the result of either
1) Poor quality - eg Lots of code, bad / undefined interactions between the components. Usually results in loss of data 2) Poor user experience - software performs complicated task well, users aren't able to adapt to using the capabilities 3) Misunderstanding of the problem solving opportunity - System solves the problem as designed, however rather than automating an old stupid process to take less time, the old stupid process could be re-engineered to bring added value (generate revenue, save lives, retain employees, etc) to the organization
Fixing the first requires someone that is technical, but not necessarily that technical. Fixing the Last requires someone that understands the business. They probably aren't technical. Fixing the Middle requires someone that understand user experience, often an engineer with some empathy, or a business person that is technical.
Good technology requires both technical and non technical contributions for success. That combination is rarer than you would think.
Since this is slashdot - let's talk about the new tech systems:
So will mental health professionals be required to do a check against gun owner databases? Will a mental illness database need to be created so that potential gun buyers can be screened at purchase time? How about house-holding - if someone in the same residence is a registered gun owner, will they be forced to surrender their weapons?
Until we have an open source printer that can be forked to print another printer which can be used to print the chip and the board, we won't be truly open.
Pretty much, no matter what you do, even if you build a wiki, have everything amazingly documented, and are in the top 10% of all shops in terms of best practices, the new person will find reasons to find fault with what you have done. Servers will be rebuilt, upgrades will happen, etc. A year from now, things will either be better off than when you were running them or worse off, but the reality is that re-use just doesn't happen enough in our industry. So if re-use isn't happening, then it's really just up to the quality of the individual.
I'm not sure at what age I learned that when I put my baby bottle down that it wouldn't mysteriously float in the air, but I suspect that I wasn't educated on gravity, but in fact learned of the existence of gravity through observation and tests.
Outside of perhaps the favorable mutation's of bacteria to become antibiotic resistant, I don't have a significant opportunity to observe and test evolution.
I find it bizarre how emotional both sides of the evolutionary debate get. Either take the time to do real science or go watch TV.
Later that day Tim used some toilet paper and noted that although the manufacturer said that it was a soft as a cloud, cloud computing is not ready for the toilet yet.
Actually, it's the corporations here in the USA that have conditioned the consumers into buying unlimited-service-for-fixed-fee per billing period contracts. Corporations are addicted to committed revenue - and fixed fee pricing is a great way to get it. The usual 80/20 rule applies where they wouldn't offer the fixed fee at a particular pricing point unless they make added profit on the under utilization by 80% of the subscribers.
In my 20 years experience of supplying IT.
If your business is small - mid sized (under 2000 employees). And you don't have custom apps. Between 100:1 and 150:1 will provide decent support for computers and packaged apps.
If your business is larger often, to reduce costs, you will have help desks and standardized pc / notebook builds. People will have to navigate through a bureaucracy to get a non-standards app on their pc. You can drive the ratio down to 500:1.
On the other hand, if you are in a business where information is your product (banking, library, database), that will drive the ratio the other way. Anywhere between 2:1 and 20:1.
It really just depends on your business. You need to remember that IT resources are an expense, just as much as servers, and network equipment and paper for the printers. So if the business model makes sense, and the technology work - life is good.
I do agree that many patents these days (eg. one-click) are not true inventions and stifling the industry. But you can't expect to agree with your employer on everything. I am assuming that, like me, you need a pretty continuous job and paycheck thereof. I predict that 99% of the time, the fact that you have your name on a patent, will be looked on in favor of you as you apply for your next job.
So do your job. Feel free to look for your next job on your own time if it's that bad where you are.
The text in this posting is a derivative of Common Sense (patent pending).
First - let me give you my own perspective.
I recommend having each subsystem log in such a fashion that you can easily grep to include or ignore that subsystem. For example for one package the following LVLx messages were the first four characters as follows:
LVL1 - basic startup and shutdown info ( a few lines per run)
LVL2 - Interactions with the database
LVL3 - Interactions with the file system
LVL4 - Detailed database interactions including each sql statement
LVL5 - amazingly verbose debug information including memory and variable allocations
In almost all cases, I recommend being able to set each level on or off. Your sysadmin (maybe yourself) will appreciate that ability.
If appropriate, I recommend an 'audit' record after each completed or aborted transaction. EG - after every order or every user change or whatever is important for accountability / business activity monitoring purposes. This is the original question.
didn't those subscribers sign up for unlimited usage?
someone's getting sued.... For service contracts with the 'terms may change clause' when the terms change, you are typically free to leave the service without penalty.
As far as being sued goes - If I were an ISP, I would think this makes sense. It's easier to defend limits that are the same for everyone, vs. arbitrarily notifying subscribers who happen to piss off a network admin for interfering with their bittorrent download.
Believe it or not, as a code monkey, you probably have better technical skills to handle management, than most of the management types around you. Math and sorting, are used in most management decisions that need to be made. That being said, you may need to develop other skills such as organizational, interpersonal communication, decision making, risk assessment, etc. The existing managers are your best sources of information as to what may be valued in management by your organization.
Have lunch with your management peers and superiors. Listen carefully for things that they complain about the organization. Also listen to them boast about their own successes. I hate to say it, but your success as a manager will be to take the problems of the organization and fix or work around them. You'll also do well by being better than they are. This in turn will be rewarded with increased scope of management. Eventually you'll be in a position to manage managers.
Next, have lunch with your team. From a purely practical standpoint, the best manager, get his team to perform the most efficiently. Get to know your team, what makes them tick. Use this knowledge to lead them. Celebrate their successes at least as often as you correct their transgressions. I prefer to lead by example - eg. if extra work needs to be done on a project, they see me working 2 extra hours for every extra hour I ask for.
Expect 10-20 percent of your time to be somewhat 'wasted' with routine stuff such as approving time sheets, vacations, people issues, budgets, planning, and providing documents to your boss that will never be used for anything.
I recommend materials by Steven Covey for general organization and decision making skills.
Slashdot Mirror
Follow the trail of money to the overly expensive tests done on relatively inexpensive machines, funded by your premiums to in$urance companies and your copayment$.
But if you do brick it, for the RMA, do you send the whole human back with the pacemaker, or do you extract the pacemaker so you can save on shipping?
Clearly we should first ask for is an IDE running infinitely smart and fast on that infinitely fast computer.
According to your prescription history, you haven't filled your proangst-xl in over a year. No wonder your are feeling low on angst.
Good for the programmers. 8x10 cubicle with it's own bathroom. Wired for high speed cablemodem. Has a door that closes so nobody can sneak up behind you while you are working.
Good for the managers. Control smoke breaks and general working hours from a master control system. Video surveillance is taken to a whole new level.
This applies to managers, engineers and engineers that have taken management roles.
I do agree - we need language to think about things. Similarly, we use the language of physics math to describe and understand things more precisely. If we don't have the language to think about it, it becomes difficult to describe.
Personally, I've found that it's a combination of drawing and words to most effectively communicate a concept.
Most of the software failures that I've witnessed are the result of either
1) Poor quality - eg Lots of code, bad / undefined interactions between the components. Usually results in loss of data
2) Poor user experience - software performs complicated task well, users aren't able to adapt to using the capabilities
3) Misunderstanding of the problem solving opportunity - System solves the problem as designed, however rather than automating an old stupid process to take less time, the old stupid process could be re-engineered to bring added value (generate revenue, save lives, retain employees, etc) to the organization
Fixing the first requires someone that is technical, but not necessarily that technical.
Fixing the Last requires someone that understands the business. They probably aren't technical.
Fixing the Middle requires someone that understand user experience, often an engineer with some empathy, or a business person that is technical.
Good technology requires both technical and non technical contributions for success. That combination is rarer than you would think.
Since this is slashdot - let's talk about the new tech systems:
So will mental health professionals be required to do a check against gun owner databases? Will a mental illness database need to be created so that potential gun buyers can be screened at purchase time? How about house-holding - if someone in the same residence is a registered gun owner, will they be forced to surrender their weapons?
How about posting some pictures of the milky way? I've only barely seen it once while on Hilton Head island.
http://www.dslreports.com/forum/r27484816-DIY-3G-4G-LTE-Yagi
http://bcbj.org/antennae/lte_yagi_diy.htm
Until we have an open source printer that can be forked to print another printer which can be used to print the chip and the board, we won't be truly open.
Would the printer spec qualify for GPL or LGPL?
If you live in the US (the posting implies that you do) and you can't resolve the issue with AT&T, then I would file a FCC Complaint.
You can even file the complaint online.
That said, 20%, is not a huge difference - is it worth fighting over?
Remember when people used to be concerned that when buying a 10 Gig hard drive, it wasn't really 10 Gigabytes?
(I hope you weren't expecting me to make your decision for you.)
I may answer the phone, and in general, talking to me on the phone is usually unpleasant, even bordering on unsafe.
He'd be smokin hot for at least a second or two until he vaporized.
Pretty much, no matter what you do, even if you build a wiki, have everything amazingly documented, and are in the top 10% of all shops in terms of best practices, the new person will find reasons to find fault with what you have done. Servers will be rebuilt, upgrades will happen, etc. A year from now, things will either be better off than when you were running them or worse off, but the reality is that re-use just doesn't happen enough in our industry. So if re-use isn't happening, then it's really just up to the quality of the individual.
I'm not sure at what age I learned that when I put my baby bottle down that it wouldn't mysteriously float in the air, but I suspect that I wasn't educated on gravity, but in fact learned of the existence of gravity through observation and tests.
Outside of perhaps the favorable mutation's of bacteria to become antibiotic resistant, I don't have a significant opportunity to observe and test evolution.
I find it bizarre how emotional both sides of the evolutionary debate get. Either take the time to do real science or go watch TV.
Of course if I was actually God's proxy, I would have had first post.
Later that day Tim used some toilet paper and noted that although the manufacturer said that it was a soft as a cloud, cloud computing is not ready for the toilet yet.
Actually, it's the corporations here in the USA that have conditioned the consumers into buying unlimited-service-for-fixed-fee per billing period contracts. Corporations are addicted to committed revenue - and fixed fee pricing is a great way to get it. The usual 80/20 rule applies where they wouldn't offer the fixed fee at a particular pricing point unless they make added profit on the under utilization by 80% of the subscribers.
I don't know why she swallowed the fly...perhaps she'll die.
In my 20 years experience of supplying IT. If your business is small - mid sized (under 2000 employees). And you don't have custom apps. Between 100:1 and 150:1 will provide decent support for computers and packaged apps. If your business is larger often, to reduce costs, you will have help desks and standardized pc / notebook builds. People will have to navigate through a bureaucracy to get a non-standards app on their pc. You can drive the ratio down to 500:1.
On the other hand, if you are in a business where information is your product (banking, library, database), that will drive the ratio the other way. Anywhere between 2:1 and 20:1.
It really just depends on your business. You need to remember that IT resources are an expense, just as much as servers, and network equipment and paper for the printers. So if the business model makes sense, and the technology work - life is good.
I do agree that many patents these days (eg. one-click) are not true inventions and stifling the industry. But you can't expect to agree with your employer on everything. I am assuming that, like me, you need a pretty continuous job and paycheck thereof. I predict that 99% of the time, the fact that you have your name on a patent, will be looked on in favor of you as you apply for your next job.
So do your job. Feel free to look for your next job on your own time if it's that bad where you are.
The text in this posting is a derivative of Common Sense (patent pending).
First - let me give you my own perspective. I recommend having each subsystem log in such a fashion that you can easily grep to include or ignore that subsystem. For example for one package the following LVLx messages were the first four characters as follows:
LVL1 - basic startup and shutdown info ( a few lines per run)
LVL2 - Interactions with the database
LVL3 - Interactions with the file system
LVL4 - Detailed database interactions including each sql statement
LVL5 - amazingly verbose debug information including memory and variable allocations
In almost all cases, I recommend being able to set each level on or off. Your sysadmin (maybe yourself) will appreciate that ability.
If appropriate, I recommend an 'audit' record after each completed or aborted transaction. EG - after every order or every user change or whatever is important for accountability / business activity monitoring purposes.
This is the original question .
As far as being sued goes - If I were an ISP, I would think this makes sense. It's easier to defend limits that are the same for everyone, vs. arbitrarily notifying subscribers who happen to piss off a network admin for interfering with their bittorrent download.
Believe it or not, as a code monkey, you probably have better technical skills to handle management, than most of the management types around you. Math and sorting, are used in most management decisions that need to be made. That being said, you may need to develop other skills such as organizational, interpersonal communication, decision making, risk assessment, etc. The existing managers are your best sources of information as to what may be valued in management by your organization.
Have lunch with your management peers and superiors. Listen carefully for things that they complain about the organization. Also listen to them boast about their own successes. I hate to say it, but your success as a manager will be to take the problems of the organization and fix or work around them. You'll also do well by being better than they are. This in turn will be rewarded with increased scope of management. Eventually you'll be in a position to manage managers.
Next, have lunch with your team. From a purely practical standpoint, the best manager, get his team to perform the most efficiently. Get to know your team, what makes them tick. Use this knowledge to lead them. Celebrate their successes at least as often as you correct their transgressions. I prefer to lead by example - eg. if extra work needs to be done on a project, they see me working 2 extra hours for every extra hour I ask for.
Expect 10-20 percent of your time to be somewhat 'wasted' with routine stuff such as approving time sheets, vacations, people issues, budgets, planning, and providing documents to your boss that will never be used for anything.
I recommend materials by Steven Covey for general organization and decision making skills.
Good luck!