The main reason to stay away from PostgreSQL is its toolset. Specifically, it's almost impossible to find a tool that allows you to analyze and tune it's performance. I say 'almost' because there may be one out there that I haven't found...but I've looked on and off for years, with no results.
For mysql there's lots of tools, like jetprofiler. For oracle you can pay. For SQLite, well, who cares. For psql, it's (as one website put it) a black art. Do you really want that as your back end?
Maybe it'll be more like the ATV1, where it's a local cache of all your amazon stuff. It'll download content while you're away, and probably provide airplay-like functionality from your kindle....except you don't stream from your kindle, you stream from your amazon box with the kindle being a transparent remote.
I could see how that could be pretty handy. It's your amazon music/movie/book library in your house. As a plus, amazon could offer backup services, photo, etc too.
For the third world, amazon could offer amazon WebTV...which would actually be pretty handy.
Google has apparently been using this technology for their StreetView cars, and apparently meet all the straw-man requirements of the article.
So...do they have more bogus requirements that need to be met?
Driverless cars don't need to be able to handle any possible situation. Most drivers can't handle those situations either - witness the large number of accidents that happen every day. The driverless cars just have to be better, and have superior liability coverage, than human drivers.
Maybe the DOE should ask for personal guarantees from the officers. Most banks do this for small business loans, and the SBA loans are substantially less than $500m USD.
One thing for sure, Best Korea excels at publicity. At this point Mr. Kim's going to get the Saddam Hussein drone award delivered to his doorstep sometime soon.
You can hack it when the ballots are being counted. How? Because it's unclear if the scrutineers are really randomly chosen.
What is the process of selection? Do they draw the names out of a hat? Easy: the person picking the names can substitute any name they want. They just need 3 scruitineers, and they can tally the votes any way they'd like.
Taking a step back, how are candidates selected? You don't have to hack the process if you manipulate the selections or compromise the candidates.
Try and pass your device on as a broken iPad mini and sell it on craigslist or ebay. That's pretty much the only way to turn that thing into something useful.
One of the reasons that progress bars are so hard is that people architect their applications incorrectly.
Progress bars are an overview of the whole process. If you don't design your application for that use case, you'll get small, atomic operations with no real cohesion - ie: what you tend to get when you do OOP design. Data encapsulation makes it so the left and right hands have no idea what's happening. Plus, your UI code is somewhere off in the distance, and you can't really get to it.
Note that Photoshop 1.0 was a one-man app...and Knoll still works on Lightroom.
People today don't realize how mind-blowing Photoshop was back in the day. Nobody in real life did image editing - it was all airbrushing, paste-up, etc.
1. Exchange business cards on contact. That would be nice.
2. Do a quick background check on people that I touch. Medical, business, personal, etc and send the result to google glasses or some other display so I can read it in real time. A disease check would be nice too.
3. Teleprompter. How convenient!
4. If I die, the watch should alarm and send the appropriate notifications.
5. Whatever a fitbit does too. Heck, it's there.
6. Complain if my phone goes out of range. Very handy.
7. Charge using my body's electrical field/motion/whatever.
8. Buy me a drink, remotely. F*ck the bartender - bring the drink here, to me, now.
9. It should look cool. I mean, it's a f*ucking smart watch, so it has to look smart. It could be as big as Wonder Woman's bangles for all I care.
You don't need a missile do deliver a nuke. Heck, you don't even need fission. Just grind up a bunch of radioactive material and use explosives to disperse it into the air. There you go, you've poisoned a city forever. Game over.
Plus, if you don't care about high efficiency you have lots of options. Airburst = maximum damage, but you don't need to use a nuke as a bomb if you don't want to.
A DHCP server generally keeps track of the leases that it sends out, and that file tends to be on-disk.
Ahe DHCP server can also be configured to check to see if the address is in use before assigning it...usually via a ping, arp, etc. That's just as likely to be turned off, because it's expensive and sort of redundant.
So...if that file is blown away during an upgrade, well, the DHCP server knows its range, and it'll just start assigning addresses.
A DHCP server upgrade seems likely, as the problem started over the weekend...and this is a problem that wouldn't be caught during the acceptance test unless you were really lucky.
It sounds like someone blew away their DHCP lease file by mistake...so DHCP is assigning addresses that are already in use. Was there an upgrade over the weekend?
If that's the case, the only way to get around it is to query all the DSLAMs and rebuild the current lease file by hand.
If I remember correctly, my Apple ][e included all the board schematics, which made it easy for everyone to make cards/etc. A few years ago I found my AppleSoft basic tutorial, which was pretty neat.
Ah, the good old days. Too bad nothing's beaten Wizardry when it comes to RPGs.
It'd be complicated to test. Put everything on an SSD, so you've removed I/O latency. Put everything on the same/equivalent hardware with a lot of bandwidth between the parts. Then write different webapps using:
* mysql * postgresql * oracle * cassandra * mongo * dynamo * etc
Then you'd have to show the performance of each application at different levels of utilization...that is, after determining what "performance" actually means for a given application.
That would be a pretty interesting benchmark. Ideally, you'd have multiple webapps, so you could have different usage patterns.
For extra credit, you'd write the webapp in multiple languages and run them in multiple containers, just to see if the container made a difference.
By definition your code sucks, because it's legacy code and you wrote it.
So what? Does it work? Does anyone want to fuck with it? Is he willing to risk his job to change the code and break everything?
New developers want to rewrite everything, and don't understand that new projects don't happen often - and when they do, they don't get to work on them unless they have skills. That doesn't mean they need to kiss ass, but it does mean that they have to write code that works.
Maybe there -is- a better way to write it now. It'd be worth it to ask. Maybe he's right? Most likely he's has no context - it's written that way because it was written that way. Maybe he can rewrite it in his spare time and show everyone.
NOTE: if he was able to read your code and said it sucks and should be refactored or something, that means the code doesn't suck as much as he said it does - because he could read and understand it. That means that it's maintainable. So that's a plus on your side.
Slashdot Mirror
Well actually, higher education is for job skills - unless you don't consider thinking a job skill.
This is the snobification of higher education - and a pathetic way to justify the higher costs and (sometimes) higher pay of university graduates.
You can use that education to ponder this: if college really trained people to think critically, would the government really allow it to exist?
The main reason to stay away from PostgreSQL is its toolset. Specifically, it's almost impossible to find a tool that allows you to analyze and tune it's performance. I say 'almost' because there may be one out there that I haven't found...but I've looked on and off for years, with no results.
For mysql there's lots of tools, like jetprofiler. For oracle you can pay. For SQLite, well, who cares. For psql, it's (as one website put it) a black art. Do you really want that as your back end?
Back in the day, people broke into servers for fun.
Now, people break into servers to serve advertising.
Soon, people will break into servers to drop bitcoin miners on them.
I guess now we know where the real money is: ad impressions. What Ad networks serve ads to the cracker community?
Porn: the low-slung engine of progress.
Either that, or they're filming a reality show.
Maybe it'll be more like the ATV1, where it's a local cache of all your amazon stuff. It'll download content while you're away, and probably provide airplay-like functionality from your kindle....except you don't stream from your kindle, you stream from your amazon box with the kindle being a transparent remote.
I could see how that could be pretty handy. It's your amazon music/movie/book library in your house. As a plus, amazon could offer backup services, photo, etc too.
For the third world, amazon could offer amazon WebTV...which would actually be pretty handy.
Google has apparently been using this technology for their StreetView cars, and apparently meet all the straw-man requirements of the article.
So...do they have more bogus requirements that need to be met?
Driverless cars don't need to be able to handle any possible situation. Most drivers can't handle those situations either - witness the large number of accidents that happen every day. The driverless cars just have to be better, and have superior liability coverage, than human drivers.
Maybe the DOE should ask for personal guarantees from the officers. Most banks do this for small business loans, and the SBA loans are substantially less than $500m USD.
Given that there are interoffice emails in the stream, that implies that someone was able to access:
1. the mail server archive/backup
2. the mail server's scrubber (whatever they call the thing that scans email for sensitive info).
Do they all share a mailhost or something like that?
One thing for sure, Best Korea excels at publicity. At this point Mr. Kim's going to get the Saddam Hussein drone award delivered to his doorstep sometime soon.
You can hack it when the ballots are being counted. How? Because it's unclear if the scrutineers are really randomly chosen.
What is the process of selection? Do they draw the names out of a hat? Easy: the person picking the names can substitute any name they want. They just need 3 scruitineers, and they can tally the votes any way they'd like.
Taking a step back, how are candidates selected? You don't have to hack the process if you manipulate the selections or compromise the candidates.
Try and pass your device on as a broken iPad mini and sell it on craigslist or ebay. That's pretty much the only way to turn that thing into something useful.
You could maybe use it as a picture frame too.
Move further away from Africa and you'll be richer. So obviously that moon-based civilization will be unbelievably rich!
Get a Foscom Wireless IP Camera. It'll email you a picture if something triggers motion detection. Pretty handy.
Might want to get something that turns on the lights, too, so the camera can get a good look at whomever.
One of the reasons that progress bars are so hard is that people architect their applications incorrectly.
Progress bars are an overview of the whole process. If you don't design your application for that use case, you'll get small, atomic operations with no real cohesion - ie: what you tend to get when you do OOP design. Data encapsulation makes it so the left and right hands have no idea what's happening. Plus, your UI code is somewhere off in the distance, and you can't really get to it.
Note that Photoshop 1.0 was a one-man app...and Knoll still works on Lightroom.
People today don't realize how mind-blowing Photoshop was back in the day. Nobody in real life did image editing - it was all airbrushing, paste-up, etc.
Anyway, good reading:
http://www.theverge.com/2013/2/13/3959868/photoshop-is-a-city-for-everyone-how-adobe-endlessly-rebuilds-its
1. Exchange business cards on contact. That would be nice.
2. Do a quick background check on people that I touch. Medical, business, personal, etc and send the result to google glasses or some other display so I can read it in real time. A disease check would be nice too.
3. Teleprompter. How convenient!
4. If I die, the watch should alarm and send the appropriate notifications.
5. Whatever a fitbit does too. Heck, it's there.
6. Complain if my phone goes out of range. Very handy.
7. Charge using my body's electrical field/motion/whatever.
8. Buy me a drink, remotely. F*ck the bartender - bring the drink here, to me, now.
9. It should look cool. I mean, it's a f*ucking smart watch, so it has to look smart. It could be as big as Wonder Woman's bangles for all I care.
10. At some point it should be embeddable.
What are the tradeoffs associated with these mutations?
In general, when you have a benefit, it's offset with a negative somewhere.
Also, now there are epigenetic effects. Maybe it's not a mutation at all, just a difference in expression?
http://www.theverge.com/2013/1/18/3891836/glee-uses-jonathan-coultons-cover-of-baby-got-back-without-permission
There's no protection for a cover. However, the Glee people weren't nice because they didn't credit him for his ultra-boring cover of a great song.
That's just what I was thinking.
You don't need a missile do deliver a nuke. Heck, you don't even need fission. Just grind up a bunch of radioactive material and use explosives to disperse it into the air. There you go, you've poisoned a city forever. Game over.
Plus, if you don't care about high efficiency you have lots of options. Airburst = maximum damage, but you don't need to use a nuke as a bomb if you don't want to.
Well, you're talking about something else.
A DHCP server generally keeps track of the leases that it sends out, and that file tends to be on-disk.
Ahe DHCP server can also be configured to check to see if the address is in use before assigning it...usually via a ping, arp, etc. That's just as likely to be turned off, because it's expensive and sort of redundant.
So...if that file is blown away during an upgrade, well, the DHCP server knows its range, and it'll just start assigning addresses.
A DHCP server upgrade seems likely, as the problem started over the weekend...and this is a problem that wouldn't be caught during the acceptance test unless you were really lucky.
It sounds like someone blew away their DHCP lease file by mistake...so DHCP is assigning addresses that are already in use. Was there an upgrade over the weekend?
If that's the case, the only way to get around it is to query all the DSLAMs and rebuild the current lease file by hand.
Sucks to be them.
If I remember correctly, my Apple ][e included all the board schematics, which made it easy for everyone to make cards/etc. A few years ago I found my AppleSoft basic tutorial, which was pretty neat.
Ah, the good old days. Too bad nothing's beaten Wizardry when it comes to RPGs.
The better question would be:
Which back-end is best?
It'd be complicated to test. Put everything on an SSD, so you've removed I/O latency. Put everything on the same/equivalent hardware with a lot of bandwidth between the parts. Then write different webapps using:
* mysql
* postgresql
* oracle
* cassandra
* mongo
* dynamo
* etc
Then you'd have to show the performance of each application at different levels of utilization...that is, after determining what "performance" actually means for a given application.
That would be a pretty interesting benchmark. Ideally, you'd have multiple webapps, so you could have different usage patterns.
For extra credit, you'd write the webapp in multiple languages and run them in multiple containers, just to see if the container made a difference.
The #1 impediment to developer productivity is developers writing code that does the wrong thing. #2 is writing code that doesn't work.
Blame meetings all you want, but realistically speaking most developers are totally clueless.
Even this question is dumb. It's basically asking "how do we write bad code faster?"
By definition your code sucks, because it's legacy code and you wrote it.
So what? Does it work? Does anyone want to fuck with it? Is he willing to risk his job to change the code and break everything?
New developers want to rewrite everything, and don't understand that new projects don't happen often - and when they do, they don't get to work on them unless they have skills. That doesn't mean they need to kiss ass, but it does mean that they have to write code that works.
Maybe there -is- a better way to write it now. It'd be worth it to ask. Maybe he's right? Most likely he's has no context - it's written that way because it was written that way. Maybe he can rewrite it in his spare time and show everyone.
NOTE: if he was able to read your code and said it sucks and should be refactored or something, that means the code doesn't suck as much as he said it does - because he could read and understand it. That means that it's maintainable. So that's a plus on your side.