Comment

I am guilty of reinvenring 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”

source

Sort:hotnew top

MrPoopyButthole@lemmy.world ⁨1⁩ ⁨month⁩ ago
It’s practice and it makes you better!

source
- marcos@lemmy.world ⁨5⁩ ⁨weeks⁩ ago
  As long as you don’t insist on using them even after it became clear that the off the shelf version is better in ever way and you’ll never have enough time to reach its quality level.
  
  source
  - Hadriscus@lemm.ee ⁨5⁩ ⁨weeks⁩ ago
    pretty much 😂
    
    source
- Hadriscus@lemm.ee ⁨5⁩ ⁨weeks⁩ ago
  it does !!
  
  source
brbposting@sh.itjust.works ⁨5⁩ ⁨weeks⁩ ago
I’d be curious to hear of a time when it paid off and one when it didn’t it. And about the kind of stuff you do.

I’m rather preparing to reinvent the wheel a little bit, as a technical person albeit one who does not code.

source
Sinuousity@lemmy.world ⁨1⁩ ⁨month⁩ ago
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

source
- boonhet@lemm.ee ⁨5⁩ ⁨weeks⁩ ago
  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.
  
  source