Create 8 battery operated arduino's whose sole purpose is to translate and then broadcast the single IP Ethernet to unique IP on a wireless network, run a local ap, then I'm sure there are apps/scripts that will allow you to sandbox the OEM app allowing the reversing of the IP translation back to the original and running multiple concurrent independent instances(no VM required), i did this with outlook prior to it allowing multiple exchange accounts, although didnt tackle the ip routing. Then sit back and get fat while you compete you full days job in an hour.
Why nerds are not Jocks....
In a real game of baseball, there are only 2 instances where a runner tries to run the entire 4 bases:
1) a home run, in which case NO ONE is trying to complete the loop as fast as possible, heck its more aptly named the home-not-so-brisk-jog.
2) an inside the park home run. While aptly applied, the number of times this situation is attempted, much less completed is so infinitesimally small, if kinda makes this junk science. Furthermore, this idea assumes that the runner is aware of the necessity of obtaining an inside the park home run path (as opposed to say a straight line single) from the time he leaves the batters box. This is simply never the case, a typical inside the park home run is usually a stand up double or stretched triple and during the base running the runner must make 2-3 judgment calls as to the prospects of reaching the next base successfully and usually occurs through some unforeseeable bounce in the outfield or fielding bordering on an error. Therefore, in all but a fraction of a percent of plays, following this path will actually cost runners time, bases and outs.
Furthermore, in the instance of a single, where from leaving the box the runner understands extra bases will not be an option, the straight line reigns supreme.
The only instance where this applies is when leaving the batters box, where at least a stretched double is assumed. Again providing inside the park home runs occur so infrequently that a four base path should be
completely omitted from calculations because it would disproportionately and adversely effect the 2 and 3 base runs. Basically apply the distance/speed algorithm used here to a triple and again for a double both will end up different from the 4 base version and each other, merge these two paths weighted based on the proportionality of doubles hit to triples hit. Thats is the path to be followed. furthermore, overlay the double and tripple paths ontop of the combined paths to allow the runner to deviate from the combined path at any point during the run to accommodate for an assumed more expected result which can be judged multiple times during the run.
Now that would be applied science.
I grew up in Merced a 40k population town of farmers and migrant workers (30 years ago), now our newly christened University is leading slashdot and expanding the universe. What now Bitches!
I did the same, only caught in QA for 6 months though....
I can tell u this, some companies(mine) hire Jr. programmers when they cant get anyone else, for one reason or another.
I found out the reason for my company soon, startup short on funding regularly misses payroll. Currently Im 3 paychecks behind...ughh
But at least Im not "Unemployed" during this messy market, and Im getting bonfide Programmer experience on my resume for when I chose to bolt!
I was in a similar situation, bay area, recent CS grad. I wasn't the valedictorian but I also was one of the smarter people in the room.
Took a crap 6 mo contract QA position at a very large and well known company. A trained monkey could have done my job! My boss sucked, my pay was 1/2 what I should receive w/ my qualifications, and my boss fought me tooth and nail about learning/mingling with the developers we supported.
I took every opportunity afforded to make friends and professional contacts in the dev team I supported. Once my contract was up, it was personal and professional references from the teams top 2 Software Engineers and one from the Development Director that made my resume stand out in the stack and further secured my job offer when they were contacted.
So my point/advice is get your foot in the door anywhere. Make contacts. Thats how you move up the ladder.
Slashdot Mirror
I've only been ashamed to be a Californian twice in my life, when Prop 8 (2008) passed, and this.......
Dumb people are....Dumb
Create 8 battery operated arduino's whose sole purpose is to translate and then broadcast the single IP Ethernet to unique IP on a wireless network, run a local ap, then I'm sure there are apps/scripts that will allow you to sandbox the OEM app allowing the reversing of the IP translation back to the original and running multiple concurrent independent instances(no VM required), i did this with outlook prior to it allowing multiple exchange accounts, although didnt tackle the ip routing. Then sit back and get fat while you compete you full days job in an hour.
a 2012 O.S. w/o tabbed browsing shows how much FAIL M.S. is still capable of........
I think the more appropriate question is, "Why does the rest of the world insist on clinging to the Metric system....?"!!!
Why nerds are not Jocks.... In a real game of baseball, there are only 2 instances where a runner tries to run the entire 4 bases: 1) a home run, in which case NO ONE is trying to complete the loop as fast as possible, heck its more aptly named the home-not-so-brisk-jog. 2) an inside the park home run. While aptly applied, the number of times this situation is attempted, much less completed is so infinitesimally small, if kinda makes this junk science. Furthermore, this idea assumes that the runner is aware of the necessity of obtaining an inside the park home run path (as opposed to say a straight line single) from the time he leaves the batters box. This is simply never the case, a typical inside the park home run is usually a stand up double or stretched triple and during the base running the runner must make 2-3 judgment calls as to the prospects of reaching the next base successfully and usually occurs through some unforeseeable bounce in the outfield or fielding bordering on an error. Therefore, in all but a fraction of a percent of plays, following this path will actually cost runners time, bases and outs. Furthermore, in the instance of a single, where from leaving the box the runner understands extra bases will not be an option, the straight line reigns supreme. The only instance where this applies is when leaving the batters box, where at least a stretched double is assumed. Again providing inside the park home runs occur so infrequently that a four base path should be completely omitted from calculations because it would disproportionately and adversely effect the 2 and 3 base runs. Basically apply the distance/speed algorithm used here to a triple and again for a double both will end up different from the 4 base version and each other, merge these two paths weighted based on the proportionality of doubles hit to triples hit. Thats is the path to be followed. furthermore, overlay the double and tripple paths ontop of the combined paths to allow the runner to deviate from the combined path at any point during the run to accommodate for an assumed more expected result which can be judged multiple times during the run. Now that would be applied science.
I grew up in Merced a 40k population town of farmers and migrant workers (30 years ago), now our newly christened University is leading slashdot and expanding the universe. What now Bitches!
Issue everyone Mittens!!!! They are relatively cheap and make it oh so hard to type terminal commands when worn.
I did the same, only caught in QA for 6 months though.... I can tell u this, some companies(mine) hire Jr. programmers when they cant get anyone else, for one reason or another. I found out the reason for my company soon, startup short on funding regularly misses payroll. Currently Im 3 paychecks behind...ughh But at least Im not "Unemployed" during this messy market, and Im getting bonfide Programmer experience on my resume for when I chose to bolt!
Its Back!! Can I get an Amen from the Congregation?!!!
I was in a similar situation, bay area, recent CS grad. I wasn't the valedictorian but I also was one of the smarter people in the room. Took a crap 6 mo contract QA position at a very large and well known company. A trained monkey could have done my job! My boss sucked, my pay was 1/2 what I should receive w/ my qualifications, and my boss fought me tooth and nail about learning/mingling with the developers we supported. I took every opportunity afforded to make friends and professional contacts in the dev team I supported. Once my contract was up, it was personal and professional references from the teams top 2 Software Engineers and one from the Development Director that made my resume stand out in the stack and further secured my job offer when they were contacted. So my point/advice is get your foot in the door anywhere. Make contacts. Thats how you move up the ladder.