DEV Community: Samer Azani

Expressions Everywhere

Samer Azani — Tue, 23 Jul 2019 15:07:24 +0000

What is an expression?

Basically, it is any valid unit of code that resolves to a value.

Below is a list of some JavaScript terminology that has the word "expression" to them.

Literal value expression: any part of a statement or another expression that is to be used exactly as it is, like number 2 in the statement a = b + 2.

Variable expression: is any symbol in a statement or another expression that represents a certain current value. An example is the variable b in the statement a = b + 2.

Arithmetic expression: is a correct combination of numbers, operators, variables, and parenthesis. It resolves then to a certain value. Example is b + 2 in the statement a = b + 2.

String expression: is basically same as an arithmetic expression but evaluates to a string type and uses a string operator. Example:
var mystring = 'alpha';
mystring += 'beta';

Logical expression: expression that evaluates to true or false. Example:
false || (3 == 4)

Assignment expression: is the assignment of a literal, variable, or arithmetic expression to a certain variable. Example is a = b + 2.

Primary expressions: are basic keywords and general expressions in JavaScript. Examples are this, new, super, Spread operator...

Anonymous function expression: is the assignment of a function not having a name to another variable. Anonymous function expressions are very similar and have almost the same syntax as function statements. Example:
let foo = function() { ... };

Named function expression: is the assignment of a function having a name to another variable. Example:
let foo = function add(a, b) { return a + b };

Immediately invoked function expression (IIFE): is a type of function expression that is called immediately, and the variables called inside the function won't affect the surrounding code outside the IIFE. IFFE's can be either anonymous or named. Example:
function myIIFE(){
...
})();

Note: the last parenthesis is needed to invoke the function expression, whereas the first set of parenthesis prevents the function from being treated as a normal function declaration.

Regular expressions: are patterns used to match character combinations in strings. They are also objects.

How to learn a new programming language or concept

Samer Azani — Mon, 15 Apr 2019 08:33:09 +0000

Last year I started learning react, and I want to share how I started doing this. Below is my process when I want to learn something new and get better at it.

1. Taking online courses and watching videos:

I enjoy these courses since I can pause and start on my own pace. Many online platforms allow taking notes or bookmarking frames. Others provide exercises that can be done and share with the instructor or other members.

There are many platforms that offer online development courses. Some are short and specific, while others need more time and money investment.

Examples:
1) udemy.com
2) coursera.com
3) edx.org
4) teamtreehouse.com
5) udacity.com
6) theodinproject.com
7) codeacademy.com
8) khanacademy.org
9) pluralsight.com
10) freecodecamp.org

2. Doing a side project:

As a start online courses are beneficial. However, it is only when I do a side project on my own that the new information really kicks in and I got used to it. As with learning other stuff, exposure is key. Even if it is a small code addition, getting exposed to the new concept helps a lot in information retention.

3. Reading the official documentation:

This is usually my first step when I start learning a new language or concept. Often, the documentation are well-written and broad. In addition, depending on the material there, I may opt in for taking an online course, watching videos, or reading articles.

4. Reading blogs posts and articles:

While drinking coffee, I usually give myself half an hour in the morning to read about new stuff I'm learning. I read blog posts and discussions to get new ideas or clear some misconceptions.

When coding, I often use stackoverflow, github discussions, and other blog articles that help me in the new territory.

My favorites general blog platforms are:
1) dev.to
2) medium.com
3) stackoverflow.com
4) github.com

There are many other blog platforms that are specific to certain fields, like css, javascript or html. I can not list them all since there are so many.

5. Following people on Twitter:

This will allow me to follow the latest trends, discussions, and thoughts and get links to the latest articles and posts.

6. Exposure to community/peers:

Meeting people who have experience in that field, exchanging knowledge, and discussing new trends or best practices is very important. This is either in my workplace like pair-programming or reviews, or external places like conferences and meetups.

I am guilty of my shortcomings in attending conferences and meetups and am trying to improve this as soon as possible.

7. Being consistent in learning:

