The botnet owners have large lists of likely usernames/passwords and IP addresses to try. In the past they just assigned a bot to try out a complete list of usernames/passwords to try for a range of IP addresses. Now, they just give each bot a range of usernames/passwords for a complete list of IP addresses. It doesn't affect the processing time required, but makes it harder to ban hosts.
Some fibre-optic cables have their own power supplied by copper wires to provide electricity to the optic repeater units. I believe they are still electrically powered.
Their major strength seemed to be that they could provide a complete single vendor solution for corporations. A company could buy the servers, workstations, graphics cards, device drivers and OS all from the same company. If there was ever a problem such as a memory leak or device driver crash, all the staff would be in-house to get the problem fixed. This is the same service that their other competitors used to offer until they switched to Microsoft.
In California it's three years. It's not particularly fun being abroad, and getting a notice from the bank giving you a weeks notice to make a transaction or the money will be seized.
It might be just my imagination, but whenever there is a large earthquake in one region of the Earth, there always seem to be two other earthquakes in longitudes +/-120 degrees from the original earthquake within a month. Does the shifting of the crust have any effect on the centre of gravity of rotation?
A more scientific conclusion would have been to use error bars in his prediction; "There is a 95% chance that an earthquake on this date, and a 99% that it will occur within seven days after this date".
I've heard similar stories from friends. One couple moved out to France to retire - the guy was lucky enough to have a pension scheme that allowed him to take early retirement at 60. Bought their dream cottage, renovated it, had friends at church and ran their own bar/restaurant. Then he was diagnosed with lung cancer and eventually passed away.
Another couple, the lady slipped on a staircase while going downstairs and hit her head against one of the leading edges of the steps. She thought nothing of it, then several hours later, was seriously ill and taken to hospital.
It just seems so cruel to have worked all those years to achieve a dream, and then have it taken away...
Management dreams of cheap replaceable labor working on an assembly line. After all assembling cars and developing highly sophisticated software have so much in common!
Trying to remain an experienced software developer seems to be like a Sumo wrestling match. You are trying to remain in the center of the ring, constantly gaining skills to feed the family and pay the mortgage. All the time, shareholders (investment companies/bankers) and directors are all trying to reduce costs by trying to turn skills into commodities, and taking on as many staff as possible. Universities are determined to make as much money as possible by churning out as many programmers as possible, all trying to pay off their debts. In between all these forces (Push and Pull from the Peter Principle) are the software developers.
I've always wondered, how do open source games (Especially FPS ones) deal with cheating.
Games like bzflag allow the admin of a map to ban players for a particular amount of time if they start breaking the rules. Some of the worst activities are:
Wall-walking - taking advantage of the latency between the server and client to walk through walls. Happens when someone tries to take a screensave while moving fast.
Team-killing (TK'ing) - shooting the other members of your team just for fun. Can happen by accident if there are ricochets in a complex environment.
Flag-runner - taking your teams flag and running off with it to the middle of the map or another team's camp. Sometimes done by accident if a spawn occur right on the base or on a "safe place" for the flag.
Team bots - players having a number of bots with them as well, which don't play very well.
Bad language - Having someone constantly repeating the same political statement over and over again.
I had a friend in college who wrote some spreadsheet templates to help manage oil storage tanks. His system kept track of dates of filling, draining, age, litres added, removed, type of oil and so on. It genuinely helped his customers save money as they wouldn't forget about slightly filled tanks which would end up being drained rather than used.
Next thing he knew, another guy was selling the exact same spreadsheet templates but with a couple of the columns swapped around. There really wasn't anything he could do.
Another story was about a guy who wrote an expert system for fixing the motors of train set engines. His system required that you measure the voltages and currents through different parts of the motor. His expert system would then tell you what was wrong with the motor. He was giving this away for free to hobbyists, until someone else figured out that the same expert system would help identify faults with industrial winches and motors, and was charging consultancy fees.
That is far too many levels. Cut out the software/hardware architect, they are pretty useless with a skilled force anyway.
That was with an embedded systems project with a medium sized company - employing a number of people from a hardware board designer working with CPU's, network controller chips device a device driver programmer, one team leader, a project manager and a couple of software engineers. Core library staff included architects and a director.
With software houses like game companies, the smallest will just have three staff; graphics programmer, artist-animator, level-editor/audio programmer.
Pair programming is more to get the senior person train up the junior person and extract their knowledge, then shuffle them up into management, so they can't pass the knowledge onto anyone else:
EET: What was the culture of the EE like back then?
Bosson: They were gurus, and you needed the OK to talk to those guys. You had to be very shy and approach them [as you would] wild animals. Our wish was to try to grab as much as we could from them. But they were guys who were protecting their jobs, too. You had to have a lot of white and gray hair, Monsieur Le Engineer.
You were trying to observe them because you wanted to get as much as you could from their behavior, their approach, their way of working. It was like [being] with a teacher. A teacher is ready to share with you. But those EEs -- as with the wild animal, you had to get close to them step by step, watching their emotions step by step.
If you watch large teams of programmers, the management actually force the developers to write slow code, claiming that maintainability is more important than any other factor!
I've worked in a couple of companies like that - usually the programmers were limited to working on technology that the management (ex-programmers) were familiar with. Then also, management didn't want the programmers learning "high-demand skills" (ie. hardware programming) that would boost the chances of their staff leaving to a better paid environment. Or there was the politics of favoritism where the directors wanted to give a leg up the seniority ladder to their best mate. Everyone else who was qualified "didn't have the skills or was busy on another project" while of course their mate "had applied at just the right time with the right skills". Another problem was that if management gave only one programmer a new hardware system, then everyone else would get cheesed off that they were falling behind that they would leave (eg. a CPU porting project). Alternatively, there are also quota based systems which would piss off one nationality off another.
Invariably these companies gain a bad reputation and implode after a slow death spiral, where they are forced to lay off staff and sell off equipment to cover debts. With fewer staff, they can't take on new projects, and the cycle continues until the last project is cancelled.
Even back in the late 1980's it was obvious that thin pyramid management structures were being toppled through downsizing. Some of my relatives took early retirement from companies due to this. Long chains of management over 15 levels deep were definitely going out of fashion: director, assistant director, senior manager, assistant senior manager, supervising manager, project manager, assistant project manager, team leader, lead programmer, senior programmer, programmer, junior programmer and intern.
Start up companies just a far simpler structure: director, software/hardware architect, team leader, senior programmer and programmer.
Everyone knew about the hazards of "dead man's shoes" and how important it was to keep your skills up to date or lose your career.
Even with monochrome, that would be enough to read text, recognize faces, walk down a pavement, take public transport, read timetables and do shopping without any of these requiring assistance.
Contact your local university, ask them if it would be possible to file a technical report with a departmental archive... that's what all university departments do when submitting papers; submit the research as a technical report, then send it off for consideration for publication. Even if the paper is turned down, you still have the technical report filing.
I would guess that they would be the same transcendental functions supported by the other shader languages; Cg, GLSL and Renderman; sine, cosine, tan, asin, acos, atan, sinh, cosh, tanh, if not sincos as well. They are also going to need exp, log, exp2, log2, exp10 and log10. All of these will be required for statistical modeling of texture, 3D animation and image processing. Maybe they won't be vectorized, or maybe it will be possible to treat each 16-element vector as a matrix.
The central fovea of the human retina has the highest density of cones sensitive to color, while peripheral vision is populated by rods which are sensitive to light intensity only.
For somebody with normal vision, redirecting light from the fovea to peripheral vision isn't going to have any benefit, but for someone with no central vision who cannot perceive texture (ie.text) or color, regaining the ability to read text is going to be of great benefit.
That has been happening for the past fifteen years. Professional application developers could only support a handful of OS's. Back in the mid 1990's, these would be the UNIX workstation vendors; IBM, Sun, SGI, DEC, HP. Then when Windows NT came out, developers were forced to drop one or more UNIX workstation vendors, whichever was the least used OS and support Windows NT. Once the other Linux OS's were able to get certified 3D graphics boards and drivers, that was another couple of traditional UNIX OS's that were pushed out. It looks like it will be a world where there will be Solaraix, Linux and Windows.
French shops and supermarkets open around 8.00am or 9.00am, have two hours lunchbreaks from 12pm to 2pm, but they work later until around 7.00pm or 8.00pm. Annoying if you are on holiday because you then have to schedule your day around the lunchbreak; shops in the morning, supermarket in the afternoon. But it is good for the office workers.
Slashdot Mirror
Many old movies are being lost due to film decay, many of which are stored only on a single reel made from acetate compounds. Then there are fires in warehouse, museums and the odd tunneling company causing archives to collapse.
The botnet owners have large lists of likely usernames/passwords and IP addresses to try. In the past they just assigned a bot to try out a complete list of usernames/passwords to try for a range of IP addresses. Now, they just give each bot a range of usernames/passwords for a complete list of IP addresses. It doesn't affect the processing time required, but makes it harder to ban hosts.
Some fibre-optic cables have their own power supplied by copper wires to provide electricity to the optic repeater units. I believe they are still electrically powered.
Perhaps they should use the data center as a means of heating up water for the staff rooms, or have a feedback pipe back to the water mains supply.
Their major strength seemed to be that they could provide a complete single vendor solution for corporations. A company could buy the servers, workstations, graphics cards, device drivers and OS all from the same company. If there was ever a problem such as a memory leak or device driver crash, all the staff would be in-house to get the problem fixed. This is the same service that their other competitors used to offer until they switched to Microsoft.
In California it's three years. It's not particularly fun being abroad, and getting a notice from the bank giving you a weeks notice to make a transaction or the money will be seized.
Alternatively:
C&C - Command and Conquer - a strategic battle game.
It might be just my imagination, but whenever there is a large earthquake in one region of the Earth, there always seem to be two other earthquakes in longitudes +/-120 degrees from the original earthquake within a month. Does the shifting of the crust have any effect on the centre of gravity of rotation?
A more scientific conclusion would have been to use error bars in his prediction; "There is a 95% chance that an earthquake on this date, and a 99% that it will occur within seven days after this date".
I've heard similar stories from friends. One couple moved out to France to retire - the guy was lucky enough to have a pension scheme that allowed him to take early retirement at 60. Bought their dream cottage, renovated it, had friends at church and ran their own bar/restaurant. Then he was diagnosed with lung cancer and eventually passed away.
Another couple, the lady slipped on a staircase while going downstairs and hit her head against one of the leading edges of the steps. She thought nothing of it, then several hours later, was seriously ill and taken to hospital.
It just seems so cruel to have worked all those years to achieve a dream, and then have it taken away...
Management dreams of cheap replaceable labor working on an assembly line. After all assembling cars and developing highly sophisticated software have so much in common!
Trying to remain an experienced software developer seems to be like a Sumo wrestling match. You are trying to remain in the center of the ring, constantly gaining skills to feed the family and pay the mortgage. All the time, shareholders (investment companies/bankers) and directors are all trying to reduce costs by trying to turn skills into commodities, and taking on as many staff as possible. Universities are determined to make as much money as possible by churning out as many programmers as possible, all trying to pay off their debts. In between all these forces (Push and Pull from the Peter Principle) are the software developers.
Did somebody write that all by themselves or did they use an automatic speech generator?
I've always wondered, how do open source games (Especially FPS ones) deal with cheating.
Games like bzflag allow the admin of a map to ban players for a particular amount of time if they start breaking the rules. Some of the worst activities are:
Wall-walking - taking advantage of the latency between the server and client to walk through walls. Happens when someone tries to take a screensave while moving fast.
Team-killing (TK'ing) - shooting the other members of your team just for fun. Can happen by accident if there are ricochets in a complex environment.
Flag-runner - taking your teams flag and running off with it to the middle of the map or another team's camp. Sometimes done by accident if a spawn occur right on the base or on a "safe place" for the flag.
Team bots - players having a number of bots with them as well, which don't play very well.
Bad language - Having someone constantly repeating the same political statement over and over again.
I had a friend in college who wrote some spreadsheet templates to help manage oil storage tanks. His system kept track of dates of filling, draining, age, litres added, removed, type of oil and so on. It genuinely helped his customers save money as they wouldn't forget about slightly filled tanks which would end up being drained rather than used.
Next thing he knew, another guy was selling the exact same spreadsheet templates but with a couple of the columns swapped around. There really wasn't anything he could do.
Another story was about a guy who wrote an expert system for fixing the motors of train set engines. His system required that you measure the voltages and currents through different parts of the motor. His expert system would then tell you what was wrong with the motor. He was giving this away for free to hobbyists, until someone else figured out that the same expert system would help identify faults with industrial winches and motors, and was charging consultancy fees.
That is far too many levels. Cut out the software/hardware architect, they are pretty useless with a skilled force anyway.
That was with an embedded systems project with a medium sized company - employing a number of people from a hardware board designer working with CPU's, network controller chips device a device driver programmer, one team leader, a project manager and a couple of software engineers. Core library staff included architects and a director.
With software houses like game companies, the smallest will just have three staff; graphics programmer, artist-animator, level-editor /audio programmer.
Pair programming is more to get the senior person train up the junior person and extract their knowledge, then shuffle them up into management, so they can't pass the knowledge onto anyone else:
ST exec turns from topsoil to silicon
EET: What was the culture of the EE like back then?
Bosson: They were gurus, and you needed the OK to talk to those guys. You had to be very shy and approach them [as you would] wild animals. Our wish was to try to grab as much as we could from them. But they were guys who were protecting their jobs, too. You had to have a lot of white and gray hair, Monsieur Le Engineer.
You were trying to observe them because you wanted to get as much as you could from their behavior, their approach, their way of working. It was like [being] with a teacher. A teacher is ready to share with you. But those EEs -- as with the wild animal, you had to get close to them step by step, watching their emotions step by step.
If you watch large teams of programmers, the management actually force the developers to write slow code, claiming that maintainability is more important than any other factor!
I've worked in a couple of companies like that - usually the programmers were limited to working on technology that the management (ex-programmers) were familiar with. Then also, management didn't want the programmers learning "high-demand skills" (ie. hardware programming) that would boost the chances of their staff leaving to a better paid environment. Or there was the politics of favoritism where the directors wanted to give a leg up the seniority ladder to their best mate. Everyone else who was qualified "didn't have the skills or was busy on another project" while of course their mate "had applied at just the right time with the right skills". Another problem was that if management gave only one programmer a new hardware system, then everyone else would get cheesed off that they were falling behind that they would leave (eg. a CPU porting project). Alternatively, there are also quota based systems which would piss off one nationality off another.
Invariably these companies gain a bad reputation and implode after a slow death spiral, where they are forced to lay off staff and sell off equipment to cover debts. With fewer staff, they can't take on new projects, and the cycle continues until the last project is cancelled.
Even back in the late 1980's it was obvious that thin pyramid management structures were being toppled through downsizing. Some of my relatives took early retirement from companies due to this. Long chains of management over 15 levels deep were definitely going out of fashion: director, assistant director, senior manager, assistant senior manager, supervising manager, project manager, assistant project manager, team leader, lead programmer, senior programmer, programmer, junior programmer and intern.
Start up companies just a far simpler structure: director, software/hardware architect, team leader, senior programmer and programmer.
Everyone knew about the hazards of "dead man's shoes" and how important it was to keep your skills up to date or lose your career.
Even with monochrome, that would be enough to read text, recognize faces, walk down a pavement, take public transport, read timetables and do shopping without any of these requiring assistance.
Contact your local university, ask them if it would be possible to file a technical report with a departmental archive... that's what all university departments do when submitting papers; submit the research as a technical report, then send it off for consideration for publication. Even if the paper is turned down, you still have the technical report filing.
I would guess that they would be the same transcendental functions supported by the other shader languages; Cg, GLSL and Renderman; sine, cosine, tan, asin, acos, atan, sinh, cosh, tanh, if not sincos as well. They are also going to need exp, log, exp2, log2, exp10 and log10. All of these will be required for statistical modeling of texture, 3D animation and image processing. Maybe they won't be vectorized, or maybe it will be possible to treat each 16-element vector as a matrix.
The central fovea of the human retina has the highest density of cones sensitive to color, while peripheral vision is populated by rods which are sensitive to light intensity only.
For somebody with normal vision, redirecting light from the fovea to peripheral vision isn't going to have any benefit, but for someone with no central vision who cannot perceive texture (ie.text) or color, regaining the ability to read text is going to be of great benefit.
That has been happening for the past fifteen years. Professional application developers could only support a handful of OS's. Back in the mid 1990's, these would be the UNIX workstation vendors; IBM, Sun, SGI, DEC, HP. Then when Windows NT came out, developers were forced to drop one or more UNIX workstation vendors, whichever was the least used OS and support Windows NT. Once the other Linux OS's were able to get certified 3D graphics boards and drivers, that was another couple of traditional UNIX OS's that were pushed out. It looks like it will be a world where there will be Solaraix, Linux and Windows.
French shops and supermarkets open around 8.00am or 9.00am, have two hours lunchbreaks from 12pm to 2pm, but they work later until around 7.00pm or 8.00pm. Annoying if you are on holiday because you then have to schedule your day around the lunchbreak; shops in the morning, supermarket in the afternoon. But it is good for the office workers.
Google's equivalent of that picture is rather blurry, so I think they are safe.
Google Streetview of the Hollywood sign