It would also have been nice when I had the stupid things glued to my head for 10 days during a VEEG. Then again, it wouldn't have helped the worst part, which was the 2-inch electrode probes stuck in beside my cheekbones. Still, it was worth it to validate the viability of surgery, even with the rotten glue.
I've often wondered if Glassfish app server and OpenMQ messaging are viable alternatives (in realibility, performance and features) to IBM's Websphere and Websphere MQ. That would save a bunch of money right there, but it's got to be a huge battle switching an existing IBM system (and add-ons to that system) over to the open source alternatives.
Yeah, that's true -- it makes more sense to either ban all, or ban none.
I worked with a guy who was driving and was hit head-on by some drunk idiot. He and his girlfriend were both in pretty bad shape for a while. I know that alcohol's not going to get banned again, but you wonder how many lives it would save if it did?
Of course, musing about something like this on/. gets you modded troll, flamebait, or worse.
This is very true -- it's so easy to get into the mindset of "well I write webapps, so everything I make has to be a webapp".
Actually, this just happened to me. I was trying to find a way to write a utility that reads and writes in a big directory structure which users can access, but which the app server is not able to see. So I figured I would have to force users to zip up the whole directory and upload it, until my team lead said, "Why don't you just make this a client-side app instead?" Before that it had never even crossed my mind, but it made so much more sense to do it that way.
It's much better to think about requirements with an open mind about the platform than it is to lock yourself in, either consciously or subconsciously.
I scored a 35 on the ACT and qualified for a full ride scholarship at every university I was considering (including Case Western, not a cheap place by any means). But that was for Comp Sci, don't know if the same scholarship criteria are used for medicine.
Generally speaking, the bigger companies (IBM, Microsoft, Google, Motorola) pay quite a bit better for co-ops. Back when I was in college (comp sci & eng), people who worked at the big places made close to twice what I was getting at a smaller place. Those numbers were pretty consistent across our whole class.
I don't know what the quality of work is like at big places compares to the smaller. I liked the variety and importance of the stuff I got to do in an IT department of 4 people, and a better co-op experience is far more valuable in the long run. Basically, do what you think you'll like the most and aligns best with what you're planning for your future, instead of just trying to squeeze as much money as you out of a co-op. It won't seem that significant once you get a real position.
I'm a fan of JPA after using it on a decent-sized project (Spring MVC web app using Hibernate's JPA implementation). From what I've seen of original Hibernate config this does look a little simpler, primarily due to the annotations. However, I did run into a few JPA and JPA+Spring quirks that took up quite a bit of my time and would never have been an issue if I stuck to straight JDBC.
Would it have been quicker if I went with JDBC instead of JPA? Maybe. But now that I've got an idea of how to work through the minor issues, I'm pretty sure it'll save me some time on my next project.
Slashdot Mirror
It would also have been nice when I had the stupid things glued to my head for 10 days during a VEEG. Then again, it wouldn't have helped the worst part, which was the 2-inch electrode probes stuck in beside my cheekbones. Still, it was worth it to validate the viability of surgery, even with the rotten glue.
I've often wondered if Glassfish app server and OpenMQ messaging are viable alternatives (in realibility, performance and features) to IBM's Websphere and Websphere MQ. That would save a bunch of money right there, but it's got to be a huge battle switching an existing IBM system (and add-ons to that system) over to the open source alternatives.
or you will be in for an unpleasant surprise.
A text file makes a better database than MySQL.
A text file does not make a better database than MySQL. No queries. No transactions. No way.
Yeah, that's true -- it makes more sense to either ban all, or ban none.
/. gets you modded troll, flamebait, or worse.
I worked with a guy who was driving and was hit head-on by some drunk idiot. He and his girlfriend were both in pretty bad shape for a while. I know that alcohol's not going to get banned again, but you wonder how many lives it would save if it did?
Of course, musing about something like this on
Let's just bring back alcohol prohibition.
So I think I'll just switch from Java to that.
Because draconian punishments work so well to prevent all these other crimes.
Mocking my post = you lose all your karma.
Then the death penalty.
First for a month, then for a year.
Then heavy fines and community service.
Then jail time.
Then the death penalty.
This will guarantee no repeat offenders.
/irony
/woosh
/irony
Error: Cyclic Dependency
for the Year Of The Linux Desktop.
(sorry, I couldn't help myself...)
for the Year Of The Linux Desktop.
This is very true -- it's so easy to get into the mindset of "well I write webapps, so everything I make has to be a webapp".
Actually, this just happened to me. I was trying to find a way to write a utility that reads and writes in a big directory structure which users can access, but which the app server is not able to see. So I figured I would have to force users to zip up the whole directory and upload it, until my team lead said, "Why don't you just make this a client-side app instead?" Before that it had never even crossed my mind, but it made so much more sense to do it that way.
It's much better to think about requirements with an open mind about the platform than it is to lock yourself in, either consciously or subconsciously.
he's interested in anything that goes "ping"
Well, teach him how to use ping then...
Then when he gets the hang of that, take off the training wheels and let him use vi.
Spectre VR has never played this silky smoothly.
I scored a 35 on the ACT and qualified for a full ride scholarship at every university I was considering (including Case Western, not a cheap place by any means). But that was for Comp Sci, don't know if the same scholarship criteria are used for medicine.
While not anyone's idea of fun
Fixed that for you.
Those tabs don't add themselves, you know.
And it's definitely not nerdy.
We should draw a line and prohibit incoherent posts like this one.
Generally speaking, the bigger companies (IBM, Microsoft, Google, Motorola) pay quite a bit better for co-ops. Back when I was in college (comp sci & eng), people who worked at the big places made close to twice what I was getting at a smaller place. Those numbers were pretty consistent across our whole class.
I don't know what the quality of work is like at big places compares to the smaller. I liked the variety and importance of the stuff I got to do in an IT department of 4 people, and a better co-op experience is far more valuable in the long run. Basically, do what you think you'll like the most and aligns best with what you're planning for your future, instead of just trying to squeeze as much money as you out of a co-op. It won't seem that significant once you get a real position.
Can't wait for this baby.
You have died of dysentery. Settle here or move on?
Because we all know this is the Year Of The Linux Desktop.
I'm a fan of JPA after using it on a decent-sized project (Spring MVC web app using Hibernate's JPA implementation). From what I've seen of original Hibernate config this does look a little simpler, primarily due to the annotations. However, I did run into a few JPA and JPA+Spring quirks that took up quite a bit of my time and would never have been an issue if I stuck to straight JDBC.
Would it have been quicker if I went with JDBC instead of JPA? Maybe. But now that I've got an idea of how to work through the minor issues, I'm pretty sure it'll save me some time on my next project.