#notinventedhere — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #notinventedhere, aggregated by home.social.
-
I #vibecoded in 2h a simple #app to manage shared expenses for trips with friends. When I was showing it, the obvious question came up:
“But surely there’s already an app for this, no?” 🤔
And the answer is: yes, I’m 100% sure there are many. 🤷♂️
BUT… finding them, comparing them, testing them, creating an account, discovering the free version is too limited, realizing they don’t work exactly the way you want, getting annoyed, trying another one… 🥱🥱🥱 can easily take more time than building the perfect tiny solution for your own use case.
I accept this is a new variant of the #NotInventedHere syndrome. Except that this time, for a not-so-small category of simple but useful apps, it actually makes sense.
Not because we should rebuild everything. But because sometimes the fastest path is not searching for the right tool. It is creating the small tool you need.
The app itself is very simple: basically a web wrapper on top of an Excel file.
-
I #vibecoded in 2h a simple #app to manage shared expenses for trips with friends. When I was showing it, the obvious question came up:
“But surely there’s already an app for this, no?” 🤔
And the answer is: yes, I’m 100% sure there are many. 🤷♂️
BUT… finding them, comparing them, testing them, creating an account, discovering the free version is too limited, realizing they don’t work exactly the way you want, getting annoyed, trying another one… 🥱🥱🥱 can easily take more time than building the perfect tiny solution for your own use case.
I accept this is a new variant of the #NotInventedHere syndrome. Except that this time, for a not-so-small category of simple but useful apps, it actually makes sense.
Not because we should rebuild everything. But because sometimes the fastest path is not searching for the right tool. It is creating the small tool you need.
The app itself is very simple: basically a web wrapper on top of an Excel file.
-
I #vibecoded in 2h a simple #app to manage shared expenses for trips with friends. When I was showing it, the obvious question came up:
“But surely there’s already an app for this, no?” 🤔
And the answer is: yes, I’m 100% sure there are many. 🤷♂️
BUT… finding them, comparing them, testing them, creating an account, discovering the free version is too limited, realizing they don’t work exactly the way you want, getting annoyed, trying another one… 🥱🥱🥱 can easily take more time than building the perfect tiny solution for your own use case.
I accept this is a new variant of the #NotInventedHere syndrome. Except that this time, for a not-so-small category of simple but useful apps, it actually makes sense.
Not because we should rebuild everything. But because sometimes the fastest path is not searching for the right tool. It is creating the small tool you need.
The app itself is very simple: basically a web wrapper on top of an Excel file.
-
I #vibecoded in 2h a simple #app to manage shared expenses for trips with friends. When I was showing it, the obvious question came up:
“But surely there’s already an app for this, no?” 🤔
And the answer is: yes, I’m 100% sure there are many. 🤷♂️
BUT… finding them, comparing them, testing them, creating an account, discovering the free version is too limited, realizing they don’t work exactly the way you want, getting annoyed, trying another one… 🥱🥱🥱 can easily take more time than building the perfect tiny solution for your own use case.
I accept this is a new variant of the #NotInventedHere syndrome. Except that this time, for a not-so-small category of simple but useful apps, it actually makes sense.
Not because we should rebuild everything. But because sometimes the fastest path is not searching for the right tool. It is creating the small tool you need.
The app itself is very simple: basically a web wrapper on top of an Excel file.
-
I #vibecoded in 2h a simple #app to manage shared expenses for trips with friends. When I was showing it, the obvious question came up:
“But surely there’s already an app for this, no?” 🤔
And the answer is: yes, I’m 100% sure there are many. 🤷♂️
BUT… finding them, comparing them, testing them, creating an account, discovering the free version is too limited, realizing they don’t work exactly the way you want, getting annoyed, trying another one… 🥱🥱🥱 can easily take more time than building the perfect tiny solution for your own use case.
I accept this is a new variant of the #NotInventedHere syndrome. Except that this time, for a not-so-small category of simple but useful apps, it actually makes sense.
Not because we should rebuild everything. But because sometimes the fastest path is not searching for the right tool. It is creating the small tool you need.
The app itself is very simple: basically a web wrapper on top of an Excel file.
-
What's that? #ubuntusnaps are badly designed for desktop usage? Who knew?
Scroll my feed whydontcha.
#Flatpak, #AppImage, take your pick. Much better integration and uses standard #SELinux - instead of having to suffer #Canonical and their #NotInventedHere syndrome with #AppArmor.
Microsoft's VS Code in Ubuntu's Snap Format Eats Up Disk Space Like Bloatware Even After Removal
https://itsfoss.com/news/vscode-snap-disk-space-issue/ -
What's that? #ubuntusnaps are badly designed for desktop usage? Who knew?
Scroll my feed whydontcha.
#Flatpak, #AppImage, take your pick. Much better integration and uses standard #SELinux - instead of having to suffer #Canonical and their #NotInventedHere syndrome with #AppArmor.
Microsoft's VS Code in Ubuntu's Snap Format Eats Up Disk Space Like Bloatware Even After Removal
https://itsfoss.com/news/vscode-snap-disk-space-issue/ -
What's that? #ubuntusnaps are badly designed for desktop usage? Who knew?
Scroll my feed whydontcha.
#Flatpak, #AppImage, take your pick. Much better integration and uses standard #SELinux - instead of having to suffer #Canonical and their #NotInventedHere syndrome with #AppArmor.
Microsoft's VS Code in Ubuntu's Snap Format Eats Up Disk Space Like Bloatware Even After Removal
https://itsfoss.com/news/vscode-snap-disk-space-issue/ -
What's that? #ubuntusnaps are badly designed for desktop usage? Who knew?
Scroll my feed whydontcha.
#Flatpak, #AppImage, take your pick. Much better integration and uses standard #SELinux - instead of having to suffer #Canonical and their #NotInventedHere syndrome with #AppArmor.
Microsoft's VS Code in Ubuntu's Snap Format Eats Up Disk Space Like Bloatware Even After Removal
https://itsfoss.com/news/vscode-snap-disk-space-issue/ -
What's that? #ubuntusnaps are badly designed for desktop usage? Who knew?
Scroll my feed whydontcha.
#Flatpak, #AppImage, take your pick. Much better integration and uses standard #SELinux - instead of having to suffer #Canonical and their #NotInventedHere syndrome with #AppArmor.
Microsoft's VS Code in Ubuntu's Snap Format Eats Up Disk Space Like Bloatware Even After Removal
https://itsfoss.com/news/vscode-snap-disk-space-issue/ -
Build what you need?
I do not wholly subscribe to the mantra of “build what you need”. To an extent, yes, make the thing you want. Only, stop doing that as soon as someone invents a less square wheel than yours. Use their wheel instead.
#buidWhatYouNeed #code #dev #ethicalHacking #IndieWeb #notInventedHere #reinventTheSquareWheel
-
Build what you need?
I do not wholly subscribe to the mantra of “build what you need”. To an extent, yes, make the thing you want. Only, stop doing that as soon as someone invents a less square wheel than yours. Use their wheel instead.
See also: Make what you need might be all wrong for the IndieWeb’s future
#buidWhatYouNeed #code #dev #ethicalHacking #IndieWeb #notInventedHere #reinventTheSquareWheel
-
Build what you need?
I do not wholly subscribe to the mantra of “build what you need”. To an extent, yes, make the thing you want. Only, stop doing that as soon as someone invents a less square wheel than yours. Use their wheel instead.
See also: Make what you need might be all wrong for the IndieWeb’s future
#buidWhatYouNeed #code #dev #ethicalHacking #IndieWeb #notInventedHere #reinventTheSquareWheel
-
Build what you need?
I do not wholly subscribe to the mantra of “build what you need”. To an extent, yes, make the thing you want. Only, stop doing that as soon as someone invents a less square wheel than yours. Use their wheel instead.
See also: Make what you need might be all wrong for the IndieWeb’s future
#buidWhatYouNeed #code #dev #ethicalHacking #IndieWeb #notInventedHere #reinventTheSquareWheel
-
Build what you need?
I do not wholly subscribe to the mantra of “build what you need”. To an extent, yes, make the thing you want. Only, stop doing that as soon as someone invents a less square wheel than yours. Use their wheel instead.
#buidWhatYouNeed #code #dev #ethicalHacking #IndieWeb #notInventedHere #reinventTheSquareWheel
-
I'm guessing that Bell Labs was the only place totally immune to Not Invented Here Syndrome, because everything really was invented there. [1]
Thoughts?
[1] To a first approximation, anyway.
-
I'm guessing that Bell Labs was the only place totally immune to Not Invented Here Syndrome, because everything really was invented there. [1]
Thoughts?
[1] To a first approximation, anyway.
-
I'm guessing that Bell Labs was the only place totally immune to Not Invented Here Syndrome, because everything really was invented there. [1]
Thoughts?
[1] To a first approximation, anyway.
-
I'm guessing that Bell Labs was the only place totally immune to Not Invented Here Syndrome, because everything really was invented there. [1]
Thoughts?
[1] To a first approximation, anyway.
-
I'm guessing that Bell Labs was the only place totally immune to Not Invented Here Syndrome, because everything really was invented there. [1]
Thoughts?
[1] To a first approximation, anyway.
-
My biggest #WWDC25 thing is about #JPEGXL. Will #Apple continue with it, since #Google has been extraordinarily #NotInventedHere in trying to kill it in the wild and in open source? Or will Apple be Apple (of old) and keep using it because it's damn good, because Apple controls its own hardware, and because it's the right thing to do?
If Apple bails on JPEGXL it'll make me far more worried than will any other single thing.
-
My biggest #WWDC25 thing is about #JPEGXL. Will #Apple continue with it, since #Google has been extraordinarily #NotInventedHere in trying to kill it in the wild and in open source? Or will Apple be Apple (of old) and keep using it because it's damn good, because Apple controls its own hardware, and because it's the right thing to do?
If Apple bails on JPEGXL it'll make me far more worried than will any other single thing.
-
My biggest #WWDC25 thing is about #JPEGXL. Will #Apple continue with it, since #Google has been extraordinarily #NotInventedHere in trying to kill it in the wild and in open source? Or will Apple be Apple (of old) and keep using it because it's damn good, because Apple controls its own hardware, and because it's the right thing to do?
If Apple bails on JPEGXL it'll make me far more worried than will any other single thing.
-
My biggest #WWDC25 thing is about #JPEGXL. Will #Apple continue with it, since #Google has been extraordinarily #NotInventedHere in trying to kill it in the wild and in open source? Or will Apple be Apple (of old) and keep using it because it's damn good, because Apple controls its own hardware, and because it's the right thing to do?
If Apple bails on JPEGXL it'll make me far more worried than will any other single thing.
-
My biggest #WWDC25 thing is about #JPEGXL. Will #Apple continue with it, since #Google has been extraordinarily #NotInventedHere in trying to kill it in the wild and in open source? Or will Apple be Apple (of old) and keep using it because it's damn good, because Apple controls its own hardware, and because it's the right thing to do?
If Apple bails on JPEGXL it'll make me far more worried than will any other single thing.
-
Analog zum #notInventedHere Problem haben wir auch ein #notLearndHere Problem. Ichs vermute dass es sogar ein #notLearnedByMyselfPersonallyYet Problem ist.
Und dabei hoffe ich darauf, dass individuelles lernen bei Herausforderungen funktioniert, die abstrakter sind als eine heiße Herdplatte.
From: @sixtus
https://mastodon.social/@sixtus/114159531684531051 -
Analog zum #notInventedHere Problem haben wir auch ein #notLearndHere Problem. Ichs vermute dass es sogar ein #notLearnedByMyselfPersonallyYet Problem ist.
Und dabei hoffe ich darauf, dass individuelles lernen bei Herausforderungen funktioniert, die abstrakter sind als eine heiße Herdplatte.
From: @sixtus
https://mastodon.social/@sixtus/114159531684531051 -
Analog zum #notInventedHere Problem haben wir auch ein #notLearndHere Problem. Ichs vermute dass es sogar ein #notLearnedByMyselfPersonallyYet Problem ist.
Und dabei hoffe ich darauf, dass individuelles lernen bei Herausforderungen funktioniert, die abstrakter sind als eine heiße Herdplatte.
From: @sixtus
https://mastodon.social/@sixtus/114159531684531051 -
Analog zum #notInventedHere Problem haben wir auch ein #notLearndHere Problem. Ichs vermute dass es sogar ein #notLearnedByMyselfPersonallyYet Problem ist.
Und dabei hoffe ich darauf, dass individuelles lernen bei Herausforderungen funktioniert, die abstrakter sind als eine heiße Herdplatte.
From: @sixtus
https://mastodon.social/@sixtus/114159531684531051 -
Not Invented Here syndrome.
Microsoft was not "into" standards. They wanted to own and control the tech they used; if they had to use something developed by others, they used their infamous "embrace, extend, extinguish" technique.
They didn't really start getting interested in using standards until much later.
-
Not Invented Here syndrome.
Microsoft was not "into" standards. They wanted to own and control the tech they used; if they had to use something developed by others, they used their infamous "embrace, extend, extinguish" technique.
They didn't really start getting interested in using standards until much later.
-
Not Invented Here syndrome.
Microsoft was not "into" standards. They wanted to own and control the tech they used; if they had to use something developed by others, they used their infamous "embrace, extend, extinguish" technique.
They didn't really start getting interested in using standards until much later.
-
Not Invented Here syndrome.
Microsoft was not "into" standards. They wanted to own and control the tech they used; if they had to use something developed by others, they used their infamous "embrace, extend, extinguish" technique.
They didn't really start getting interested in using standards until much later.
-
Not Invented Here syndrome.
Microsoft was not "into" standards. They wanted to own and control the tech they used; if they had to use something developed by others, they used their infamous "embrace, extend, extinguish" technique.
They didn't really start getting interested in using standards until much later.
-
@pebo @isAutonomous
Klassischer Fall von #NotInventedHere-Syndrom vielleicht? -
@pebo @isAutonomous
Klassischer Fall von #NotInventedHere-Syndrom vielleicht? -
@pebo @isAutonomous
Klassischer Fall von #NotInventedHere-Syndrom vielleicht? -
@pebo @isAutonomous
Klassischer Fall von #NotInventedHere-Syndrom vielleicht? -
@pebo @isAutonomous
Klassischer Fall von #NotInventedHere-Syndrom vielleicht? -
If you've been following me for a while you know that:
1) I'm a loud advocate of good UX above everything else.
2) I'm not a fan of the "design systems".Why (2)? Because largely I believe it failed to deliver (1). From my experience Design Systems are an awesome drop-in solution for 99% of *anyone's* cases if and only if:
a) You take the design system as-is and are willing to bend your design choices so it does not violate said design system.
b) You don't develop your own design system (this would directly violate (a)).
c) Everyone in the team understands the interactions and intentions of every piece perfectly.Sadly pretty much every company violates any or all of the above.
-
If you've been following me for a while you know that:
1) I'm a loud advocate of good UX above everything else.
2) I'm not a fan of the "design systems".Why (2)? Because largely I believe it failed to deliver (1). From my experience Design Systems are an awesome drop-in solution for 99% of *anyone's* cases if and only if:
a) You take the design system as-is and are willing to bend your design choices so it does not violate said design system.
b) You don't develop your own design system (this would directly violate (a)).
c) Everyone in the team understands the interactions and intentions of every piece perfectly.Sadly pretty much every company violates any or all of the above.
-
If you've been following me for a while you know that:
1) I'm a loud advocate of good UX above everything else.
2) I'm not a fan of the "design systems".Why (2)? Because largely I believe it failed to deliver (1). From my experience Design Systems are an awesome drop-in solution for 99% of *anyone's* cases if and only if:
a) You take the design system as-is and are willing to bend your design choices so it does not violate said design system.
b) You don't develop your own design system (this would directly violate (a)).
c) Everyone in the team understands the interactions and intentions of every piece perfectly.Sadly pretty much every company violates any or all of the above.
-
If you've been following me for a while you know that:
1) I'm a loud advocate of good UX above everything else.
2) I'm not a fan of the "design systems".Why (2)? Because largely I believe it failed to deliver (1). From my experience Design Systems are an awesome drop-in solution for 99% of *anyone's* cases if and only if:
a) You take the design system as-is and are willing to bend your design choices so it does not violate said design system.
b) You don't develop your own design system (this would directly violate (a)).
c) Everyone in the team understands the interactions and intentions of every piece perfectly.Sadly pretty much every company violates any or all of the above.
-
Ok, say it with me:
"We don't need to come up with new solutions. The answer is already in the documentation. We just need to read."
#notInventedHere is bad for consistency, training, onboarding, and support. Please read the RFC.
-
Ok, say it with me:
"We don't need to come up with new solutions. The answer is already in the documentation. We just need to read."
#notInventedHere is bad for consistency, training, onboarding, and support. Please read the RFC.
-
Ok, say it with me:
"We don't need to come up with new solutions. The answer is already in the documentation. We just need to read."
#notInventedHere is bad for consistency, training, onboarding, and support. Please read the RFC.
-
Ok, say it with me:
"We don't need to come up with new solutions. The answer is already in the documentation. We just need to read."
#notInventedHere is bad for consistency, training, onboarding, and support. Please read the RFC.
-
#NotInventedHere is rerunning old cartoons on startup life, and I had to share this one… https://notinventedhe.re/on/2011-10-26 #OpenSource
-
#NotInventedHere is rerunning old cartoons on startup life, and I had to share this one… https://notinventedhe.re/on/2011-10-26 #OpenSource
-
#NotInventedHere is rerunning old cartoons on startup life, and I had to share this one… https://notinventedhe.re/on/2011-10-26 #OpenSource