error in jpg...
-
Well... We recently sent our client an update for the mockups of a new website we're about to start developing, in the form of a zip containing a couple of jpeg images (actually the images were mockups for the custom 404 and 500 error pages). So far so good. Minutes later, our PM got an angry call from the client. Here's how it roughly went down: [Client]: Hey, the mockups you sent over are not working at all. All I'm getting is errors! [PM]: What do you mean, that the zip file is corrupt? That you can't open the images? [Client]: No, the zip is not corrupt, and I can "open" the files, but when I do, I get an error! Fix it NOW! [PM]: Ok... What kind of error? [Client]: I get a 404 error on one image and a 500 error on the other. I said, FIX IT NOW!!! [PM]: hm, you do realize that you're seeing the MOCKUPS for the CUSTOM ERROR pages, right? That you're supposed to see an IMAGE displaying an ERROR. Right? [Client]:...
Φευ! Εδόμεθα υπό ρηννοσχήμων λύκων! (Alas! We're devoured by lamb-guised wolves!)
-
Well... We recently sent our client an update for the mockups of a new website we're about to start developing, in the form of a zip containing a couple of jpeg images (actually the images were mockups for the custom 404 and 500 error pages). So far so good. Minutes later, our PM got an angry call from the client. Here's how it roughly went down: [Client]: Hey, the mockups you sent over are not working at all. All I'm getting is errors! [PM]: What do you mean, that the zip file is corrupt? That you can't open the images? [Client]: No, the zip is not corrupt, and I can "open" the files, but when I do, I get an error! Fix it NOW! [PM]: Ok... What kind of error? [Client]: I get a 404 error on one image and a 500 error on the other. I said, FIX IT NOW!!! [PM]: hm, you do realize that you're seeing the MOCKUPS for the CUSTOM ERROR pages, right? That you're supposed to see an IMAGE displaying an ERROR. Right? [Client]:...
Φευ! Εδόμεθα υπό ρηννοσχήμων λύκων! (Alas! We're devoured by lamb-guised wolves!)
-
Well... We recently sent our client an update for the mockups of a new website we're about to start developing, in the form of a zip containing a couple of jpeg images (actually the images were mockups for the custom 404 and 500 error pages). So far so good. Minutes later, our PM got an angry call from the client. Here's how it roughly went down: [Client]: Hey, the mockups you sent over are not working at all. All I'm getting is errors! [PM]: What do you mean, that the zip file is corrupt? That you can't open the images? [Client]: No, the zip is not corrupt, and I can "open" the files, but when I do, I get an error! Fix it NOW! [PM]: Ok... What kind of error? [Client]: I get a 404 error on one image and a 500 error on the other. I said, FIX IT NOW!!! [PM]: hm, you do realize that you're seeing the MOCKUPS for the CUSTOM ERROR pages, right? That you're supposed to see an IMAGE displaying an ERROR. Right? [Client]:...
Φευ! Εδόμεθα υπό ρηννοσχήμων λύκων! (Alas! We're devoured by lamb-guised wolves!)
Sounds like the only thing that needs fixing is the client! :laugh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Sounds like the only thing that needs fixing is the client! :laugh:
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
Client can not be fixed! And 101% of clients behave like this in a lot of occasions...Better get used to it...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
Client can not be fixed! And 101% of clients behave like this in a lot of occasions...Better get used to it...
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
You must not know IBM System/360 programming: XC - eXecute Client (actually Xor Character) EDIT: For the humour-impaired, this was intended to raise a smile. It perhaps did not achieve the desired effect, but I certainly do not advocate harming clients in any way.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
-
You must not know IBM System/360 programming: XC - eXecute Client (actually Xor Character) EDIT: For the humour-impaired, this was intended to raise a smile. It perhaps did not achieve the desired effect, but I certainly do not advocate harming clients in any way.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
I'm old enought to learn on mainframe and I can remember that eXecute here means this: https://en.wikipedia.org/wiki/Contract_killing[^]
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
-
I'm old enought to learn on mainframe and I can remember that eXecute here means this: https://en.wikipedia.org/wiki/Contract_killing[^]
Skipper: We'll fix it. Alex: Fix it? How you gonna fix this? Skipper: Grit, spit and a whole lotta duct tape.
You must have had some really weird instructors (and an even weirder mainframe :omg: ).
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack. --Winston Churchill
-
Well... We recently sent our client an update for the mockups of a new website we're about to start developing, in the form of a zip containing a couple of jpeg images (actually the images were mockups for the custom 404 and 500 error pages). So far so good. Minutes later, our PM got an angry call from the client. Here's how it roughly went down: [Client]: Hey, the mockups you sent over are not working at all. All I'm getting is errors! [PM]: What do you mean, that the zip file is corrupt? That you can't open the images? [Client]: No, the zip is not corrupt, and I can "open" the files, but when I do, I get an error! Fix it NOW! [PM]: Ok... What kind of error? [Client]: I get a 404 error on one image and a 500 error on the other. I said, FIX IT NOW!!! [PM]: hm, you do realize that you're seeing the MOCKUPS for the CUSTOM ERROR pages, right? That you're supposed to see an IMAGE displaying an ERROR. Right? [Client]:...
Φευ! Εδόμεθα υπό ρηννοσχήμων λύκων! (Alas! We're devoured by lamb-guised wolves!)
Typical of clients. Get used to it. It's going to happen far more often than you can put up with.
A guide to posting questions on CodeProject
Click this: Asking questions is a skill. Seriously, do it.
Dave Kreskowiak -
Well... We recently sent our client an update for the mockups of a new website we're about to start developing, in the form of a zip containing a couple of jpeg images (actually the images were mockups for the custom 404 and 500 error pages). So far so good. Minutes later, our PM got an angry call from the client. Here's how it roughly went down: [Client]: Hey, the mockups you sent over are not working at all. All I'm getting is errors! [PM]: What do you mean, that the zip file is corrupt? That you can't open the images? [Client]: No, the zip is not corrupt, and I can "open" the files, but when I do, I get an error! Fix it NOW! [PM]: Ok... What kind of error? [Client]: I get a 404 error on one image and a 500 error on the other. I said, FIX IT NOW!!! [PM]: hm, you do realize that you're seeing the MOCKUPS for the CUSTOM ERROR pages, right? That you're supposed to see an IMAGE displaying an ERROR. Right? [Client]:...
Φευ! Εδόμεθα υπό ρηννοσχήμων λύκων! (Alas! We're devoured by lamb-guised wolves!)
Next time you send a mock up clearly describe what you are sending,
this is a mock up of the the custom error pagesand you would not have a pissed off, embarrassed client. If you did describe it correctly then you are running up against the standard reaction of a client, they hire you therefore they feel they have the right to yell at you.Never underestimate the power of human stupidity RAH
-
Next time you send a mock up clearly describe what you are sending,
this is a mock up of the the custom error pagesand you would not have a pissed off, embarrassed client. If you did describe it correctly then you are running up against the standard reaction of a client, they hire you therefore they feel they have the right to yell at you.Never underestimate the power of human stupidity RAH
Mycroft Holmes wrote:
Next time you send a mock up clearly describe what you are sending,
this is a mock up of the the custom error pagesand you would not have a pissed off, embarrassed client.Yeah, we did describe it. Something along the lines of "please review the images that show the design of the custom error pages". From what I know, a few hours later, both the client and the PM were laughing about it (kudos to the client for being able to be auto-sarcastic).
Φευ! Εδόμεθα υπό ρηννοσχήμων λύκων! (Alas! We're devoured by lamb-guised wolves!)
