I’m not complaining, but I didn’t realize how much work it was. It makes me really respect the people who do it on a regular basis.

For example:

  • You know how to use your software, but other people don’t. So you need to write documentation.
  • You can just modify the source files, but it’s impractical for everyone to do that. So you need to add a config file.
  • You can just drag the output files into place, but that’s impractical for everyone to do. So you need to package it.
  • You trust yourself, but distro maintainers rightfully don’t. So you need to package your source code and configure the package to compile it.
  • You will abide by your idea of how the software should be used, but other people might not. So you need to pick a license.

Sometimes I think there must be an easier way, but I can’t think of any. I guess it probably gets easier with experience.

2 points
*
Deleted by creator
permalink
report
reply
6 points

Yeah, when I released the alpha of my first open source app, boy I had a lot of work to do when I started getting feedback

permalink
report
reply
56 points
*

That’s why engineers are, on average, paid more than researchers… And why research is such a nicer job.

Create robust and easy-to-use stuff is tough and you don’t get much reward

permalink
report
reply
20 points
*

But if anything goes wrong or doesn’t work right, suddenly the users remember who deserves recognition

permalink
report
parent
reply
13 points

Not really, they’ll complain, open an incident and tell engineers they “are amateur, my grandmother could do better”

permalink
report
parent
reply
2 points

Well said!

permalink
report
parent
reply
2 points
*

I’ve been attempting to build systems to make this “robustness” redundant across all my works, but I always feel there’s something more that I missed. I can’t tell if this task is simply never-ending or I just lack the knowledge of covering all the dots from the get-go or both.

permalink
report
parent
reply
1 point

Those are signs of an ever evolving/improving mind! You continue to perfect your craft and as such your older self is less efficient, perfect and organised.

permalink
report
parent
reply
30 points

This is basically the problem with “suckless” software summed up.

permalink
report
reply
10 points

Terrible name too

permalink
report
parent
reply
9 points

Brb, putting “suckfull software developer - 12 years” on my resume.

permalink
report
parent
reply
9 points

I’m not sure I’d call it a problem. In the end it’s the developers’ choice.

Btw, I think this applies in general to opinionated software. Suckless is just a subset of that.

permalink
report
parent
reply
28 points

Documentation is very useful today (to clarify our thoughts on what is useful and what is not, what is in scope and what is not), and for our future selves.

Writing small bits of software made me appreciative of the work teams put on large pieces of infrastructure!

permalink
report
reply
7 points

Hard agree on helping out your future self. I routinely drop a commands.md file in every project now, and dump any commands in there for creating the dev environment, the build step, any thoughts that might help when I come back in five years.

permalink
report
parent
reply

Open Source

!opensource@lemmy.ml

Create post

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

  • Posts must be relevant to the open source ideology
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

Community stats

  • 3.9K

    Monthly active users

  • 1.8K

    Posts

  • 30K

    Comments