this post was submitted on 09 Nov 2024
465 points (98.7% liked)
Science Memes
11148 readers
4870 users here now
Welcome to c/science_memes @ Mander.xyz!
A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.
Rules
- Don't throw mud. Behave like an intellectual and remember the human.
- Keep it rooted (on topic).
- No spam.
- Infographics welcome, get schooled.
This is a science community. We use the Dawkins definition of meme.
Research Committee
Other Mander Communities
Science and Research
Biology and Life Sciences
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- !reptiles and [email protected]
Physical Sciences
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Humanities and Social Sciences
Practical and Applied Sciences
- !exercise-and [email protected]
- [email protected]
- !self [email protected]
- [email protected]
- [email protected]
- [email protected]
Memes
Miscellaneous
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I am guilty of reinventing the wheel on almost every project. It brings immense control but doubles the workload. I do this because I have trust issues, but at least in the end I have "homemade everything"
I feel like doubling the workload is better than quadrupling the size of the project inheriting a bevy of features and tools you likely won't touch at all. Sure it's stripped out later (ideally), but I like less bloat and that includes during dev when I might have to dig through 3rd party code with its own conventions and standards packed into a 'source available' library with potentially dogshit or absent documentation.
Also yes, it's good practice
Unused code is stripped out by the compiler, but will your homemade library properly use all the fancy instruction set extensions for matrices? IIRC it's not as simple as just compiling for the correct microarch. But I could be wrong.