this post was submitted on 31 Jan 2024
1521 points (97.3% liked)

linuxmemes

21195 readers
283 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

    • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
    poopsmith
    zephyr
    rtxn
    1521
    Some inspiring quotes from our supreme leader (lemmy.dbzer0.com)
    submitted 9 months ago by [email protected] to c/linuxmemes
    210 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] [email protected] 4 points 9 months ago (1 children)

    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.

    [–] [email protected] 3 points 9 months ago* (last edited 9 months ago)

    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.