In theory you can expand the image to 3d by clipping each object and vertically slicing it into layers (for a tree, or horizontally for a bench) then adding 3D effect to the layers, filling in where there is gaps and overlaying where needed, for each object in each frame of the film, then composit all the objects and masks back on to the scene. Now that you've spent ~100 hours on that your first frame is done, time to do the next, but now it's harder because you need to account for motion so your clipping masks are no the same AR as the previous frame and your fill/overlap layers changed as well since the perspective has changed. Wash rinse repeat for the rest of your life to finish a 10 minute clip. possible to do right? yes. practical? not at all. -nB
because they wouldn't make enough money to make it worth it. Redbox is about at the floor of cost at $1/day. Even with all the automation you have to pay people to stock the machines, you get damaged disks from wear and tear, no one rental caused the issue so you can't charge it back to the last renter. You have to pay the cost of the machines, and the maintenance on them. Honestly I'm surprised that Redbox is profitable at $1/day. All it takes is someone damaging your machine and you're back in the hole. -nB
This all would have been different if, instead of refusing to get back on the ship, there was a recording of him demanding the CG find a way to get him back on his ship ASAP... Would have made his "I fell in the lifeboat" spheel a little easier to swallow.
No one said he couldn't change his mind. I take that to be not that he was wrong or misquoted, but rather to mean: You needed those rules then, now you need these. FWIW at least, IANAbibleStudiesGuy
Besides recovering the oil is profitable, especially when compared to pumping oil out of the ground and transporting the crude and refining to fuel and transporting the fuel. This one only has the first and last steps, cutting out the middle steps: pump oil out of ship, transport to fuel depot.
Also, the ship may be salvageable. even if it costs $10M to repair and another $5M to salvage it you're still ahead $10M compared to buying a new one. -nB
To the netflix thing: They could fix this easily by allowing sub accounts to stream, but only if another account is not currently streaming. The main account gets the same error, but with the option of bumping the currently playing stream.
As to PWDs, another excellent reason not to share with anyone other than a priest while confessing, a Lawyer on your retainer, or a spouse is privilege. They can not be forced to divulge the info.
*this* The first time I discovered XKCD about a year and a half ago I started at the beginning and went through them all. I decided Randall is not only smarter then me, but smarter than most of those I think of as mentors. A week later someone told me that there was alt text that needed to be read as well. *sob* back to the first comic I went and started over. To be fair I learned stuff from the alt text.
I know you were not the one to suggest I leave, just decided to ball both responses together.
I don't actually disagree, it's just that since this is an inherited codebase and the dev team we have in place now is relatively junior, I would rather not futz with the existing code. We avoid introducing any more code like this, but the legacy stuff is still there.
In the case of point 1 I agree with the provision that I can ram a style guide down people's throat to limit how they do this. I am concerned that once you allow goto's into the code they will find each other and multiply, resulting in summing cithulu or the flying spaghetti monster. Humans beeing what they are, if they think a goto makes it easier to code up, they will, without a thought for maintainability in the future. As it sits now, there are three gotos in the code, all documented, all reviewed. Easy to find when you search for goto. If we use them more openly then it will be harder to find potentially bad uses. I think that is my biggest argument in favor of do while 0.
In the case of point 2, I'm not sure if we could make that portable enough to fit on the embedded firmware. The host OS application is the bulk of the code, but the smaller portion that exists on the embedded device (and also exists on the host) is severely memory constrained.
My current job is almost entirely code cleanup, I'm focusing on logic errors and compatibility issues, rather than style issues, largely because the former two impact functionality. If I can clean up style while I'm at it, I do. -nB
meh, I'd make a file named achievements.h and.c, then dump all the stuff in there. Link it in once to make all the badges come up, then #IFDEF it out. -nB
To be fair, the code is reliable, stable, and the Do{}while(0);'s are not so long as to be trouble tracing. This is all C code, not C++, and has to be cross compatible with embedded firmware, Windows, and Linux. Also, since that's close to the largest sin in the codebase, I'll not be leaving anytime soon.
so at the end of this you either passed everything or you know where you borked. Are there better ways? yes. Does this work in a very compatible way? yes. Is it broken? no. Shall I then fix it? no.
Every time I see an ask/. about "I hate my job" or "My job is asking foo of me but my job is bar", I count my lucky stars that my job is sane, well defined, challenging, and the worst of it is a couple (hundred) thousand lines of code that contain some dailywtf worthy examples. -nB
That's funny. The codebase I inherited is *full* of do{}while(0); with a bunch of breaks inside of the do to jump out at any point something goes haywire. Come work for my team, your day will never suck (at least my that metric). -nB
I think you have your service interval wrong on the race engines. My buddy rebuilds his after every couple races. F1 used to swap in a new engine before every race (they made that impossible by limiting them to 12 engines per season). Those get rebuilt after every race and after qualifying. -nB
I heat up my truck just enough to melt the ice on the windshield. I have a 5.7 hemi and it doesn't do too much worse on winter gas. Same as you, it can run E85, but not on the factory hoses. I ran one tank because I was curious and mileage bailed (and stayed bad for another tank of gas because the computer corrected for the E85). -nB
Not always possible. We have a greybeard that is currently irreplaceable. He's not an ass, or BOFH, or anything (a bit brash and abrasive, but whatever). Problem is he can do magic in low level code that I can barely follow. Currently he is training me on some of the more obscure components that until now he is the only one to have touched them. This is because until now they have always worked and he did any "minor" maintenance that was needed. Last senior dev to touch the code caused the entire codebase to not compile, or to compile but not work properly. Here is the catch: he's dying. On the list for a lung transplant, but he is still smoking, so he won't be getting one. If he died now we'd be fscked. People familiar with the codebase can't fix it. I'm a jr dev, but he's making me his protegee, and I in turn will train someone else because I want to be able to leave on vacation. -nB
Because while we are cogs, some of us fill a niche that is rather unique and not easily done by someone else filling in. When I'm on vacation I have a mail filter running. Only two e-mail addresses get through: My Boss, and my stand-in. -nB
I work 18 hours a day, because if I don't, the others will screw up any tasks I let them do. I spend 16 hours a day fixing their mistakes so the customers don't find them. Within 5 minutes of walking out of the hospital, my phone was ringing off the hook. Within 10 minutes of getting out of the hospital, I was on my laptop trying to fix the problem, and fielding back to back phone calls.
Cause: Serious Type A. Get a shrink. (seriously, not trolling, I have one and it's done wonders.) -nB
Wow. Polar opposite at my company. That said, we are known in the industry for being aggressive and *ahem* direct, even compared to our peer companies. I think my brain (or skull) would break (get broken) working there. It sounds nice, but there would be some sort of decompression period that would be akin to the bends and I'd need a serious pressure chamber...
Yeah, I don't see the contractor life as appealing. I get that the money is better, but I like the group health insurance, 401k match, etc. To each his own I suppose. I've got to stick with GP, that I'd stick around and train my replacement. I might be a dick about it and *only* train my replacement, not fight any other fires, but I would train them. Would take almost a year IMHO, I've been doing this one job for 5 years and I still don't know everything about the codebase I inherited (that is still under active dev).
Also: I have notified all my co-workers that if they ever get a lunch invite to sushi, my treat, at the local hotspot for lunch, they can safely assume I'm not going to be there much longer, as there is no monetary reason to stay. -nB
Slashdot Mirror
In theory you can expand the image to 3d by clipping each object and vertically slicing it into layers (for a tree, or horizontally for a bench) then adding 3D effect to the layers, filling in where there is gaps and overlaying where needed, for each object in each frame of the film, then composit all the objects and masks back on to the scene. Now that you've spent ~100 hours on that your first frame is done, time to do the next, but now it's harder because you need to account for motion so your clipping masks are no the same AR as the previous frame and your fill/overlap layers changed as well since the perspective has changed. Wash rinse repeat for the rest of your life to finish a 10 minute clip.
possible to do right? yes.
practical? not at all.
-nB
http://xkcd.com/941/ FTFY
because they wouldn't make enough money to make it worth it. Redbox is about at the floor of cost at $1/day. Even with all the automation you have to pay people to stock the machines, you get damaged disks from wear and tear, no one rental caused the issue so you can't charge it back to the last renter. You have to pay the cost of the machines, and the maintenance on them.
Honestly I'm surprised that Redbox is profitable at $1/day. All it takes is someone damaging your machine and you're back in the hole.
-nB
This is a good thing, the more awareness about the TSA from lawmakers will bring about a much needed reigning in.
-nB
This all would have been different if, instead of refusing to get back on the ship, there was a recording of him demanding the CG find a way to get him back on his ship ASAP... Would have made his "I fell in the lifeboat" spheel a little easier to swallow.
No one said he couldn't change his mind. I take that to be not that he was wrong or misquoted, but rather to mean: You needed those rules then, now you need these.
FWIW at least, IANAbibleStudiesGuy
This would work. Worlds biggest tiki candle!
Besides recovering the oil is profitable, especially when compared to pumping oil out of the ground and transporting the crude and refining to fuel and transporting the fuel. This one only has the first and last steps, cutting out the middle steps: pump oil out of ship, transport to fuel depot.
Also, the ship may be salvageable. even if it costs $10M to repair and another $5M to salvage it you're still ahead $10M compared to buying a new one.
-nB
To the netflix thing:
They could fix this easily by allowing sub accounts to stream, but only if another account is not currently streaming. The main account gets the same error, but with the option of bumping the currently playing stream.
As to PWDs, another excellent reason not to share with anyone other than a priest while confessing, a Lawyer on your retainer, or a spouse is privilege. They can not be forced to divulge the info.
*this*
The first time I discovered XKCD about a year and a half ago I started at the beginning and went through them all. I decided Randall is not only smarter then me, but smarter than most of those I think of as mentors.
A week later someone told me that there was alt text that needed to be read as well.
*sob*
back to the first comic I went and started over. To be fair I learned stuff from the alt text.
I know you were not the one to suggest I leave, just decided to ball both responses together.
I don't actually disagree, it's just that since this is an inherited codebase and the dev team we have in place now is relatively junior, I would rather not futz with the existing code. We avoid introducing any more code like this, but the legacy stuff is still there.
In the case of point 1 I agree with the provision that I can ram a style guide down people's throat to limit how they do this. I am concerned that once you allow goto's into the code they will find each other and multiply, resulting in summing cithulu or the flying spaghetti monster. Humans beeing what they are, if they think a goto makes it easier to code up, they will, without a thought for maintainability in the future. As it sits now, there are three gotos in the code, all documented, all reviewed. Easy to find when you search for goto. If we use them more openly then it will be harder to find potentially bad uses. I think that is my biggest argument in favor of do while 0.
In the case of point 2, I'm not sure if we could make that portable enough to fit on the embedded firmware. The host OS application is the bulk of the code, but the smaller portion that exists on the embedded device (and also exists on the host) is severely memory constrained.
My current job is almost entirely code cleanup, I'm focusing on logic errors and compatibility issues, rather than style issues, largely because the former two impact functionality. If I can clean up style while I'm at it, I do.
-nB
so gcc, vim, coffee, and a gun then. Glad we all agree ;)
meh, .c, then dump all the stuff in there. Link it in once to make all the badges come up, then #IFDEF it out.
I'd make a file named achievements.h and
-nB
To be fair, the code is reliable, stable, and the Do{}while(0);'s are not so long as to be trouble tracing. This is all C code, not C++, and has to be cross compatible with embedded firmware, Windows, and Linux. Also, since that's close to the largest sin in the codebase, I'll not be leaving anytime soon.
the general layout is of the general style:
enum tonsOfStatusCodes{PASS=0,FAIL,CUSTOM,foo, bar,baz}; ...
tonsOfStatusCodes status = FAIL;
do{
status=customMalloc(ptr);
if(status){break;}
status=populateData(ptr);
if(status){break;}
status=transmogrifyData(ptr);
}while(0);
so at the end of this you either passed everything or you know where you borked.
Are there better ways? yes.
Does this work in a very compatible way? yes.
Is it broken? no.
Shall I then fix it? no.
Every time I see an ask /. about "I hate my job" or "My job is asking foo of me but my job is bar", I count my lucky stars that my job is sane, well defined, challenging, and the worst of it is a couple (hundred) thousand lines of code that contain some dailywtf worthy examples.
-nB
That's funny. The codebase I inherited is *full* of do{}while(0); with a bunch of breaks inside of the do to jump out at any point something goes haywire. Come work for my team, your day will never suck (at least my that metric).
-nB
I'm going with option one based on Occam's razor, however I *really* want to believe option two.
I think you have your service interval wrong on the race engines.
My buddy rebuilds his after every couple races.
F1 used to swap in a new engine before every race (they made that impossible by limiting them to 12 engines per season). Those get rebuilt after every race and after qualifying.
-nB
I heat up my truck just enough to melt the ice on the windshield.
I have a 5.7 hemi and it doesn't do too much worse on winter gas.
Same as you, it can run E85, but not on the factory hoses. I ran one tank because I was curious and mileage bailed (and stayed bad for another tank of gas because the computer corrected for the E85).
-nB
Not always possible.
We have a greybeard that is currently irreplaceable. He's not an ass, or BOFH, or anything (a bit brash and abrasive, but whatever). Problem is he can do magic in low level code that I can barely follow. Currently he is training me on some of the more obscure components that until now he is the only one to have touched them. This is because until now they have always worked and he did any "minor" maintenance that was needed. Last senior dev to touch the code caused the entire codebase to not compile, or to compile but not work properly.
Here is the catch: he's dying. On the list for a lung transplant, but he is still smoking, so he won't be getting one. If he died now we'd be fscked.
People familiar with the codebase can't fix it. I'm a jr dev, but he's making me his protegee, and I in turn will train someone else because I want to be able to leave on vacation.
-nB
Because while we are cogs, some of us fill a niche that is rather unique and not easily done by someone else filling in. When I'm on vacation I have a mail filter running. Only two e-mail addresses get through: My Boss, and my stand-in.
-nB
Effect:
high blood pressure and a TIA.
Trigger:
I work 18 hours a day, because if I don't, the others will screw up any tasks I let them do. I spend 16 hours a day fixing their mistakes so the customers don't find them. Within 5 minutes of walking out of the hospital, my phone was ringing off the hook. Within 10 minutes of getting out of the hospital, I was on my laptop trying to fix the problem, and fielding back to back phone calls.
Cause:
Serious Type A. Get a shrink. (seriously, not trolling, I have one and it's done wonders.)
-nB
Wow.
Polar opposite at my company. That said, we are known in the industry for being aggressive and *ahem* direct, even compared to our peer companies. I think my brain (or skull) would break (get broken) working there. It sounds nice, but there would be some sort of decompression period that would be akin to the bends and I'd need a serious pressure chamber...
To borrow from Rush fans...
Mega Dittos.
My employer has never given less than a 2 month severance that I know of (other than termination for cause).
Yeah, I don't see the contractor life as appealing. I get that the money is better, but I like the group health insurance, 401k match, etc. To each his own I suppose.
I've got to stick with GP, that I'd stick around and train my replacement. I might be a dick about it and *only* train my replacement, not fight any other fires, but I would train them. Would take almost a year IMHO, I've been doing this one job for 5 years and I still don't know everything about the codebase I inherited (that is still under active dev).
Also: I have notified all my co-workers that if they ever get a lunch invite to sushi, my treat, at the local hotspot for lunch, they can safely assume I'm not going to be there much longer, as there is no monetary reason to stay.
-nB