Software principles

What do you think software should have?


Software has some requirements for me to use it.

This is to discuss as a community what software - including web applications should consider.

投票 (可选) (别通知) (可选)


我同意你关于尝试一些事情并看看什么是有效的。 WordPress 就是一个很好的例子。我认为 wordpress 是非常好的软件,但很多缺乏经验的开发人员认为它很糟糕。但是这些开发人员在他们的生活中并没有做出任何重要的事情。


有些开发人员认为 Haskell 和 Clojure 是游戏规则的改变者,但随后他们产生了难以理解的丑陋混乱,除了他们的作者之外没有人能理解,这不是因为他们的代码很漂亮或其他人没有经验。

In my experience when someone says something is clean or beautiful I have disagreed. I think one man's beauty is another man's garbage 🤣

I agree with you with regard to trying things out and seeing what works. WordPress is a good example of that. I think wordpress is very good software but a lot of subpar inexperienced developers think it's bad. But those developers haven't made anything significant in their lives.

I lean on the tool making and practical realm of software development.

Theres developers who think Haskell and Clojure are game changers but then they produce unreadable ugly messes that nobody but their author can understand and it's not because their code is beautiful or that others are inexperienced.

    : Mindey
    :  -- 
    :  -- 





  • 作为研究
  • 作为艺术
  • 作为探索
  • 作为工具制作
  • 作为工艺
  • 作为工程 ...

There's entire philosophy for how good quality software should be written from typing, structuring, logging, building, releasing, dividing into and combining from services... however, all that depends on particular choices of formats and standards and short-medium-long term goals.

For example, not everyone has to stick to stringent engineering requirements in the research phase -- it's easier to rapidly build a half-baked rocket and try again, than to meticulously design a masterpiece, that lacks a key ability (e.g., ability to come back to land).

And so, wildly different requirements and principles may exist, when thinking of software:

  • As research
  • As art
  • As exploration
  • As tool-making
  • As craft
  • As engineering ...