Souvir  💡

Vim exit plan: - :q to quit - :q! to force quit - :wq to save and quit

There are many aspects to being a good developer, but it starts with seeing yourself as a professional. That mindset alone will move you in the right direction. Think about the areas of your profession you can work on, as you strive to become a good, truly professional developer

Design patterns can be categorized in multiple ways. The most popular is the following: - Creational - Structural - Behavioral - Concurrency - Architectural I'll review each category and most common patterns in future threads!

Conclusion, Design patterns: - is Abstract and Flexible
- controls Structure - a solution to a common but generic problem. - a general solution to a general problem. - often have to be implemented each time it is used.

"Each pattern describes a problem which occurs over and over again in our environment, and then describes the core of the solution to that problem, in such a way that you can use this solution a million times over, without ever doing it the same way twice" - Christopher Alexander

In other words, a design pattern is a way of structuring your code in order to elegantly express a relationship between functional components. You might use design patterns within the implementation of an algorithm.

A design pattern can't be directly translated to code. It is a "strategy" that can be useful for the design of an application. It’s a relatively vague description of how to solve a problem at an architectural level, with an emphasis on flexibility and maintainability.

Definition: A design pattern is a general repeatable solution to a commonly occurring problem in software design. It isn't a finished design that can be transformed directly into code but a description or template for how to solve a problem in many different situations.

[THREAD] As requested I'm starting a series of thread on design pattern. First: - An algorithm is a step-by-step recipe for performing some task - A design pattern is like a blueprint: a structured collection of objects, associations, and actions to accomplish some goal

Being open to learning is much more important than already knowing things.

Why was this piece of code written this way? What is the problem that that this feature solves? Who wrote this and is he still around to ask him? What do these guys know that I don’t? Next time ask why! You will be surprised by the answers and learn a lot

If you can choose any language to work with, without constraint, would you change the ones in your project?

So a thread it will be! I'll start by "what's a design pattern" for everyone to be able to follow Stay tuned

Abstractions aren’t vague messes  but useful tools