This could've lead to a somewhat funny situation as well. QA could've filed a bug saying autofocus didn't work. Then by the time the developer looked at the bug, it could've been in the working period and the developer could've marked the bug as 'WORKSFORME'. Which, when it gets back to that QA guy's plate, depending on whether it was still in the working period or not, the QA guy could've tested it and marked it as 'RESOLVED' if it was working, or re-open the bug if it still wasn't working. If it was re-opened, the whole cycle could continue to repeat.
I don't know if such a thing happened, but it would've been funny (in hindsight at least) if it had.
Actually, it's required to pass your checkride. The FAA examiner will at some point during your checkride do something to distract you and see how well you react to it (drop a pencil on your side of the floor, ask you to calculate true airspeed, etc.).
What's needed are higher standards for driving period. Right now, practically anyone can pass a driver's test and the written test is a joke. If it was more like getting a pilot's license, (harder test, more extensive practical test, required number of hours driving with an instructor), we'd probably all be a lot safer. Fewer idiots would pass the tests and be on the road. Only safe drivers and really determined idiots would be on the road:)
Hi, nice to meet you. Now increment the number of people you know who cut their teeth writing code on the linux kit before getting into the games business by 1. The Linux kit helped me get to know the GS and VU0, VU1, which came in handy a few months / year later when I interviewed for a position at Playstation (and then got that position). I work elsewhere now, but that PS2 Linux kit was definately valuable to me.
I used to ask the same question. I now work for a small startup. Most of us develop on Linux, a couple on Windows, and a couple on Mac. If we could afford to do a linux-only version, we would. But in order to have any kind of marketshare on the desktop, we need to output a Windows version.
The mac and linux versions mostly "just work" and simply need testing. But about a month before release, the entire team needs to stop what they're doing and get the Windows version fully working and tested. Windows development is a resource hog (in terms of people). In some ways, Windows is just different, but it seems in many ways, Windows is deliberately incompatable with anything else at the source code level. Windows makes it as difficult as possible to be cross-platform.
As a result, we get the Windows version out and working before we have time to test the Linux and Mac versions. It kinda sucks to spend that much time and resources on a Windows version. It's either that, or re-route our development resources to Windows-only and ignore the other platforms. Of course, we don't want to do that.
Either Microsoft is really stupid or really evil. Along with declaring printf(), et. al. "not portable, use _printf() instead", we should now use memcpy_s(). Let me go see where that is defined in the C standard. Oh, that's right, it isn't. It's only on Microsoft platforms.
So, what's going on here? Make up your own function (not in the C standard) to replace memcpy() and tell people to use that rather than memmove() (which is in the C standard). What the hell is the motivation here?
Funny thing is, i was just trying to remember the syntax for this earlier today. I was trying to determine whether my 64bit machine as LP or ILP. Shamefully, i broke down and wrote my code in a file and compiled that file. would've been nice to avoid that.
After working for my employer for 5 years on an H-1B visa, they started processing my green card. They know I am qualified, I have experience in this position, I get along with my coworkers and I am familiar with some of their trade secrets. Of course, at this point they are not interested in hiring anyone else, American or otherwise, for my position.
The law ends up having the effect that my company now needs to hire lawyers to go through this ridiculous process. This doesn't prove that they don't have legitimate reasons to want to keep me around. If they find a good candidate in the process, they will probably try to hire him for another position. They would still have to come up with a reason why he is not a good replacement for my position specifically (my company was hiring programmers at the time).
Dude, you're being duped. Your company is behaving this way very deliberately. It's called "green hand-cuffs". I used to work for a company that would hire H1B workers in for 30k less than their peers, encourage them to apply for a green card, then proceed to sit on their ass for 5 years. They'll give you pathetic excuses for why it isn't progressing. The truth is that they're sitting on the paperwork, trying to milk a low-wage employee for all they can. Some of my ex-coworkers came to this realization and were tempted to leave...only to find out they would need to 1) find another company to sponsor their H1B visa, 2) would have to restart the green card process from the beginning.
Don't accept excuses from your company. I've worked for another company that was getting green cards for their H1B workers in about a year to a year and a half (many times even less). It doesn't take six years to get a green card.
Rewatch that episode. The cellphone did affect the instruments on the cessna cockpit they were driving around on the back of their truck (to simulate "in-flight").
Then they did their tests on a brand-spanking-new Hawker (an expensive corporate jet). The Hawker wasn't affected by the cellphones. I can certainly believe that thing is sufficiently shielded so as not to be affect by cellphones.
I've flown in planes older than I am (34). I wouldn't put so much faith that those planes or perhaps even some newer ones are shielded enough to block out cellphones / electronics.
What are you talking about? That's precisely how I use vim (actually gvim + clewn).:make will invoke make to do the build. if you have any errors, VIM will jump to the file/line where the error occurred. I can bring up a window with the list of errors and go to each one. Clewn acts as an interface between vim and gdb. So, I can single-step through source code, set breakpoints, look at variables/watch points all from within VIM.
Re:Get Heavenly Sword - Its Brilliant.
on
Lair Review
·
· Score: 1
Dude, you have way to much free time on your hands! 20-25 hours in a week? That's half a regular work week. Actually, isn't that how many hours people put in at a part-time job? Sounds like you need to get out or get yourself a job man.
Re:Really not that bad
on
Lair Review
·
· Score: 3, Informative
Yeah, it's really not that bad. I feel the reviewers are being overly harsh. It sounds like most of them just do the initial basic tutorial and move onto the game and have a hard time controlling things. When I played it, I played the initial tutorial, level 1, then went back to the tutorial section and played through all the other tutorials. That probably helped immensely. I still struggled a bit with the 180 turns and the dragon battles that required me to shake the controller left and right. Otherwise, it responded to everything else just fine for me. It really wasn't this massive struggle they make it out to be.
I wish I still had mod points so I could mark your comment as flamebait. You obviously haven't played the game. It took me 12 hours to beat the game (yes, I timed it). And while that's still short (along the same lines as Gear of Wars short), it's no where near the claim of "5 hours with 2 hours of cutscenes". You simply made that up.
It's a really good game. Beautiful graphics, decent story, surprisingly good acting for a video game, and good gameplay. The gameplay is sort of a Goddess of War, but the different fighting stances and combos keeps it interesting and keeps it from getting repetitive. It's also the first PS3 game that I feel that uses the sixaxis well. Oh, and towards the later chapters, I felt the combat was rather intense and would have to take a long break from it after a half-hour to an hour of play.
Next time, try playing the game before you start bashing it.
Old school adventures didn't have no fancy static screens. Old school adventures were walls of text! And full of mazes of twisty little passages all alike. You young'ins and your shiny 8-bit graphics will never appreciate navigating a non-euclidean maze while fending off theives and grues. Bah!
Ever since I got a PS3, I've been video chatting with a friend of mine in England, a friend in the next city over and my family on the opposite coast. It seems the main limiting factor in our video chat quality is the upload rate of the person sending video. As a result, I get much better video from my friend in England (who has a rather large upload rate) then my friend in the next city over (who has the slowest upload rate...and is also using comcast).
Better upload rates are definately of interest. -tom
I'd say it depends. I would think a developer on Windows would have a better argument for multiple monitors since, despite its name, Windows is rather lousy at managing windows. A typical Windows usage model is to have an IDE fully maximied on one screen, and if anything else needs to be seen while developing, it helps to have it on a second monitor.
If the developer uses XWindows, then they are (generally) using a window manager which allows them to have several terminals, graphical editing programs and other apps sharing the same screen real-estate. A window manager allows the developer to quickly and effectively move between windows (focus follows mouse) and manage the layering of windows (Alt+F3 lower window, Alt+F1 raise window, etc). It's easier to have two windows open that partially obscure each other and quickly and effectively operate between the two. Add on top of this the added real-estate provided by virtual desktops and an XWindows user can get by with fewer physical screens. I suppose the exception to this would be if a single large real-estate application always needs to be up and visible. For example, a web developer would need a web browser up most of the time, and web browsers take up a good deal of screen real-estate.
Slashdot Mirror
This could've lead to a somewhat funny situation as well. QA could've filed a bug saying autofocus didn't work. Then by the time the developer looked at the bug, it could've been in the working period and the developer could've marked the bug as 'WORKSFORME'. Which, when it gets back to that QA guy's plate, depending on whether it was still in the working period or not, the QA guy could've tested it and marked it as 'RESOLVED' if it was working, or re-open the bug if it still wasn't working. If it was re-opened, the whole cycle could continue to repeat.
I don't know if such a thing happened, but it would've been funny (in hindsight at least) if it had.
Actually, it's required to pass your checkride. The FAA examiner will at some point during your checkride do something to distract you and see how well you react to it (drop a pencil on your side of the floor, ask you to calculate true airspeed, etc.).
What's needed are higher standards for driving period. Right now, practically anyone can pass a driver's test and the written test is a joke. If it was more like getting a pilot's license, (harder test, more extensive practical test, required number of hours driving with an instructor), we'd probably all be a lot safer. Fewer idiots would pass the tests and be on the road. Only safe drivers and really determined idiots would be on the road :)
Umm, I think so Brain. But why do we need polka dotted pants at a lan party? Narf!
Hi, nice to meet you. Now increment the number of people you know who cut their teeth writing code on the linux kit before getting into the games business by 1. The Linux kit helped me get to know the GS and VU0, VU1, which came in handy a few months / year later when I interviewed for a position at Playstation (and then got that position). I work elsewhere now, but that PS2 Linux kit was definately valuable to me.
I knew a guy who was a Physicist. Government cancelled the program he was working on. It was highly classified, so he couldn't put his work experience on a resumé. He decided to take classes at a local community college and got a job delivering pizzas. He eventually got his degree in Computer Science and came to work with us at Kennedy Space Center.
Smart guy. And I really respect how he took a job he normally wouldn't do in order to help re-educate himself in a new field.
I used to ask the same question. I now work for a small startup. Most of us develop on Linux, a couple on Windows, and a couple on Mac. If we could afford to do a linux-only version, we would. But in order to have any kind of marketshare on the desktop, we need to output a Windows version.
The mac and linux versions mostly "just work" and simply need testing. But about a month before release, the entire team needs to stop what they're doing and get the Windows version fully working and tested. Windows development is a resource hog (in terms of people). In some ways, Windows is just different, but it seems in many ways, Windows is deliberately incompatable with anything else at the source code level. Windows makes it as difficult as possible to be cross-platform.
As a result, we get the Windows version out and working before we have time to test the Linux and Mac versions. It kinda sucks to spend that much time and resources on a Windows version. It's either that, or re-route our development resources to Windows-only and ignore the other platforms. Of course, we don't want to do that.
Either Microsoft is really stupid or really evil. Along with declaring printf(), et. al. "not portable, use _printf() instead", we should now use memcpy_s(). Let me go see where that is defined in the C standard. Oh, that's right, it isn't. It's only on Microsoft platforms.
So, what's going on here? Make up your own function (not in the C standard) to replace memcpy() and tell people to use that rather than memmove() (which is in the C standard). What the hell is the motivation here?
Here I was hoping it was about Structures of Arrays vs. Arrays of Structures. Oh well.
In fact, forget the blackjack and goodwill!
Gah, hate to reply to my own post, but I got it working:
cat << eof | cc -x c -
i picked 'eof' as the marker of my end of input. you can pick whatever you like.
the compiler needs to know what language it is compiling, thus -x c
and finally tell the compiler to read from stdin with '-'
I got the same thing:
cc: no input files
I tried bash and tcsh. I'm on Fedora Core 8.
Funny thing is, i was just trying to remember the syntax for this earlier today. I was trying to determine whether my 64bit machine as LP or ILP. Shamefully, i broke down and wrote my code in a file and compiled that file. would've been nice to avoid that.
After working for my employer for 5 years on an H-1B visa, they started processing my green card. They know I am qualified, I have experience in this position, I get along with my coworkers and I am familiar with some of their trade secrets. Of course, at this point they are not interested in hiring anyone else, American or otherwise, for my position.
The law ends up having the effect that my company now needs to hire lawyers to go through this ridiculous process. This doesn't prove that they don't have legitimate reasons to want to keep me around. If they find a good candidate in the process, they will probably try to hire him for another position. They would still have to come up with a reason why he is not a good replacement for my position specifically (my company was hiring programmers at the time).
Dude, you're being duped. Your company is behaving this way very deliberately. It's called "green hand-cuffs". I used to work for a company that would hire H1B workers in for 30k less than their peers, encourage them to apply for a green card, then proceed to sit on their ass for 5 years. They'll give you pathetic excuses for why it isn't progressing. The truth is that they're sitting on the paperwork, trying to milk a low-wage employee for all they can. Some of my ex-coworkers came to this realization and were tempted to leave...only to find out they would need to 1) find another company to sponsor their H1B visa, 2) would have to restart the green card process from the beginning.
Don't accept excuses from your company. I've worked for another company that was getting green cards for their H1B workers in about a year to a year and a half (many times even less). It doesn't take six years to get a green card.
Rewatch that episode. The cellphone did affect the instruments on the cessna cockpit they were driving around on the back of their truck (to simulate "in-flight").
Then they did their tests on a brand-spanking-new Hawker (an expensive corporate jet). The Hawker wasn't affected by the cellphones. I can certainly believe that thing is sufficiently shielded so as not to be affect by cellphones.
I've flown in planes older than I am (34). I wouldn't put so much faith that those planes or perhaps even some newer ones are shielded enough to block out cellphones / electronics.
Store the power in Energon Cubes. Then let me know where you put those >;-)
Thanks,
Megatron
What are you talking about? That's precisely how I use vim (actually gvim + clewn). :make will invoke make to do the build. if you have any errors, VIM will jump to the file/line where the error occurred. I can bring up a window with the list of errors and go to each one. Clewn acts as an interface between vim and gdb. So, I can single-step through source code, set breakpoints, look at variables/watch points all from within VIM.
If you're going live in Silicon Valley, learn all of the above.
Isn't this thing just the elumens projection screen (www.est-kl.com/projection/elumens/projection.html) without the proper distortion correction?
Forget the hideout. The true evil scientist would figure out a way to aim it.
they want their 14.4 modem back.
Dude, you have way to much free time on your hands! 20-25 hours in a week? That's half a regular work week. Actually, isn't that how many hours people put in at a part-time job? Sounds like you need to get out or get yourself a job man.
Yeah, it's really not that bad. I feel the reviewers are being overly harsh. It sounds like most of them just do the initial basic tutorial and move onto the game and have a hard time controlling things. When I played it, I played the initial tutorial, level 1, then went back to the tutorial section and played through all the other tutorials. That probably helped immensely. I still struggled a bit with the 180 turns and the dragon battles that required me to shake the controller left and right. Otherwise, it responded to everything else just fine for me.
It really wasn't this massive struggle they make it out to be.
I really don't understand what their problem is.
I wish I still had mod points so I could mark your comment as flamebait. You obviously haven't played the game. It took me 12 hours to beat the game (yes, I timed it). And while that's still short (along the same lines as Gear of Wars short), it's no where near the claim of "5 hours with 2 hours of cutscenes". You simply made that up.
It's a really good game. Beautiful graphics, decent story, surprisingly good acting for a video game, and good gameplay. The gameplay is sort of a Goddess of War, but the different fighting stances and combos keeps it interesting and keeps it from getting repetitive. It's also the first PS3 game that I feel that uses the sixaxis well. Oh, and towards the later chapters, I felt the combat was rather intense and would have to take a long break from it after a half-hour to an hour of play.
Next time, try playing the game before you start bashing it.
Get off my lawn!
Old school adventures didn't have no fancy static screens. Old school adventures were walls of text! And full of mazes of twisty little passages all alike. You young'ins and your shiny 8-bit graphics will never appreciate navigating a non-euclidean maze while fending off theives and grues. Bah!
xyzzy
Upload isn't just for p2p.
Ever since I got a PS3, I've been video chatting with a friend of mine in England, a friend in the next city over and my family on the opposite coast. It seems the main limiting factor in our video chat quality is the upload rate of the person sending video. As a result, I get much better video from my friend in England (who has a rather large upload rate) then my friend in the next city over (who has the slowest upload rate...and is also using comcast).
Better upload rates are definately of interest.
-tom
I'd say it depends. I would think a developer on Windows would have a better argument for multiple monitors since, despite its name, Windows is rather lousy at managing windows. A typical Windows usage model is to have an IDE fully maximied on one screen, and if anything else needs to be seen while developing, it helps to have it on a second monitor.
If the developer uses XWindows, then they are (generally) using a window manager which allows them to have several terminals, graphical editing programs and other apps sharing the same screen real-estate. A window manager allows the developer to quickly and effectively move between windows (focus follows mouse) and manage the layering of windows (Alt+F3 lower window, Alt+F1 raise window, etc). It's easier to have two windows open that partially obscure each other and quickly and effectively operate between the two. Add on top of this the added real-estate provided by virtual desktops and an XWindows user can get by with fewer physical screens. I suppose the exception to this would be if a single large real-estate application always needs to be up and visible. For example, a web developer would need a web browser up most of the time, and web browsers take up a good deal of screen real-estate.