Brainstorming: Tags

[guettli]

The current README is way too long. But how to structure it, so that it is easier to read?

I think tags are better than a book-like structure.

This issue is for brainstorming which tags could be usefull.

Feel free to add your ideas.

[guettli]

Testing

Datastructures

Programming (general)

Teamwork

Work-Life-Balance

Debugging

HTML

Python: https://github.com/guettli/python-tips

Django: https://github.com/guettli/django-tips

Kubernetes: https://github.com/guettli/learning-kubernetes-log

[zxenonx]

In addition to notes on Data Structures only, do you plan to add some notes about Algorithms as well? (this would be great)

Can we also add CI/CD and Design patterns?
@guettli

[guettli]

Yes, CI/CD makes sense.

With "Design patterns" ... I am unsure. I am not a big fan of design patterns. I prefer boring functions and libraries. Most Design Patterns handle "state". I don't like state. I prefer it stateless. State should in the DB, not in my code. Like http-requests. Requests should not last longer than some seconds.

But thank you for CI/CD there are already some notes about this topic in the README. Please add new ideas here, if things come to your mind.

[zxenonx]

Yes, CI/CD makes sense.

With "Design patterns" ... I am unsure. I am not a big fan of design patterns. I prefer boring functions and libraries. Most Design Patterns handle "state". I don't like state. I prefer it stateless. State should in the DB, not in my code. Like http-requests. Requests should not last longer than some seconds.

But thank you for CI/CD there are already some notes about this topic in the README. Please add new ideas here, if things come to your mind.

Oh, you're not a big fan of Design patterns...😕
You don't find it useful at all, do you?

What are the cases where design patterns are worth using?

[guettli]

I replied here: #17

I would like to keep this issue focused on "Brainstorming Tags". Please reply in above discussion (or start a new discussion).