home.social

#namingthingsishard — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #namingthingsishard, aggregated by home.social.

  1. How many projects have you abandoned simply because it took you too long to figure out what to call the thing?!

  2. How many projects have you abandoned simply because it took you too long to figure out what to call the thing?!

    #WebDev #namingThingsIsHard

  3. Griechische Mythologie nervt.

    Nie gibt es die richtigen Göttinnen für die Dinge die ich benennen will 😡

    #namingThingsIsHard

  4. Can't believe I got phishing from IT Iffy Consultants.

    Even if it had been spam rather than phishing, would you really want to hire iffy consultants? 😆

    (They might be trendy Apple-style "i-Tiffy Consultants" - whatever a "tiffy" is - but that's just asking for it, like being penisland.com or expertsexchange.com or whorepresents.com)

    #NamingThingsIsHard

  5. Can't believe I got phishing from IT Iffy Consultants.

    Even if it had been spam rather than phishing, would you really want to hire iffy consultants? 😆

    (They might be trendy Apple-style "i-Tiffy Consultants" - whatever a "tiffy" is - but that's just asking for it, like being penisland.com or expertsexchange.com or whorepresents.com)

    #NamingThingsIsHard

  6. For those interested: That's from the AMD Geode LX Processor Data Book. In the version from February 2009 (with Publication ID 33234H, as visible in the original post), these show up on page 84.

    #namingThingsIsHard

  7. 🚀 "Naming things is hard," said every programmer ever, while busily counting imaginary unicorns named 'Index', 'Count', 'Offset', and 'Size'. 🦄 Apparently, the latest breakthrough in computer science is realizing that typos are bugs and not a new feature. 🤔 #RevolutionaryCodingInsights
    tigerbeetle.com/blog/2026-02-1 #NamingThingsIsHard #ProgrammingHumor #TyposAreBugs #ComputerScience #InsightsInCoding #HackerNews #ngated

  8. 🚀 "Naming things is hard," said every programmer ever, while busily counting imaginary unicorns named 'Index', 'Count', 'Offset', and 'Size'. 🦄 Apparently, the latest breakthrough in computer science is realizing that typos are bugs and not a new feature. 🤔 #RevolutionaryCodingInsights
    tigerbeetle.com/blog/2026-02-1 #NamingThingsIsHard #ProgrammingHumor #TyposAreBugs #ComputerScience #InsightsInCoding #HackerNews #ngated

  9. What's a shorter way to describe: "Outside humidity if it were at inside temperature"

    ---
    I have a helper sensor in HomeAssistant which calculates this, but #NamingThingsIsHard

  10. What's a shorter way to describe: "Outside humidity if it were at inside temperature"

    ---
    I have a helper sensor in HomeAssistant which calculates this, but #NamingThingsIsHard

  11. I picked up a cheap little second hand laptop today that I want to turn into my 'travel' laptop, after browsers have become unusable on the old one (which only had 2GB RAM).

    Now I have two hard choices:
    - What should it be called?
    - Which OS to install?

    #FreeBSD #OpenBSD #RunBSD #NamingThingsIsHard

  12. I picked up a cheap little second hand laptop today that I want to turn into my 'travel' laptop, after browsers have become unusable on the old one (which only had 2GB RAM).

    Now I have two hard choices:
    - What should it be called?
    - Which OS to install?

    #FreeBSD #OpenBSD #RunBSD #NamingThingsIsHard

  13. Meanwhile, Felix and I have entered the name brainstorming phase. One strong contender: Gurkie—inspired by "augurk" (Dutch for pickle). 🥒

    Felix says he needs to sleep on it (it was my idea, and he doesn't want to be influenced). Naming a plant is serious business, after all.

    #CucumberChronicles #NamePending #PlantParenthood #NamingThingsIsHard

  14. Meanwhile, Felix and I have entered the name brainstorming phase. One strong contender: Gurkie—inspired by "augurk" (Dutch for pickle). 🥒

    Felix says he needs to sleep on it (it was my idea, and he doesn't want to be influenced). Naming a plant is serious business, after all.

  15. There's resistance against using the same name in a namespace and a type inside that namespace. Why? What is the actual problem with this code? Is the 'foo::foo' looking too much like a constructor definition (in that context)? Isn't it great how the call to 'bar' has a clear relation to 'foo'?
    Why is it considered bad practice that shouldn't pass code review?

    #cpp #cplusplus #WG21 #cpp26 #namingThingsIsHard

  16. There's resistance against using the same name in a namespace and a type inside that namespace. Why? What is the actual problem with this code? Is the 'foo::foo' looking too much like a constructor definition (in that context)? Isn't it great how the call to 'bar' has a clear relation to 'foo'?
    Why is it considered bad practice that shouldn't pass code review?

    #cpp #cplusplus #WG21 #cpp26 #namingThingsIsHard

  17. There's resistance against using the same name in a namespace and a type inside that namespace. Why? What is the actual problem with this code? Is the 'foo::foo' looking too much like a constructor definition (in that context)? Isn't it great how the call to 'bar' has a clear relation to 'foo'?
    Why is it considered bad practice that shouldn't pass code review?

    #cpp #cplusplus #WG21 #cpp26 #namingThingsIsHard

  18. There's resistance against using the same name in a namespace and a type inside that namespace. Why? What is the actual problem with this code? Is the 'foo::foo' looking too much like a constructor definition (in that context)? Isn't it great how the call to 'bar' has a clear relation to 'foo'?
    Why is it considered bad practice that shouldn't pass code review?

    #cpp #cplusplus #WG21 #cpp26 #namingThingsIsHard

  19. There's resistance against using the same name in a namespace and a type inside that namespace. Why? What is the actual problem with this code? Is the 'foo::foo' looking too much like a constructor definition (in that context)? Isn't it great how the call to 'bar' has a clear relation to 'foo'?
    Why is it considered bad practice that shouldn't pass code review?

    #cpp #cplusplus #WG21 #cpp26 #namingThingsIsHard

  20. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  21. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  22. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  23. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  24. I'm working on a new project which will be using Protocol Buffers for messaging between two systems. One of the message operations will be a ping/pong heartbeat, so that the two systems can know that the other system is operational.

    In Protocol Buffers language, the ping message will be named PingRequest. What should the name of the pong message be?

    #ProtocolBuffers #NamingThingsIsHard

  25. It's true what they say, the hardest thing about programming is naming things. The same goes for coming up with names for games. Can't quite think of a name for my Descent-like game. Something will come to me but it is annoying lol
    #gamedev #namingThingsIsHard

  26. It's true what they say, the hardest thing about programming is naming things. The same goes for coming up with names for games. Can't quite think of a name for my Descent-like game. Something will come to me but it is annoying lol
    #gamedev #namingThingsIsHard

  27. HELP ME Fediverse :fediverse: ! 🥺 I need a name for an open source :opensource: project I'm working on. Please suggest anything in comments! I'm kinda stumped.

    It's a self-hosted AI-enhanced image search engine - see rough design sketches attached.

    ---------

    The Plan™:

    Basically it'll index all images in a given directory with 2 mechanisms:

    1. Exif / meta data + filepaths
    2. AI (currently CLIP) embeddings → vector DB

    ....then there'll be a web interface that lets you enter search terms & filter by various things like filename, exif fields, etc

    Quite early in development, but got the embedding worker done today!

    Aim is for it to run comfortably on a Raspberry Pi 4 that also has other things running on it.

    Still to do:

    - 🌐 Web interface
    - 🌄 Exif indexer
    - 🥔 Quantise CLIP etc for lower resource usage, go looking for better models
    - :opensource: Open source the code, but need a name for the project first!
    - 💭 Lotsa stuff I forget

    Tech:
    - 🟢 Node.js (pure JS libraries where possible)
    - 🍇 VectorDB: npmjs.com/package/hnsw (potential issue: this is in-memory or IndexedDB)
    - 🌄 Exif DB: npmjs.com/package/njodb ('cause I hate working with databases 'cause they're boring - sql ESP)
    - :python: Python worker 4 embedding/AI stuff: PyTorch, CLIP

    #AI #SelfHosting #OpenSource #NamingThings #IsHard #NamingThingsIsHard

  28. HELP ME Fediverse :fediverse: ! 🥺 I need a name for an open source :opensource: project I'm working on. Please suggest anything in comments! I'm kinda stumped.

    It's a self-hosted AI-enhanced image search engine - see rough design sketches attached.

    ---------

    The Plan™:

    Basically it'll index all images in a given directory with 2 mechanisms:

    1. Exif / meta data + filepaths
    2. AI (currently CLIP) embeddings → vector DB

    ....then there'll be a web interface that lets you enter search terms & filter by various things like filename, exif fields, etc

    Quite early in development, but got the embedding worker done today!

    Aim is for it to run comfortably on a Raspberry Pi 4 that also has other things running on it.

    Still to do:

    - 🌐 Web interface
    - 🌄 Exif indexer
    - 🥔 Quantise CLIP etc for lower resource usage, go looking for better models
    - :opensource: Open source the code, but need a name for the project first!
    - 💭 Lotsa stuff I forget

    Tech:
    - 🟢 Node.js (pure JS libraries where possible)
    - 🍇 VectorDB: npmjs.com/package/hnsw (potential issue: this is in-memory or IndexedDB)
    - 🌄 Exif DB: npmjs.com/package/njodb ('cause I hate working with databases 'cause they're boring - sql ESP)
    - :python: Python worker 4 embedding/AI stuff: PyTorch, CLIP

    #AI #SelfHosting #OpenSource #NamingThings #IsHard #NamingThingsIsHard

  29. HELP ME Fediverse :fediverse: ! 🥺 I need a name for an open source :opensource: project I'm working on. Please suggest anything in comments! I'm kinda stumped.

    It's a self-hosted AI-enhanced image search engine - see rough design sketches attached.

    ---------

    The Plan™:

    Basically it'll index all images in a given directory with 2 mechanisms:

    1. Exif / meta data + filepaths
    2. AI (currently CLIP) embeddings → vector DB

    ....then there'll be a web interface that lets you enter search terms & filter by various things like filename, exif fields, etc

    Quite early in development, but got the embedding worker done today!

    Aim is for it to run comfortably on a Raspberry Pi 4 that also has other things running on it.

    Still to do:

    - 🌐 Web interface
    - 🌄 Exif indexer
    - 🥔 Quantise CLIP etc for lower resource usage, go looking for better models
    - :opensource: Open source the code, but need a name for the project first!
    - 💭 Lotsa stuff I forget

    Tech:
    - 🟢 Node.js (pure JS libraries where possible)
    - 🍇 VectorDB: npmjs.com/package/hnsw (potential issue: this is in-memory or IndexedDB)
    - 🌄 Exif DB: npmjs.com/package/njodb ('cause I hate working with databases 'cause they're boring - sql ESP)
    - :python: Python worker 4 embedding/AI stuff: PyTorch, CLIP

    #AI #SelfHosting #OpenSource #NamingThings #IsHard #NamingThingsIsHard

  30. HELP ME Fediverse :fediverse: ! 🥺 I need a name for an open source :opensource: project I'm working on. Please suggest anything in comments! I'm kinda stumped.

    It's a self-hosted AI-enhanced image search engine - see rough design sketches attached.

    ---------

    The Plan™:

    Basically it'll index all images in a given directory with 2 mechanisms:

    1. Exif / meta data + filepaths
    2. AI (currently CLIP) embeddings → vector DB

    ....then there'll be a web interface that lets you enter search terms & filter by various things like filename, exif fields, etc

    Quite early in development, but got the embedding worker done today!

    Aim is for it to run comfortably on a Raspberry Pi 4 that also has other things running on it.

    Still to do:

    - 🌐 Web interface
    - 🌄 Exif indexer
    - 🥔 Quantise CLIP etc for lower resource usage, go looking for better models
    - :opensource: Open source the code, but need a name for the project first!
    - 💭 Lotsa stuff I forget

    Tech:
    - 🟢 Node.js (pure JS libraries where possible)
    - 🍇 VectorDB: npmjs.com/package/hnsw (potential issue: this is in-memory or IndexedDB)
    - 🌄 Exif DB: npmjs.com/package/njodb ('cause I hate working with databases 'cause they're boring - sql ESP)
    - :python: Python worker 4 embedding/AI stuff: PyTorch, CLIP

    #AI #SelfHosting #OpenSource #NamingThings #IsHard #NamingThingsIsHard

  31. Do not name things after:

    - The Vendor
    - The Language
    - The Datasystem
    - The Orchestration

    Instead, name them after:

    - The Process
    - The Outcome
    - The Audience
    - The Functionality

    #SRE #NamingThingsIsHard #BikeShedGames

  32. Do not name things after:

    - The Vendor
    - The Language
    - The Datasystem
    - The Orchestration

    Instead, name them after:

    - The Process
    - The Outcome
    - The Audience
    - The Functionality

    #SRE #NamingThingsIsHard #BikeShedGames

  33. 📗 "A Brief Book" - in which I explain the origins of the phrase and why I feel it fits perfectly for Approachable Open Source's mission.

    🗺 and 🧭

    approachableopensource.com/upd

    #opensource #book #namingthingsishard

  34. 📗 "A Brief Book" - in which I explain the origins of the phrase and why I feel it fits perfectly for Approachable Open Source's mission.

    🗺 and 🧭

    approachableopensource.com/upd

    #opensource #book #namingthingsishard

  35. I do love that buffer.subarray() returns a – checks notes – Buffer instance, not an array, in Node.js. 👀

    #namingThingsIsHard #NodeJS #Buffer #Array #dev

  36. I do love that buffer.subarray() returns a – checks notes – Buffer instance, not an array, in Node.js. 👀

    #namingThingsIsHard #NodeJS #Buffer #Array #dev

  37. Seems like at #fdroid we started to tackle a problem which I personally also encountered, but never found a good solution in my head: the distinction between F-Droid (the repository of FOSS apps) and F-Droid (the client for repositories of android apps). See gitlab.com/fdroid/admin/-/issu (thanks @uniqx for bringing it up)

    It basically the #NamingThingsIsHard problem, you always have in technology