Skip Navigation
Google is so bad these days, nothing but shitty SEO results
  • Google definitely has its moments of returning crap results, but you chose a terrible example.

    Results from both docker and redis, on topic for exactly what you asked for.

    Why even use Google at all, when you could search docker hub If that’s what you knew you wanted.

  • It's almost impossible to deny being an alcoholic without sounding like an alcoholic
  • Haha yeah it’s weird how NOT drinking is weird. I couldn’t care less what other people do, nor what they think of me; drinking is just no longer appealing to me

    No idea why you got downvoted so bad, I guess I did have the benefit of your edit when I read your reply.

  • Red flags in software engineers
  • Which do you agree with?

    Edit: There is maybe one that’s semi-ok (reversing a linked list) but it’s not a red flag if an engineer can’t do it on the spot.

    In my decade+ career, I’ve used a linked list in production code….. maybe twice? Thats not to say they aren’t useful, but I don’t make a habit of committing stuff to my memory unless I’m going to use it.

    Could I do it? Absolutely. Could I do it without searching it up? Yea. Would I search it up anyway? 100%

  • Which database service can you recommend? Like MonoDB
  • What use case are you trying to solve? Do you need a relational database? Do you want to self host or rely on another service/company to manage it for you?

    There’s so many questions to answer before a recommendation can be made.

  • Female surgeons sexually assaulted while operating
  • What are you going on about?

    Nobody in this thread has said “not all men”.

    The top comment said “can people just not suck”, then OP responded saying “actually, in this case, only men suck”.

  • Happy Labor Day! I labored over a Taylor Swift Acronym Lookup app, and I'd love some feedback
  • The 404 should just say the same message as “acronym not found”. It just means the first 4 letters didn’t match a file on the backend; I didn’t enumerate all the blank json for A-Z*4.

    Yeah, but it doesn't translate to the site. That's what I'm trying to say :) Your catch above doesn't distinguish between 404 or anything else (5xxx) and displays An error occurred while processing your request. Please try again later for all eventualities. So, regardless whether the acronym wasn't found or there was a genuine server error, the same error message is displayed.

    It was a really challenging project to process all the data. As with most large datasets, there are tons of pain points. Like 60% of the time spent was parsing out the song name from the janky first line of metadata. Some pain I dealt with over the project off the top of my head:

    I honestly have no idea what you had to drag it all out from, but it looks well implemented from the small amount I played around with it. I've never used Firebase, but it looks like you got it working so that's a good job too.

    It's probably just my old man brain that saw you were doing this all with files and it felt odd. That's not to say it's wrong, it's just different to what I would have done.

    There's a bunch of advantages to databases, like indexes and partial/fuzzy text matching - but I can certainly understand why you went this route if you needed to keep costs down and didn't want to bother with any DB maintenance.

    Well done :)

  • Happy Labor Day! I labored over a Taylor Swift Acronym Lookup app, and I'd love some feedback
  • Yeah, that error message is left over from an earlier version where I sharded by acronym length instead. At that time, there would always be a file. The problem was the files were getting to be huge at the 50 character length (20MB) and performance went to shit on poor mobile connections. So I refactored to shard by first 4, and files dropped down to a few K each and became a lot snappier.

    I don't think that's necessarily true. I just tried a random string, and I got the correct 404 response back, but it doesn't look like the app handles that case and it just prints that error on any error.

                .catch(error => {
                    console.error("Error fetching or processing the JSON file:", error);
                    displayError("An error occurred while processing your request. Please try again later.", tableBody);
                });
    

    Anyway, I wasn't trying to shit on it. Good job :)

  • Happy Labor Day! I labored over a Taylor Swift Acronym Lookup app, and I'd love some feedback
  • I have no skin in the game for the app itself, I just saw your post on the “front page” while scrolling and shitting….

    there are 30,000 files

    I’m more intrigued why you appear to be managing this with files. Why not use a database?

    Edit: you’re also not handling misses very well. I just tried a random string and got the below error. That doesn’t tell me if it was my fault or a server error.

    An error occurred while processing your request. Please try again later.

  • Lemmy Support @lemmy.ml devdad @programming.dev
    Disk space required for lemmy instance?

    With vlemmy disappearing, I’m considering spinning up a VM and sticking it in a DMZ for my own personal use (and any friends who wish to use Lemmy).

    I believe there is caching involved, so does anybody have a good idea of how much disk space an instance for say ~10 users would require?

    13
    InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)DE
    devdad @programming.dev
    Posts 1
    Comments 49