Everyone has their own pace in learning, and I don't compare myself to others. I ususally learn a part or module every other day and implement it. Most importantly, I do not stress myself and keep it fun.

8. Taking a break:

When I feel overwhelmed with the new material, I take a break and do something else. The break may vary from couple of minutes to several days. When I feel relaxed and rejuvenated, I come back to the topic with a refreshed mind and new energy.

9. Selecting enjoyable topics:

I usually select topics I enjoy doing, which is now related to web. Most of the times, I select a topic that compliments my existing knowledge but have not enough experience or exposure to.

10. Sharing what I know:

After having enough exposure and experience in the new material, it's time to give back and share when I can. This is with work colleagues, local communities, online blog posts and articles, and open-source projects. Open-source projects is one aspect, which I unfortunately lack, and am planning to improve in as well.

11. Doing a real-time client project:

This will forge everything I learned and will expose me to new depths in the new language.

At the end, it takes time depending on each person to fully understand a new topic. That said, what's your process for learning something new?

How to make good code reviews and win colleagues?

Samer Azani — Sat, 21 Jul 2018 07:02:58 +0000

Code reviews do not only improve the quality of code but are a great tool to learn from others and share experience. Doing and having code reviews is not an easy task. Pointing to or criticising your colleagues and peers is not something someone would like to do daily. Therefore, doing it in a constructive and positive manner would be beneficial to both the reviewer and reviewee.

Prepare:

1) Adhere to coding guideline or make one with your team members.

Use the right words:

2) Avoid using negative words and comments like "Remove", "Change", "Not needed", "No", "Bad", "I don't like this" etc...
3) Don't use sarcasm.
4) Avoid referring to code as "mine", "yours", or "theirs".
5) Ask questions instead of giving orders. Use questions like "Do you think this would be better?", "What do you think about...?"
6) Be positive. Don't say words like "I didn't do this", "It wasn't me" etc...

Clarify:

7) Explain the reason behind your comment and how it will improve the code.
8) Express yourself clearly and provide arguments. If needed, link to other code snippets or PRs.
9) Ask for clarification if the code is unclear. If there are too many questions it would be better asking them in person.
10) Be clear in the feedback. If a lot of discussion is needed it can be done in a different session.

Accept:

11) Learn from the comments and how others tackle the same problem.
12) Don't take it personal, code reviews are about the code and not you as a person.
13) Accept all feedback. Whether you are a Junior or Senior take feedback positively.
14) Be open to other ways of writing code or methods.
15) Don't turn the feedback into an ongoing argument. You can always talk to the commenter in person.

Support:

16) Be supportive. Help by pair-programming or showing an example.
17) Be responsive. Provide more information or clarification in the same day or after one day.
18) Be quick. Don't leave too many Pull Requests open. The codebase will grow, and the PR will stay behind.
19) Give positive feedback when the PR is accepted, like using the Like emoji or saying words like "Great, well done".
20) If a feedback helps, inform the reviewer how you find that helpful. Use words like "Good catch, thank you" etc...

Having a constructive and positive code review will foster a healthy work culture and allow team members to express themselves freely without the worry of shame and negative feedback. This will create an environment where team members feel respected, valued and productive. At the end it will allow an agile environment, knowledge sharing and growth.

Joining a Startup? A Personal Experience.

Samer Azani — Fri, 06 Jul 2018 08:27:06 +0000

I was fortunate enough to be part of a highly successful startup, which was later on acquired by a large international firm. This acquisition was the first of its kind in the Middle East and a big step forward in my career and personal life. Although I was not a co-founder or a stakeholder, I was fortunate enough to discover the world and dynamics of how startups function. I would say it was both stressful and enjoyable. You do learn a lot. Whether about new technologies where you get the chance to apply them, or about team members and about yourself.

Regardless whether a startup succeeds or fails, it is truly a very enriching and fulfilling personal experience. Of course not all startups share the similar work culture and circumstances, but below are my two cents regarding my personal experience.

1. Befriend adaptation and change

