Skip to main content

Dimensions of writing software

Some dimension in which I have to write software:

  • Domain-Knowledge (Problem-Domain)
  • Coding: How to write down a thought in a formal language. Includes testing
  • Design: How to structure the output of Coding
  • Refactoring: How to restructure on different levels including Coding
  • Teams: How to organize and lead teams 
  • Knowledge of Tools, Libraries, and Frameworks
  • Scientific Papers + Reading other Peoples Code + Reading Books (Solution-Domain)
  • Sales: How to sell it?
  • Deployment
I am missing some entries but more important, I am missing a simpler abstraction. I feel it but cannot formulate it yet.

Comments

Post a Comment

Popular posts from this blog

Futureproof Software

From here:  https://dzone.com/articles/the-secrets-of-futureproof-software Self-healing Self-patching, or more broadly, self-updating Backward compatibility Dynamic adaptation/ability to evolve over time Intent-based Made up of reusable futureproof components
Post a Comment
Read more

Choose Projects you do NOT do!

Inspiration from FluentC++ Choose which project NOT to work on. Be clear what you want and which projects are toxic. Keep the Hedgehog-concept in mind. Be sure that you are a) deeply passionate about the project b) the project can be the best in the world quality c) you can earn money with it If one of the three points is not met and not realistic soon don't do the project. Play around with it privately. Maybe you can pivot there so that it meets the criteria.
Post a Comment
Read more