Wake me up when it is pitch-able, hit-able and the size of a baseball. It would make our "national pastime" exciting to watch.
It might actually be easier to essentially embed this in a clear plastic soccer ball. You'd want to add a radio tx to stream the images out so you could have a "ball-cam" in the live feed. Maybe instant replay would be good enugh. With a spinning ball you'd need one hell of a fast shutter to cut out the blur.
Kernel of a good idea worth a big pile of cash but they have a long way to go.
Java... ok, why not. I would take a look at Cassandra and Zookeeper to get the ball rolling. You'll need a good load balancer; nginx or haproxy since I don't know of a good one in Java. I assume a bunch of tomcat servers for the actual app. I suppose jboss messaging to keep with the java theme.
You can get all that on one machine for development, then for deployment you can flexibly adjust the number of db servers, queue servers, load balancers and app servers based on anticipated load. If you're extra-cool you can deloy to a cloud and dynamically allocate servers as-needed.
Been there, done that. Got the t-shirt. It's fun. Enjoy it.
Spend an extra day or two thinking about exactly how you're going to handle logging. It will be worth it.
The best you can do is make sure your own code is clean and clear. Eventually the contrast will be noticed and management should step in to figure out how to overall improve code quality. In theory they will consult with the developers that have demonstrated good practices. It is quite possible, even likely that no one will care.
You do your job. You write your code. If you do well you may end up managing a team. Then you can implement whatever kind of quality control you feel is appropriate.
The only truly meaningful metric is customer satisfaction. After each ticket is closed send a survey email to the user. If your team plows through enough tickets you get a statistically significant success % per tech that you can compare to the other techs.
Without knowing a lot more about the nature of tickets it is hard to give a better response. It might be very important to gauge the difficulty (trivial-hard) and novelty (common-rare) of tickets but it could also be a waste of time. Does one tech plow through dozens of tickets a day or a few? Are the techs specialized? Anything email related goes to joe, hardware issues to tom, etc.. Are the tickets auto-generated from emails, called in or do they fill out a web form?
Given the size of the team the company thinks 1) you aren't getting the job done, 2) one or more people on the team are dead weight or 3) you are overworked and need more people. I wouldn't bet on #3.
"Unscrewed" with Martin Sargent... what a show that was. For a taste, take a listed to the "Infected" Podcast. Crazy/insane-funny, twisted, warped, and yes, more than just a little sick from time to time.
'most popular' implies that the member group has a positive view of the object. 'most used' has no positive or negative connotation. As the relevant data (browser statistics) is based on the number of hits rather than a poll of user preference it is clearly more accurate and truthful to say "most used" instead of "most popular".
Suppose Bill and Linus were in the same high school, and the ballot was distributed as:
MOST POPULAR (pick three) [ ] Billy G [ ] Billy G [ ] Billy G [ ] Other _________
While Billy might claim to be most popular based on the outcome of such a vote, it reflects a warped and stilted reality. He could say he got the most votes, which would at least be literally true. There is an inherent assumption that statements regarding the state of existance are intended to approximate true reality. The degree to which that approximation is accurate cooresponds directly with the truthfullness of the statement.
I'll probably go to hell for it, but to put it in terms of Goodwins Law:
Getting gassed by Nazis was very popular among the Jews.
If it is a digital camera the transfer speed should be entirely irrelivent to the quality of the output. That it is possible to drop frames during a video transfer it implies that the video is being re-encoded as it transfers. With a camera design that badly screwed up, I would expect problems.
I don't think he (or any sensible developer) would have any problem with using table tags for tabular data, especially data with good headings and captions.
"Price is rarely irrelivent. A more economical option would be to skip the FSO and just use something like a Proxim QuickBridge. Another alternative which hits a nice price/performance/reliability is a Trango Atlas (45Mbps, about $3k). Most inexpensive (ala 10k) and the licence may be an annual recurring cost. Licence costs depend on location (city/county/state)."
Not sure what happened there, my paragraph about licenced freq antenna systems got chopped up. Weird.. but you probably don't want to go with licenced freq anyway.
Good question. What you are looking for is a point to point bridge. At short range with good line of sight there are only three relevant factors. Price, Speed and Quality.
If price is irrelivent, a free space optic (like gigabeam) with an RF backup (like a Tsunami) will give you massive amounts of bandwidth, low latencies and lots of 9s for uptime/reliability.
Price is rarely irrelivent. A more economical option would be to skip the FSO and just use something like a Proxim QuickBridge. Another alternative which hits a nice price/performance/reliability is a Trango Atlas (45Mbps, about $3k). Most inexpensive (ala 10k) and the licence may be an annual recurring cost. Licence costs depend on location (city/county/state).
Just one male and one female bee, surviving for 60 days and nights on a boat. Of course, given that the female bee (presumably a queen) is either already fertilized (and will start laying 2-3k eggs per day) or unfertilized in which case that one male bee has a whole lot of sperm to contribute to the cause (16-20 males is typical).
Without any worker bees (female) our queen is going to starve in short order. Even if she survives with no one to feed the larvae our ark bound colony is a lot like a warcraft game with all your peons killed and no resources to make more.
"Software" in general isn't expected to be 100% bug free. But a highly specialized application for voting (ie: counting input) that runs on standardized hardware would take a competent programmer hours, not days to write. Even in ADA. Add *YEARS* of testing/debug time and any error is inexcusable. An error that changes the tally is criminal.
The only complexity comes with a secure transport mechanism to merge results from the stations. Results are already reported per-precient. Secure transport between locked down hardware is a well understood and solved problem.
It isn't like a voting booth system is difficult to debug or verify. The stories about machines getting more votes than they could handle smack of total incompetence.
A great episode. You've indicated the one real flaw in Farscape that even die-hard fans have to acknowledge. Many of the episodes are hard to understand unless you've seen all the earlier shows.
With so many of the Farscape episodes as 2 or 3 part it isn't something they could have fixed without dumbing down the plot.
On the meta-plot axis; you have the weak meta-plot shows like Star Trek (orig and NG), single plot threads (voyager) and multiple plot threads (DS9, B5 and Farscape).
The stronger the meta-plot the harder it will be for a new viewer to "get" the show. Some shows are worth the effort (Farscape); some are not (DS9 }:> ).
Slashdot Mirror
Vote with your wallet, my next SSD will be a samsung.
Is anyone actually surprised by these poll results?
Wake me up when it is pitch-able, hit-able and the size of a baseball. It would make our "national pastime" exciting to watch.
It might actually be easier to essentially embed this in a clear plastic soccer ball. You'd want to add a radio tx to stream the images out so you could have a "ball-cam" in the live feed. Maybe instant replay would be good enugh. With a spinning ball you'd need one hell of a fast shutter to cut out the blur.
Kernel of a good idea worth a big pile of cash but they have a long way to go.
Maybe those two LOC are is really, really, really bad.
Java... ok, why not. I would take a look at Cassandra and Zookeeper to get the ball rolling. You'll need a good load balancer; nginx or haproxy since I don't know of a good one in Java. I assume a bunch of tomcat servers for the actual app. I suppose jboss messaging to keep with the java theme.
You can get all that on one machine for development, then for deployment you can flexibly adjust the number of db servers, queue servers, load balancers and app servers based on anticipated load. If you're extra-cool you can deloy to a cloud and dynamically allocate servers as-needed.
Been there, done that. Got the t-shirt. It's fun. Enjoy it.
Spend an extra day or two thinking about exactly how you're going to handle logging. It will be worth it.
Tough but true.
The best you can do is make sure your own code is clean and clear. Eventually the contrast will be noticed and management should step in to figure out how to overall improve code quality. In theory they will consult with the developers that have demonstrated good practices. It is quite possible, even likely that no one will care.
You do your job. You write your code. If you do well you may end up managing a team. Then you can implement whatever kind of quality control you feel is appropriate.
The only truly meaningful metric is customer satisfaction. After each ticket is closed send a survey email to the user. If your team plows through enough tickets you get a statistically significant success % per tech that you can compare to the other techs.
Without knowing a lot more about the nature of tickets it is hard to give a better response. It might be very important to gauge the difficulty (trivial-hard) and novelty (common-rare) of tickets but it could also be a waste of time. Does one tech plow through dozens of tickets a day or a few? Are the techs specialized? Anything email related goes to joe, hardware issues to tom, etc.. Are the tickets auto-generated from emails, called in or do they fill out a web form?
Given the size of the team the company thinks 1) you aren't getting the job done, 2) one or more people on the team are dead weight or 3) you are overworked and need more people. I wouldn't bet on #3.
Taking away the last line of defense by digitizing our schoolbooks is just not acceptable. You thing that e-book is going to be stopping bullets?
o otings.textbooks.ap/index.html
http://www.cnn.com/2006/EDUCATION/10/20/school.sh
Anyone that won't at least give it fundamental extrememly influential historical document status isn't rational. Troll is a fair mod.
In no particular order:
Nethack
Masters of Orion 2
Continuum
Alpha Centauri
Neverwinter Nights
"Unscrewed" with Martin Sargent... what a show that was. For a taste, take a listed to the "Infected" Podcast. Crazy/insane-funny, twisted, warped, and yes, more than just a little sick from time to time.
'most popular' implies that the member group has a positive view of the object. 'most used' has no positive or negative connotation. As the relevant data (browser statistics) is based on the number of hits rather than a poll of user preference it is clearly more accurate and truthful to say "most used" instead of "most popular".
Suppose Bill and Linus were in the same high school, and the ballot was distributed as:
MOST POPULAR (pick three)
[ ] Billy G
[ ] Billy G
[ ] Billy G
[ ] Other _________
While Billy might claim to be most popular based on the outcome of such a vote, it reflects a warped and stilted reality. He could say he got the most votes, which would at least be literally true. There is an inherent assumption that statements regarding the state of existance are intended to approximate true reality. The degree to which that approximation is accurate cooresponds directly with the truthfullness of the statement.
I'll probably go to hell for it, but to put it in terms of Goodwins Law:
Getting gassed by Nazis was very popular among the Jews.
If it is a digital camera the transfer speed should be entirely irrelivent to the quality of the output. That it is possible to drop frames during a video transfer it implies that the video is being re-encoded as it transfers. With a camera design that badly screwed up, I would expect problems.
I don't think he (or any sensible developer) would have any problem with using table tags for tabular data, especially data with good headings and captions.
"Price is rarely irrelivent. A more economical option would be to skip the FSO and just use something like a Proxim QuickBridge. Another alternative which hits a nice price/performance/reliability is a Trango Atlas (45Mbps, about $3k). Most inexpensive (ala 10k) and the licence may be an annual recurring cost. Licence costs depend on location (city/county/state)."
Not sure what happened there, my paragraph about licenced freq antenna systems got chopped up. Weird.. but you probably don't want to go with licenced freq anyway.
Good question. What you are looking for is a point to point bridge. At short range with good line of sight there are only three relevant factors. Price, Speed and Quality.
If price is irrelivent, a free space optic (like gigabeam) with an RF backup (like a Tsunami) will give you massive amounts of bandwidth, low latencies and lots of 9s for uptime/reliability.
Price is rarely irrelivent. A more economical option would be to skip the FSO and just use something like a Proxim QuickBridge. Another alternative which hits a nice price/performance/reliability is a Trango Atlas (45Mbps, about $3k). Most inexpensive (ala 10k) and the licence may be an annual recurring cost. Licence costs depend on location (city/county/state).
So for rough ballparks...
FSO w/RF backup, 1Gbps, $25k +
Licenced P2P RF, 100Mb, $12k + Licence
Unlicenced P2P RF, 54Mb, $3k (Trango)
Unlicenced P2P RF on-the-cheap, 54Mb, $1500 (Microtik, other 802.11x based systems)
Unlicenced P2P RF ultra-cheap, 54Mb, $400 (WRT54Gx2 w/Sveasoft firmware, external antennas)
Just one male and one female bee, surviving for 60 days and nights on a boat. Of course, given that the female bee (presumably a queen) is either already fertilized (and will start laying 2-3k eggs per day) or unfertilized in which case that one male bee has a whole lot of sperm to contribute to the cause (16-20 males is typical).
Without any worker bees (female) our queen is going to starve in short order. Even if she survives with no one to feed the larvae our ark bound colony is a lot like a warcraft game with all your peons killed and no resources to make more.
"Software" in general isn't expected to be 100% bug free. But a highly specialized application for voting (ie: counting input) that runs on standardized hardware would take a competent programmer hours, not days to write. Even in ADA. Add *YEARS* of testing/debug time and any error is inexcusable. An error that changes the tally is criminal.
The only complexity comes with a secure transport mechanism to merge results from the stations. Results are already reported per-precient. Secure transport between locked down hardware is a well understood and solved problem.
It isn't like a voting booth system is difficult to debug or verify. The stories about machines getting more votes than they could handle smack of total incompetence.
Very well put; but you'll sure scare the fundies working with evolution in mathematical terms.
Depends a great deal on which state in the USA
"Revenging Angel", Season 3 Episode 16
A great episode. You've indicated the one real flaw in Farscape that even die-hard fans have to acknowledge. Many of the episodes are hard to understand unless you've seen all the earlier shows.
With so many of the Farscape episodes as 2 or 3 part it isn't something they could have fixed without dumbing down the plot.
On the meta-plot axis; you have the weak meta-plot shows like Star Trek (orig and NG), single plot threads (voyager) and multiple plot threads (DS9, B5 and Farscape).
The stronger the meta-plot the harder it will be for a new viewer to "get" the show. Some shows are worth the effort (Farscape); some are not (DS9 }:> ).
He's presumably (hopefully?) talking about the zone file format.
For the lazy...
Nope, the non-standard connector requirement is still in place.
The reasoning isn't entirely absurd. They are trying to reduce accidental/ignorant violations.
Coincidence or Scam? My vote is SCAM
Request for donations to Michelle