#namingishard — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #namingishard, aggregated by home.social.
-
Breathe in....breathe out...
Repeat: "I am not snarking at people today. I am not snarking."
"I am especially not snarking at the poster who says the 'United States of America' isn't a 'real' name, and we shouldn't be allowed to use 'American' as our demonym...
Even though he comes from the 'United Kingdom' but calls himself 'British',
despite his country only making up about three quarters of the British Isles.
I will NOT snark at him. I will NOT."
-
Breathe in....breathe out...
Repeat: "I am not snarking at people today. I am not snarking."
"I am especially not snarking at the poster who says the 'United States of America' isn't a 'real' name, and we shouldn't be allowed to use 'American' as our demonym...
Even though he comes from the 'United Kingdom' but calls himself 'British',
despite his country only making up about three quarters of the British Isles.
I will NOT snark at him. I will NOT."
-
Breathe in....breathe out...
Repeat: "I am not snarking at people today. I am not snarking."
"I am especially not snarking at the poster who says the 'United States of America' isn't a 'real' name, and we shouldn't be allowed to use 'American' as our demonym...
Even though he comes from the 'United Kingdom' but calls himself 'British',
despite his country only making up about three quarters of the British Isles.
I will NOT snark at him. I will NOT."
-
Breathe in....breathe out...
Repeat: "I am not snarking at people today. I am not snarking."
"I am especially not snarking at the poster who says the 'United States of America' isn't a 'real' name, and we shouldn't be allowed to use 'American' as our demonym...
Even though he comes from the 'United Kingdom' but calls himself 'British',
despite his country only making up about three quarters of the British Isles.
I will NOT snark at him. I will NOT."
-
Breathe in....breathe out...
Repeat: "I am not snarking at people today. I am not snarking."
"I am especially not snarking at the poster who says the 'United States of America' isn't a 'real' name, and we shouldn't be allowed to use 'American' as our demonym...
Even though he comes from the 'United Kingdom' but calls himself 'British',
despite his country only making up about three quarters of the British Isles.
I will NOT snark at him. I will NOT."
-
I was again reminded how bluntly excluding everything IT is being built. I wanted to use the phrase "put me in CC of that email". But:
- Does an average person know what it means?
- Or even how to do it in their app?
- What if the field in their app has a different name? -
I was again reminded how bluntly excluding everything IT is being built. I wanted to use the phrase "put me in CC of that email". But:
- Does an average person know what it means?
- Or even how to do it in their app?
- What if the field in their app has a different name? -
I was again reminded how bluntly excluding everything IT is being built. I wanted to use the phrase "put me in CC of that email". But:
- Does an average person know what it means?
- Or even how to do it in their app?
- What if the field in their app has a different name? -
I was again reminded how bluntly excluding everything IT is being built. I wanted to use the phrase "put me in CC of that email". But:
- Does an average person know what it means?
- Or even how to do it in their app?
- What if the field in their app has a different name? -
I was again reminded how bluntly excluding everything IT is being built. I wanted to use the phrase "put me in CC of that email". But:
- Does an average person know what it means?
- Or even how to do it in their app?
- What if the field in their app has a different name? -
Little IT naming protip:
🙅♂️ Do not use relative project version names like "next", "tng", "legacy", "old". It _will_ eventually confuse people as newcomers won't know if "`old` was before `next`, but that was also before `classic`". It _will_ eventually lose meaning as you release `next-next` and `next-next-next`.
👍 Do use absolute project version names. 1, 2, 3, ... At best irrespective to what new-ism marketing department came with. They want project rebrand? Fine, but we're now on Foo-4.3. So the next one will be Bar-5.0. -
Little IT naming protip:
🙅♂️ Do not use relative project version names like "next", "tng", "legacy", "old". It _will_ eventually confuse people as newcomers won't know if "`old` was before `next`, but that was also before `classic`". It _will_ eventually lose meaning as you release `next-next` and `next-next-next`.
👍 Do use absolute project version names. 1, 2, 3, ... At best irrespective to what new-ism marketing department came with. They want project rebrand? Fine, but we're now on Foo-4.3. So the next one will be Bar-5.0. -
Little IT naming protip:
🙅♂️ Do not use relative project version names like "next", "tng", "legacy", "old". It _will_ eventually confuse people as newcomers won't know if "`old` was before `next`, but that was also before `classic`". It _will_ eventually lose meaning as you release `next-next` and `next-next-next`.
👍 Do use absolute project version names. 1, 2, 3, ... At best irrespective to what new-ism marketing department came with. They want project rebrand? Fine, but we're now on Foo-4.3. So the next one will be Bar-5.0. -
Little IT naming protip:
🙅♂️ Do not use relative project version names like "next", "tng", "legacy", "old". It _will_ eventually confuse people as newcomers won't know if "`old` was before `next`, but that was also before `classic`". It _will_ eventually lose meaning as you release `next-next` and `next-next-next`.
👍 Do use absolute project version names. 1, 2, 3, ... At best irrespective to what new-ism marketing department came with. They want project rebrand? Fine, but we're now on Foo-4.3. So the next one will be Bar-5.0. -
So if this is called a "backspace", shouldn't this be called "forwardspace"?
-
So if this is called a "backspace", shouldn't this be called "forwardspace"?
-
So if this is called a "backspace", shouldn't this be called "forwardspace"?
-
So if this is called a "backspace", shouldn't this be called "forwardspace"?
-
So if this is called a "backspace", shouldn't this be called "forwardspace"?
-
I have a "src" folder for my own source code, or code I've contributed to, but do you have a separate folder for source code from other people? I.e. code you've downloaded just because there are no available binary packages? If so, what do you call it?
-
I have a "src" folder for my own source code, or code I've contributed to, but do you have a separate folder for source code from other people? I.e. code you've downloaded just because there are no available binary packages? If so, what do you call it?
-
I have a "src" folder for my own source code, or code I've contributed to, but do you have a separate folder for source code from other people? I.e. code you've downloaded just because there are no available binary packages? If so, what do you call it?
-
I have a "src" folder for my own source code, or code I've contributed to, but do you have a separate folder for source code from other people? I.e. code you've downloaded just because there are no available binary packages? If so, what do you call it?
-
I have a "src" folder for my own source code, or code I've contributed to, but do you have a separate folder for source code from other people? I.e. code you've downloaded just because there are no available binary packages? If so, what do you call it?
-
It's a good day when you get to crack out the whiteboard and starting figuring out a code structure.
-
It's a good day when you get to crack out the whiteboard and starting figuring out a code structure.
-
It's a good day when you get to crack out the whiteboard and starting figuring out a code structure.
-
It's a good day when you get to crack out the whiteboard and starting figuring out a code structure.
-
It's a good day when you get to crack out the whiteboard and starting figuring out a code structure.
-
-
-
-
-
-
@postmodern I think it should try to parse it and raise a dedicated/wrapping exception if that didn't work. So, wrapping any parsing error in a PresumablyIncorrectResponseMimeTypeExceptionWrapperExceptionError or so. #NamingIsHard
-
@postmodern I think it should try to parse it and raise a dedicated/wrapping exception if that didn't work. So, wrapping any parsing error in a PresumablyIncorrectResponseMimeTypeExceptionWrapperExceptionError or so. #NamingIsHard
-
@postmodern I think it should try to parse it and raise a dedicated/wrapping exception if that didn't work. So, wrapping any parsing error in a PresumablyIncorrectResponseMimeTypeExceptionWrapperExceptionError or so. #NamingIsHard
-
@postmodern I think it should try to parse it and raise a dedicated/wrapping exception if that didn't work. So, wrapping any parsing error in a PresumablyIncorrectResponseMimeTypeExceptionWrapperExceptionError or so. #NamingIsHard
-
Oh Frege’s puzzles! #SwiftUI is full of those. And many other frameworks, for that matter.
https://christiantietze.de/posts/2023/08/swiftui-view-is-your-viewmodel/ -
Oh Frege’s puzzles! #SwiftUI is full of those. And many other frameworks, for that matter.
https://christiantietze.de/posts/2023/08/swiftui-view-is-your-viewmodel/ -
Oh Frege’s puzzles! #SwiftUI is full of those. And many other frameworks, for that matter.
https://christiantietze.de/posts/2023/08/swiftui-view-is-your-viewmodel/ -
Oh Frege’s puzzles! #SwiftUI is full of those. And many other frameworks, for that matter.
https://christiantietze.de/posts/2023/08/swiftui-view-is-your-viewmodel/ -
In Go, a package is a directory of Go files, and a module is a collection of packages.
To me, things would have been clearer if it were the other way around:
You'd package a bunch of modules together. -
In Go, a package is a directory of Go files, and a module is a collection of packages.
To me, things would have been clearer if it were the other way around:
You'd package a bunch of modules together. -
In Go, a package is a directory of Go files, and a module is a collection of packages.
To me, things would have been clearer if it were the other way around:
You'd package a bunch of modules together. -
I just published a post: The Case for Variables
https://mikemai.net/blog/2023/06/23/the-case-for-variables.html
-
I just published a post: The Case for Variables
https://mikemai.net/blog/2023/06/23/the-case-for-variables.html
-
I just published a post: The Case for Variables
https://mikemai.net/blog/2023/06/23/the-case-for-variables.html
-
I just published a post: The Case for Variables
https://mikemai.net/blog/2023/06/23/the-case-for-variables.html
-
I just published a post: The Case for Variables
https://mikemai.net/blog/2023/06/23/the-case-for-variables.html
-
Naming is hard, isn't it? https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ - still relevant and so true #namingishard
-
Naming is hard, isn't it? https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ - still relevant and so true #namingishard
-
Naming is hard, isn't it? https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ - still relevant and so true #namingishard
-
Am I upset that I spent the day push a wet noodle up the wrong hill? Sorta. But I did learn a lot about how the previous IT guy set things up, and where (I think he was headed).
Hopefully the newly gained understanding / knowledge will still be in my head come Monday. 2/2
-
Am I upset that I spent the day push a wet noodle up the wrong hill? Sorta. But I did learn a lot about how the previous IT guy set things up, and where (I think he was headed).
Hopefully the newly gained understanding / knowledge will still be in my head come Monday. 2/2
