this post was submitted on 31 Jan 2024
1516 points (97.3% liked)
linuxmemes
20909 readers
1997 users here now
I use Arch btw
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules
- Follow the site-wide rules and code of conduct
- Be civil
- Post Linux-related content
- No recent reposts
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Aha... so that's why my wife says "why you gotta always complicate things" π.
Not regarding coding in particular, I'm an electronics and telecommunications engineer, I do code a little though (here and there π), but regarding every day things, like maybe make something that will ease my life, yeah sure, I do that. But it has to be something I use frequently enough, otherwise, no I don't see the point in spending the time and the energy to actually do it.
Different disciplines - different thresholds. But yeah, thatβs exactly it.
With software engineering, the unknown space is vast, yet the tools are great. So itβs very easy to start tinkering and get lost in the process.
Yeah, I know what you mean. A colleague of mine in uni that studied software engineering had this take on it: "I don't have to invest anything but time in what I'm doing, so making mistakes or doing something for the heck of it is justified. On the other hand you (me) invest not only time, but also money in a project that might come out to be not really practical to be used in the real world."
He has a point to be honest. Plus, with real hardware projects it's not like you can get "lost" in the design process and be like "u, I can do this, and add this, and maybe this" cuz that costs extra money and time, plus a schematic and PCB redesign, etc. So, yeah, I do agree that it's easier to tinker and get lost in code.