Working in a startup means experimenting with ideas and concepts. Some ideas do have an impact, some on the other hand do not. That is why it is important when having a target, to set out a plan and to stop at certain time intervals during execution, to reflect about the current situation, and to decide whether or not to continue with the plan or create a new one.

Change is present everyday and every time. Do not expect to a have a constant work environment. Sometimes you and your team will acknowledge that something in the big picture is not quite right, so a lot of change will be needed. That in turn will be reflected in the choice of technology you use, and the approach regarding the current issue at hand.

2. Develop a can-do attitude

When you stumble upon a problem relax and be confident about solving it. The situation is new, the problem is complex, lots of people depend on you, but hey - you can do it. Thinking about the problem as a whole will indeed seem hard, but by dividing it into smaller issues or by setting out a plan, that will certainly help you in keeping your confidence high and in allowing you to concentrate on the problem itself and not about your ability to overcome it.

Divide and Conquer is a really helpful strategy in this situation. Another way to develop a can-do attitude is to regularly discuss the situation and issue with others. May it be your colleague, your CEO, the whole team - what matters is to get different opinions on the matter and reach a collective plan to tackle it.

3. Learn a lot

Having change as your new friend with a can-do attitude will enable you to learn a lot. You will have a chance to learn something new everyday, whether it is a technical concept, communication style with team members, or even learn about your personality.

Since the technology used might be new and the features change often, you will learn new technologies, prototype a lot, and expand your knowledge set in other domains used in the startup. For example, I did not have previous experience about scaling and about website performance issues. After reaching a high level of user visits, that issue became our number one concern and all the team shifted to address the requirement. That is how I, and everyone else in the team, learned about scalability, performance, usability and much more.

You will also get the chance to discover yourself, your personality and how you deal with people around you in difficult situations. It will be an eye-opener and a great chance for personal growth and maturity.

4. Gain new friends and family

Working in a startup means interacting with people around you all the time. Whether they are colleagues, the CEO and management, entrepreneurs, or other networks - you will need to deal with people everyday. By doing so, you will meet new faces every other day and you will eventually make new acquaintances and friends.

In addition, you and your team will work very closely to each other on a daily basis. A startup is not in that sense a typical work environment, where everyone knows their social boundaries in the office. A startup is more family-based, where you and your team are driven by one target, one plan, and one collective effort with all the highs and lows that come with it.

5. Share your private life

By gaining new friends and family, you will have to say goodbye to some of your private life. You and your team will work very closely to each other, interact frequently, and share aspirations, hopes, good and bad times. Eventually, everyone will know whats going on with everyone else, and you will end up sharing some of your private life.

6. Expect to work on holidays and weekends

The startup workplace is very dynamic. Sometimes setting tough deadlines and committing to it, sometimes showing a prototype to an investor or VC, or other times encountering a problem and needing to address it as soon as possible. Otherwise the user base will decline instead of grow. All of these factors requires to have an open mindset and to work in unconventional times. Late night, weekends, public holidays - no matter the day be prepared to receive a call from a fellow teammate informing you about an issue you need to solve at that moment.

7. Work in a highly-motivated environment

In addition to the dynamics of a startup, startup teams are usually largely motivated. They have a common goal to reach to, they set-out a plan with sprints and retrospectives, they are armored with a can-do attitude, and they celebrate success and minimize losses. You will get a highly motivated, positive and enthusiastic environment.

8. Become more social and communicative

You will need to interact and talk to different people almost everyday. Because of the agile and dynamic type of startups, good and clear communication is crucial to the success of the product.

For example, if a feature is unclear or has missing information you will need then to reach out to your fellow team members. You will need to take the initiative and and be ready for the follow up.

9. Enjoy a lot

Startups are stressful. The pressure of deliverability, the constant change, the social aspects of dealing with your team members on an individual level, and the unforeseen and unknown future, all adds up to the stress of working in a startup. But in this journey you will definitely encounter pleasant and enjoyable moments, where you will certainly cherish unpredicted outcomes and situations.