To detect humans, wouldn't it be easier and less costly, and perhaps even more effective, to hold a large database of questions that are readable and solvable only by humans?
Asking simple math or site-relevant questions are not only easier for humans (I'm talking about "What's 5 - 3") to read, but they're harder for automated parsing by software to crack.
I've inherited a misbehaving piece of Java/Hibernate code. I'm hoping the cloud has a silver lining, because otherwise it has the stench of Mordor on it...
Hibernate's notoriously difficult to debug and inspect when something's gone wrong.
Personally, if you're only using a couple of database tables, you shouldn't need an ORM solution. Just read/write from the DB using stored procedures.
I've helped out with interviews where I work, and here's some of what we look for:
Experience - not just in Java, but also in the industry.
Core Java, Essential J2EE and Web Frameworks - understanding of core Java, its querks (reference checks:.equals() verses == for instance). J2EE is just a specification. Get used to that. Learn the basics of J2EE and how servlets, JSPs and the request/response process works (FTLOF, know the difference between GET and POST!). Struts experience is a good thing.
It's a difficult industry to get into as you're probably aware. Recruiting for Java posts is a minefield - it's full of people who should be stacking shelves in a supermarket.
I don't think you can go far wrong if you get as much experience in core Java as possible. The same goes for J2EE; if you understand what it is and know the trials and tribulations of building a web-app from scratch, you're on the right track. Then, and only then, should you move onto working with frameworks; so build applications both stand-alone and web, and do the boring stuff yourself (i.e., write your own web.xml.)
Spring and Hibernate are funny ones. Spring's just an IoC framework. Until you're proficient in OO design, you probably shouldn't worry about it. Oh, and learn what IoC is first. Don't just think 'spring' and say you know it. Very few people know why they chose spring as a framework (there are plenty of IoC containers out there).
Hibernate (an ORM solution) is a dark art. Get the basics done first. Write JDBC DAOs yourself and learn why you'd need ORM before you dive into it.
Anarchy Online's been very successful. Before Age of Conan was released, it had a relatively large player-base. That's since dwindled due to AoC, but it's still around.
There's a graphics update due to be released (if ever), that would revamp the game entirely. Lots of players are waiting on it.
Python isn't a scripting language. It's a fully featured object oriented language. It just so happens that it's awesome and flexible enough to be used for scripting.
Scam doesn't necessarily mean nothing. It just means it's not as good or it doesn't do as well as it was marketed to do. SLI is a perfect example - "not 2x performance" is a shocking waste of money when another card is ~$400 and it's helping to fry the rest of your components.
It's called K.I.S.S. The following devices could be combined into one with numerous offerings that are on the mobile phone market these days:
Nokia N810
LG Chocolate
Sony Ericcson Z310a
Cowan iAudio X5L
Arguably, you could also scrap the digital camera as most phones have cameras on them. I'm a photographer myself so I can appreciate not wanting to do that.
For the Logitech MX1000 (wireless mouse) - use batteries. As for your Nintendo DS, the battery life is pretty good on that, so you could just charge it each night instead of lugging the power adapter around.
It's hardly going to bring down the company (unless the company was in such dire straits that anything small could bring it down, in which case it's about time to leave), and may bring to the attention of the upper mucks of an important issue.
There are better ways of doing that, such as persevering, practicing what you preach (good development standards and approach), being firm with management about the issue.
You're obviously fighting an up-hill struggle. Going straight to the CEO is both a good and bad idea - if it works you'll get immediate affect, but it's likely to be ignored.
You need to argue this case as much as possible. If you're the developer, or in charge of development, enforce decent developmental practices and ensure your estimates include them. Err on the side of caution. Take an estimate and double it. Managers talk money, not standards, so you'll have to hit them where it hurts.
Otherwise, is there anything off-the-shelf that could alleviate some development?
To the editors:
Just because Digg, reddit et al have posts like this, it doesn't mean slashdot needs it. Part of the reason I still hit this site is because what's posted has some worth and is usually interesting.
Slashdot Mirror
To detect humans, wouldn't it be easier and less costly, and perhaps even more effective, to hold a large database of questions that are readable and solvable only by humans?
Asking simple math or site-relevant questions are not only easier for humans (I'm talking about "What's 5 - 3") to read, but they're harder for automated parsing by software to crack.
Hibernate's notoriously difficult to debug and inspect when something's gone wrong.
Personally, if you're only using a couple of database tables, you shouldn't need an ORM solution. Just read/write from the DB using stored procedures.
I was referring to spring core. Technically just a IoC & aspect-j framework.
It's a difficult industry to get into as you're probably aware. Recruiting for Java posts is a minefield - it's full of people who should be stacking shelves in a supermarket.
I don't think you can go far wrong if you get as much experience in core Java as possible. The same goes for J2EE; if you understand what it is and know the trials and tribulations of building a web-app from scratch, you're on the right track. Then, and only then, should you move onto working with frameworks; so build applications both stand-alone and web, and do the boring stuff yourself (i.e., write your own web.xml.)
Spring and Hibernate are funny ones. Spring's just an IoC framework. Until you're proficient in OO design, you probably shouldn't worry about it. Oh, and learn what IoC is first. Don't just think 'spring' and say you know it. Very few people know why they chose spring as a framework (there are plenty of IoC containers out there).
Hibernate (an ORM solution) is a dark art. Get the basics done first. Write JDBC DAOs yourself and learn why you'd need ORM before you dive into it.
Basically, learn the core concepts.
I see a rather amusing picture of two lobsters; each of them holding a knife. I'm using Adblock too.
I was rating its success on age. It's been around for 7 or so years.
Anarchy Online's been very successful. Before Age of Conan was released, it had a relatively large player-base. That's since dwindled due to AoC, but it's still around.
There's a graphics update due to be released (if ever), that would revamp the game entirely. Lots of players are waiting on it.
Somebody can't detect satire properly.
Weren't Openhand working closely with the Openmoko project? If so, will Intel pull them out of their work on the Neo/Freerunner?
Python isn't a scripting language. It's a fully featured object oriented language. It just so happens that it's awesome and flexible enough to be used for scripting.
That's still a shocking survey. 300 people? That's entirely non-representative.
I hate these sensationalist statistics. How many people did they ask? What's the report's definition of 'admin'? etc etc
95% of statistics are made up on the spot.
I didn't know that. Thanks.
Scam doesn't necessarily mean nothing. It just means it's not as good or it doesn't do as well as it was marketed to do. SLI is a perfect example - "not 2x performance" is a shocking waste of money when another card is ~$400 and it's helping to fry the rest of your components.
That is all.
Isn't SLI a con?
That's not what the movies tell us!
I meant keep it simple by not using so many devices.
I neglected to ask this in my previous post: why the f-ck have you got three mobile phones?
Arguably, you could also scrap the digital camera as most phones have cameras on them. I'm a photographer myself so I can appreciate not wanting to do that.
For the Logitech MX1000 (wireless mouse) - use batteries. As for your Nintendo DS, the battery life is pretty good on that, so you could just charge it each night instead of lugging the power adapter around.
There are better ways of doing that, such as persevering, practicing what you preach (good development standards and approach), being firm with management about the issue.
That's called sabotage and it's a silly idea.
You're obviously fighting an up-hill struggle. Going straight to the CEO is both a good and bad idea - if it works you'll get immediate affect, but it's likely to be ignored.
You need to argue this case as much as possible. If you're the developer, or in charge of development, enforce decent developmental practices and ensure your estimates include them. Err on the side of caution. Take an estimate and double it. Managers talk money, not standards, so you'll have to hit them where it hurts.
Otherwise, is there anything off-the-shelf that could alleviate some development?
What part of delusions implies you admit anything anyway?
To the editors:
Just because Digg, reddit et al have posts like this, it doesn't mean slashdot needs it. Part of the reason I still hit this site is because what's posted has some worth and is usually interesting.
Sort it out.