22
T0D0
40d

Diary of an insane lead dev: day 447

pdf thumbnails that the app generates are now in S3 instead of saved on disk.

when they were on disk, we would read them from disk into a stream and then create a stream response to the client that would then render the stream in the UI (hey, I didn't write it, I just had to support it)

one of my lazy ass junior devs jumps on modifying it before I can; his solution is to retrieve the file from the cloud now, convert the stream into a base64 encoded string, and then shove that string into an already bloated viewmodel coming from the server to be rendered in the UI.

i'm like "why on earth are you doing that? did you even test the result of this and notice that rendering those thumbnails now takes 3 times as long???"

jr: "I mean, it works doesn't it?"

seriously, if the image file is already hosted on the cloud, and you can programmatically determine its URL, why wouldn't you just throw that in the src attribute in your html tag and call it a day? why would you possibly think that the extra overhead of retrieving and converting the file before passing it off to the UI in an even larger payload than before would result in a good user experience for the client???

it took me all of 30 seconds to google and find out that AWS SDK has a method to GetPreSignedURL on a private file uploaded to s3 and you can set when it expires, and the application is dead at the end of the year.

JFC. I hate trying to reason with these fuckheads by saying "you are paid for you brain, fucking USE IT" because, clearly these code monkeys do not have brains.

Comments
  • 4
    Modern webshitters seem to do this all the time. I can only conclude the thought process ends at, "well the browser file API requires me to create objectURLs or base64 encoded urls to work with local images, so servers must work that way too." "Native handlers" and "protocols" don't seem to compute.

    Might want to point out to him that base64 ends up being ~1/3rd more data than the same value not base64.
  • 3
    That's surprisingly complex for the usual Jr dev story...
  • 1
    It's because HTML is too difficult for your run-off-the-mill web dev. On MANY fronts.
Add Comment