this post was submitted on 31 Jan 2024
1521 points (97.3% liked)
linuxmemes
21194 readers
332 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
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
sudoin 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
You could make the memes manually, or like a true programmer spend several hours if not days making a script that make them for you.
Yeah, I've seen the type... had a colleague in uni like that. And it's not like he's gonna need it for something else, but why spend an hour making them when he could spend 5 hours making the script to generate them in 1 second.
If this is how true programmers think, I'm sorry, I'm not a true programmer then π€·.
I meant it as a joke, but the way I see it is as a "fast" and fun exercise where their's no pressure and the only judge is yourself. It's more about coding something for the fun of it.
I understand the logic, but this really seems like a complete waste of time. I'd rather spend that time coding something really useful than coding that.
It's not a waste of time if you enjoyed making it. See it as like reading a book or watching a show.
When you have to do something once, do it manually, when you need to do it more often, script/code it.
Oh, and coding is much more fun then manual labour.
Depends for who... I also enjoy welding and woodworking. It's not always about the end product, it's about the journey.
And 12 times is not that much. I mean, it's not like I'm gonna make another one next year.
Thatβs how engineers think in their free time.
When the specific goal is something I can do manually, and itβs not pressing, I would rather spend time learning how to make a tool to do it. I might not need the tool ever, I do use the knowledge picked up on those forays every day.
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.
I've been guilty of this... I justify it in my head by saying:
That is true though, I agree. If I do see it as practice, then yes, I would do it regardless.