<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Masma Sajahan on Medium]]></title>
        <description><![CDATA[Stories by Masma Sajahan on Medium]]></description>
        <link>https://medium.com/@sajahanmasma?source=rss-61f212668cef------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wGs2VeL3y3v7ftKs3CrJqQ.jpeg</url>
            <title>Stories by Masma Sajahan on Medium</title>
            <link>https://medium.com/@sajahanmasma?source=rss-61f212668cef------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 10:22:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sajahanmasma/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Craft a Resume That Gets You Noticed: A Practical Guide for University Students]]></title>
            <link>https://medium.com/@sajahanmasma/how-to-craft-a-resume-that-gets-you-noticed-a-practical-guide-for-university-students-e14751a14c4e?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/e14751a14c4e</guid>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Mon, 24 Aug 2026 09:40:04 GMT</pubDate>
            <atom:updated>2026-08-24T09:40:04.572Z</atom:updated>
            <content:encoded><![CDATA[<p>Starting university is exciting. You learn new technologies, work on projects, meet new people, participate in events, and slowly begin to understand what you want to do in your career. But at some point, almost every university student faces an important question: <strong>“How do I present myself when I apply for an internship or a job?”</strong></p><p>One of the first answers to that question is your resume.</p><p>For many students, creating a resume can feel confusing. You may wonder what information should be included, how much information is enough, whether your university projects are worth mentioning, or what to write when you have little or no professional experience. The good news is that you don’t need years of industry experience to create a strong resume. You simply need to know how to present your existing skills, experiences, projects, and achievements in a clear and professional way.</p><p>This article is a practical guide for university students who want to create a resume that clearly communicates who they are, what they can do, and what they can contribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oAw4ZpNrBTnQCaEGpO9WSA.png" /></figure><h3>What Is a Resume?</h3><p>A resume is a professional document that highlights your qualifications, including your education, skills, experience, and achievements, to show your suitability for a job or other opportunity. In simple terms, you can think of your resume as a short introduction to your professional identity.</p><p>Before a recruiter meets you or speaks with you, your resume may be the first thing they see. It gives them an initial idea about your background, your abilities, and the type of opportunities you are looking for. This is why a resume is often described as your <strong>first impression</strong>.</p><p>Imagine that two university students are applying for the same internship. Both students have similar technical knowledge, but one submits a clear and well organized resume while the other submits a resume with poor formatting, unnecessary information, and long paragraphs. Even before the interview, the first student may create a stronger impression simply because their skills and experiences are presented more effectively.</p><p>However, a resume is not about making yourself look perfect. It is about making your <strong>real strengths easy to understand</strong>.</p><h3>Resume vs. CV</h3><p>Before creating your document, it is important to understand the difference between a resume and a CV. These two terms are often used interchangeably, but they can have different purposes.</p><p>A resume is generally concise and targeted, usually around one or two pages. It focuses on the skills, experiences, and achievements that are relevant to a particular job or opportunity. It is commonly used when applying for positions in companies and other industry environments.</p><p>A CV, or Curriculum Vitae, is generally more comprehensive. It can contain a detailed record of your academic and professional history, including research, publications, conferences, teaching experience, and other academic activities. It is commonly used for academic and research-oriented opportunities.</p><p>The most important point is not simply to remember the difference between the two. Instead, always check what the organization is asking for and understand the purpose of the document you are submitting.</p><h3>What Should a Good Resume Contain?</h3><p>There is no single resume format that is perfect for every person or every job. A good student resume should contain enough information for a recruiter to quickly understand your background and potential.</p><p>However, for university students, a strong resume can include the following sections:</p><p><strong>1.Header<br>2.Objective / About Me<br>3.Education<br>4.Technical Skills<br>5.Projects<br>6.Experience<br>7.Achievements / Awards<br>8.Leadership &amp; Extracurricular Activities</strong></p><p>Now let’s look at each section more closely.</p><h4>1.Start With a Clear Header</h4><p>The header is the first part of your resume, so it should immediately tell the reader who you are and how they can contact you. Your name should be clearly visible, followed by important contact details such as your phone number and professional email address. For IT students, it is also useful to include your LinkedIn and GitHub profiles when they are relevant and properly maintained.</p><p>One small detail that students sometimes overlook is their email address. Your resume is a professional document, so your email address should also look professional. An email such as “coolboy123@gmail.com” or “princessgirl456@gmail.com” may not create the impression you want. A simple email based on your name is a much better choice.</p><p>Your LinkedIn and GitHub profiles can also strengthen your resume. LinkedIn can provide more information about your professional background, while GitHub can give recruiters an opportunity to see your actual programming projects. But remember that including a link is useful only if the profile or repository is active, relevant, and presentable.</p><h4>2.Writing Your Objective or About Me</h4><p>The objective or “About Me” section gives the recruiter a quick idea about your career direction. It does not need to be a long paragraph. Two or three clear sentences are usually enough.</p><p>For example, instead of writing a very general statement such as, “I am seeking a challenging position in a reputed organization where I can utilize my skills and improve my knowledge,” try to be more specific. You could say that you are an IT undergraduate interested in software development and looking for an internship where you can apply your programming and problem-solving skills while gaining practical industry experience.</p><p>The difference is that the second statement actually tells the recruiter something about you. When writing your objective, think about three things: <strong>What am I interested in? What kind of opportunity am I looking for? What relevant skills can I bring?</strong></p><p>Also remember that an objective is not mandatory for every resume. If the rest of your resume already communicates your career direction clearly, you may choose to leave it out.</p><h4>3.Presenting Your Education</h4><p>As a university student, your education is one of the most important parts of your resume. Especially when you have limited professional experience, your degree shows the academic foundation you are currently building.</p><p>Include your degree or program, university name, and expected graduation date. If your GPA is strong and relevant, you may include it as well. You can also mention relevant coursework when it helps demonstrate that you have knowledge related to the position.</p><p>For example, an IT undergraduate might include their degree, university, and expected graduation year. If you are still in your first year, don’t think that you cannot include your education because you haven’t graduated yet. Simply indicate that your degree is currently in progress.</p><p>Your resume is supposed to represent where you are <strong>now</strong>, not only where you will be after graduation.</p><h4>4.Showcasing Your Technical Skills</h4><p>For IT students, the technical skills section can be one of the most important parts of the resume. Throughout university, you may learn programming languages, frameworks, databases, development tools, DevOps technologies, or even machine learning concepts.</p><p>However, avoid creating a huge list simply to make your resume look impressive. Instead, organize your skills clearly. For example, you might separate programming languages, web technologies, databases, and development tools into different categories. This makes the section easier for recruiters to scan.</p><p>More importantly, be honest about your skills. If you include Java, Python, React, Docker, or any other technology on your resume, you should be prepared to discuss it during an interview. It is much better to list five technologies that you genuinely understand than twenty technologies that you have only heard about.</p><p>Your resume should reflect your <strong>actual abilities</strong>, not your wishlist.</p><h4>5.Let Your Projects Demonstrate Your Skills</h4><p>For university students, projects are extremely valuable because they provide evidence that you can apply what you have learned.</p><p>You may not have professional industry experience yet, but you may have completed academic projects, group projects, personal projects, hackathons, or other technical work. These projects can demonstrate your programming ability, problem-solving skills, teamwork, and understanding of technologies.</p><p>However, simply listing a project name is not enough. Instead of writing, “Student Management System-Java,” explain what you built, what technologies you used, and what your contribution was.</p><p>For example, you could explain that you developed a student management system using Java and MySQL to manage student registration and academic information, and that you were responsible for implementing particular functionalities or designing part of the database.</p><p>This immediately gives the recruiter more information about your ability.</p><p>If your project is available on GitHub, include the repository link. For an IT student, saying that you know a programming language is useful, but showing a real project where you used that language can make your claim much stronger.</p><p>Don’t just tell people what you can do. Whenever possible, show them.</p><h4>6.Experience Is Not Only About Employment</h4><p>Many students think they cannot include an experience section because they have never worked for a company. But experience can mean more than a full-time or part-time job.</p><p>Internships, volunteer work, university organizational activities, event coordination, open-source contributions, and leadership responsibilities can all demonstrate valuable skills.</p><p>For example, being involved in a university technical organization may demonstrate teamwork, communication, planning, leadership, and responsibility. Organizing an event can show that you know how to coordinate with people, manage tasks, and work towards a common goal.</p><p>The important thing is to explain what you actually did.</p><p>Simply writing “Member of IEEE” does not tell the recruiter much. Instead, explain how you contributed to technical events, worked with a team, coordinated activities, or supported a particular initiative.</p><p>Your experience section should focus on your <strong>contribution</strong>, not just your position or membership.</p><h4>7.Highlighting Achievements and Awards</h4><p>Achievements and awards can help differentiate your resume from others. These can include coding competition results, hackathon achievements, scholarships, academic awards, research recognition, or other notable accomplishments.</p><p>You don’t need to have won a national competition to include an achievement. If something demonstrates your dedication, ability, or progress, it may be worth mentioning.</p><p>At the same time, don’t worry if your resume doesn’t contain a long list of awards. University is a learning period, and everyone develops at a different pace. If you don’t have many achievements yet, use your university years to explore opportunities such as competitions, workshops, technical communities, research projects, and volunteering.</p><p>The goal should not be to collect certificates just to make your resume longer. The goal should be to build meaningful experiences and skills.</p><h4>8.Leadership and Extracurricular Activities Matter Too</h4><p>A strong candidate is not defined only by technical knowledge. Employers also look for qualities such as communication, teamwork, leadership, adaptability, and time management.</p><p>This is where extracurricular and leadership activities can become valuable.</p><p>If you have worked with a student organization, organized an event, led a team, volunteered for a technical program, or participated in a university club, these experiences can show qualities that may not be visible from your technical skills alone.</p><p>However, once again, don’t simply list an organization or position. Explain the contribution you made and what you learned or achieved through the experience.</p><p>A good resume should show a journey: you learned something, applied it, contributed to something, and continued to grow.</p><h3>Customize Your Resume for Every Opportunity</h3><p>One of the most important resume-writing tips is to avoid sending exactly the same resume to every company.</p><p>Imagine that you are applying for two positions. One is a Software Engineering Internship, while the other is a Data Science Internship. Although your educational background may remain the same, the skills and projects you emphasize should be different.</p><p>Start by reading the job description carefully. Look at the technologies, skills, and qualities the employer is looking for. If you genuinely have those skills, make sure they are clearly visible in your resume.</p><p>This does not mean copying the job advertisement word for word. It means understanding what the employer needs and presenting your relevant qualifications clearly.</p><p>Think of your resume as a document that should be tailored to the opportunity, rather than a document that you create once and send everywhere.</p><h3>Keep the Design Simple and Professional</h3><p>A resume does not need to be filled with colors, graphics, icons, and complicated designs to look professional.</p><p>In fact, when it comes to resumes, <strong>clarity is more important than decoration</strong>.</p><p>Use clear headings, readable fonts, consistent spacing, and bullet points where appropriate. Make sure the information is easy to scan.</p><p>Remember that recruiters may have to review many applications. A clean and organized resume allows them to quickly find the information they need.</p><p>Instead of writing a long paragraph describing your project, use short and meaningful statements that explain what you did.</p><p>For example, rather than writing one large paragraph about developing a web application, you can describe the key contributions in a few clear sentences or bullet points.</p><p>Your goal is not to make the resume visually complicated. Your goal is to make it <strong>easy to understand</strong>.</p><h3>Use Action Words</h3><p>The words you use in your resume also matter.</p><p>Instead of repeatedly writing “Responsible for…”, use strong action words that clearly communicate your contribution. Words such as <strong>developed, designed, implemented, created, organized, led, achieved, and managed</strong> can make your statements more direct and meaningful.</p><p>For example, instead of saying, “Responsible for developing a website,” you could say, “Developed a responsive website using React.”</p><p>The second statement is more direct because it clearly tells the reader what you did.</p><p>Whenever you write a bullet point or description, ask yourself:</p><p><strong>“What did I actually do?”</strong></p><p>Then start the sentence with a strong action word.</p><h3>Common Resume Mistakes to Avoid</h3><p>Even if you have good skills and experiences, a few simple mistakes can make your resume less effective.</p><p>One common mistake is <strong>writing long paragraphs</strong>. Recruiters often review many resumes, so they should be able to find important information quickly. Instead of writing large blocks of text, use short sentences and bullet points to highlight your key contributions.</p><p>Another mistake is <strong>poor formatting</strong>. A resume doesn’t need complicated designs, too many colors, or different fonts. Keep the layout clean, consistent, and easy to read. Remember, <strong>clarity is more important than decoration</strong>.</p><p>Many students also <strong>copy resumes from others</strong>. Using a template for inspiration is fine, but the content should represent your own skills, projects, and experiences. Never add skills or achievements simply because they appear on someone else’s resume.</p><p>One of the most important mistakes to avoid is <strong>listing responsibilities instead of showing your contribution</strong>. For example, instead of writing <em>“Worked on a project,”</em> write <em>“Developed a web application using React.”</em> The second statement clearly shows what you actually did.</p><p>Finally, always check for <strong>spelling and grammar mistakes</strong>, remove irrelevant information, and make sure every skill you mention is something you can confidently explain during an interview.</p><p>Creating a good resume is not about making yourself look impressive by adding as much information as possible. It is about presenting your genuine skills, experiences, projects, and achievements in a way that is clear, relevant, and easy to understand.</p><p>As a university student, you may sometimes feel that you don’t have enough experience. But look at your journey carefully. Your projects show what you can build. Your technical skills show what you have learned. Your extracurricular activities show how you work with others. Your achievements show your effort and progress. Your experiences show how you apply what you learn.</p><p>You already have a story.</p><p>Your resume is simply the document that helps you <strong>tell that story professionally</strong>.</p><p>So don’t wait until graduation.</p><p>Start with what you have today. Keep learning, keep building, keep participating, and keep updating your resume.</p><p>Because when the right opportunity comes, you don’t want to start preparing from zero.</p><p><strong>You want to be ready.</strong></p><p>And remember:</p><p><strong>Your resume may be only one or two pages, but it can be the first step toward your next big opportunity.</strong></p><p>Found this helpful? Follow me on Medium for more practical tips, learning resources, and career insights for students and young professionals. Let’s learn and grow together.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e14751a14c4e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Me and YIT]]></title>
            <link>https://medium.com/@sajahanmasma/me-and-yit-a2a3664c8a40?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2a3664c8a40</guid>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Mon, 13 Jul 2026 04:30:15 GMT</pubDate>
            <atom:updated>2026-07-13T04:30:15.104Z</atom:updated>
            <content:encoded><![CDATA[<p>My journey with Yarl IT Hub started during my undergraduate days at the University of Vavuniya. As an IT student, I was always eager to explore new technologies, learn beyond the classroom, and connect with people who shared the same passion. That curiosity introduced me to Yarl IT Hub, and it became a meaningful part of my learning journey.</p><p>My first experience with YIT was through <strong>Uki</strong>, one of the transformative initiatives of Yarl IT Hub. In 2024, I applied for the <strong>12-week Data Science Program</strong> and, after going through the application process and aptitude test, I was selected for the program.</p><p>That was my first step into a structured learning experience beyond university. The sessions helped me strengthen my knowledge in Data Science while giving me the opportunity to learn, interact, and build connections with a wonderful learning community.</p><p>Being an IT undergraduate, I was always motivated to explore different areas of technology. Later, I applied for Uki’s <strong>Short Course — Introduction to AWS</strong>, which became my first exposure to cloud computing and AWS technologies. Completing the course assignments and learning from industry-oriented content was a valuable experience that expanded my technical perspective.</p><p>From that point onwards, I started following YIT’s activities, staying connected with their initiatives, and learning from the opportunities they created for the community.</p><p>After completing my degree in 2025, I got another opportunity to connect with YIT through the <strong>Uki Lecturer vacancy</strong>. I was shortlisted for the interview and attended. Although I could not commit as a full-time lecturer at that time due to my professional commitments, being considered for the opportunity itself was a memorable experience and another valuable connection with the YIT community.</p><p>In early 2026, YIT announced the <strong>Leadership Excellence Program — Cohort 03</strong> with a full scholarship opportunity. With many applicants, I was grateful to be shortlisted and participate in the 4-day program.</p><p>This experience was more than just a workshop. It was a space for reflection, learning, and growth. Through interactive sessions and activities, I gained deeper insights into self-awareness, communication, strategic thinking, and meaningful leadership. The opportunity to connect with passionate peers, mentors, and professionals from different backgrounds made the journey even more inspiring.</p><p>Coming from a background where I always enjoyed volunteering and sharing knowledge, my university journey was not only about academics but also about contributing to communities. Although I had travelled with YIT activities during 2024 and 2025, I had not yet received the chance to actively volunteer. That changed in 2026.</p><p>As part of <strong>Yarl Geek Challenge Season 15 — Junior</strong>, I had the wonderful opportunity to contribute as a resource person and mentor with the support of the Vavuniya YIT team.</p><p>I conducted sessions for students in the Robotics (Arduino) category at the zonal level, introducing them to Arduino boards, electronic components, circuit simulation using Tinkercad, and how technology can be used to solve real-world environmental problems.</p><p>Later, I had the privilege of conducting another session at <strong>V/Puthukulam Maha Vidyalaya</strong> with the participation of more than 100 students from different schools. Seeing their curiosity and enthusiasm reminded me of my own school days when I attended similar workshops conducted by resource persons. Back then, I admired their confidence and always had a small dream of standing in front of students one day and guiding them.</p><p>Today, through learning, passion, and volunteering, I am grateful to experience that dream.</p><p>The journey continued from seminars to hands-on workshops. During the YGC Season 15 Junior workshop series, I had the opportunity to mentor students in the <strong>Web &amp; Mobile Development</strong> category, guiding them on prototype development, improving their ideas, using AI tools, understanding modern development approaches, and bringing their solutions closer to implementation.</p><p>Watching students move from having only ideas to developing actual solutions within a short period was truly inspiring. Their creativity and willingness to solve problems showed the potential of the next generation of innovators.</p><p>Although I could not participate in the zonal and district-level competitions due to unavoidable circumstances, every experience I gained through YIT has been valuable.</p><p>Looking back, my journey with Yarl IT Hub has been a beautiful combination of learning, networking, volunteering, mentoring, and personal growth.</p><p>From being a learner through Uki programs to becoming a mentor for young innovators, YIT has given me opportunities that shaped both my technical and personal development.</p><p><strong>15 years of YIT is not just a milestone; it is a collection of countless stories, connections, and dreams. I am truly happy to be a small part of this journey.</strong></p><p>I am eagerly looking forward to attending the <strong>YGC Innovation Festival 2026</strong> and continuing my journey with YIT. In the future as well, I hope to contribute, volunteer, share knowledge, and support the growth of this amazing community.</p><p>Thank you, Yarl IT Hub, for creating opportunities, inspiring people, and building a community where learning and giving back go hand in hand.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fsIqxWT-Tv3vx2Cc5XYIRg.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2a3664c8a40" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 04 -Understanding People, Building Connections, and Creating Communities]]></title>
            <link>https://medium.com/@sajahanmasma/day-04-understanding-people-building-connections-and-creating-communities-c52e182ae920?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/c52e182ae920</guid>
            <category><![CDATA[networking]]></category>
            <category><![CDATA[people]]></category>
            <category><![CDATA[community-building]]></category>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Wed, 08 Apr 2026 07:58:36 GMT</pubDate>
            <atom:updated>2026-04-08T07:58:36.039Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ynf4UdZJLxGBJ7AZpf1FMQ.png" /></figure><p>The final day of the Leadership Excellence Program felt different from the beginning. By this time, we had explored leadership, goal setting, communication, and thinking models. Day 4 brought everything together by focusing on something at the heart of leadership.</p><p>We started the day by discussing cultural differences. A simple sentence, gesture, or body language can carry completely different meanings in different cultures. What feels normal in one environment may be misunderstood in another. This made me realize that leadership is not only about ideas and decisions ,it is also about understanding diverse perspectives.</p><h4>Looking Beyond the Surface: The Iceberg of Culture</h4><p>To understand cultural differences better, we learned about the <strong>Iceberg Model of Culture</strong>. The concept explains that only a small part of culture is visible above the surface things like clothing, food, language, and rituals. These are easy to observe, but they do not fully define a culture.</p><p>The larger part lies beneath the surface. This “deep culture” includes values, communication styles, beliefs, attitudes toward time, and unwritten social rules. These hidden elements strongly influence behavior, yet they are not immediately visible.</p><p>This idea helped me understand why misunderstandings happen. Sometimes we judge based on what we see, without understanding the deeper cultural context. Areas such as values, communication patterns, concept of time, and personal space often lead to cross-cultural misunderstandings. We also discussed how communication styles differ across countries, reminding us that effective leaders must adapt to diverse audiences.</p><h4>The Importance of Professional Networking and Mentoring</h4><p>The session then shifted to professional networking. Networking is not just about exchanging contacts ,it is about building meaningful professional relationships. We discussed maintaining professionalism during networking by avoiding sensitive topics such as politics, religion, age, or personal matters. Another important lesson was the value of follow-ups. Meeting someone at a conference is only the beginning; maintaining the connection afterward creates long-term opportunities.</p><p>From networking, we moved to mentoring a powerful relationship for personal and professional growth. A mentor is not someone who gives orders or judgments. Instead, a mentor listens actively, respects confidentiality, and guides through thoughtful questioning. On the other hand, a mentee should take initiative, set goals, listen actively, and approach the relationship with a positive mindset.</p><p>We also learned that mentoring is different from coaching and counseling. Coaching is more active and performance-driven, while mentoring is more supportive and experience-based. Counseling focuses on personal challenges, whereas mentoring focuses on growth. Importantly, mentor-mentee relationships can naturally come to an end, and that is perfectly acceptable.</p><h4>From Individuals to Communities</h4><p>The final discussion of the program focused on building communities. We explored the difference between a community and a movement. A community focuses on connection, identity, and belonging, such as user groups built around shared interests. A movement, however, focuses more on action, advocacy, and change.</p><p>Creating a strong community requires a clear vision, shared values, and collective ownership. We discussed important attributes such as encouraging open participation, maintaining transparency, and involving members in decision-making. Communities grow when people feel recognized, valued, and empowered to contribute. Releasing ideas early, iterating quickly, and learning together were also highlighted as key principles.</p><p>This part of the session made me realize that leadership does not stop at individual success. True leadership creates spaces where people connect, collaborate, and grow together.</p><h3>Final Reflection -The End of a Meaningful Journey</h3><p>As the program concluded, I reflected on the four days as a whole. Day 1 taught me how to define leadership and set meaningful goals. Day 2 showed me how to communicate ideas effectively. Day 3 challenged me to think differently. And Day 4 reminded me that leadership is ultimately about understanding people and building communities.</p><p>This final day emphasized empathy, cultural awareness, networking, mentoring, and collaboration all essential qualities for meaningful leadership.</p><p>The program may have ended, but the learning continues. These four days did not just provide knowledge; they reshaped how I think, communicate, and connect with others.</p><p>And that, for me, is the true essence of leadership.</p><p>If this sparked something in you, follow me on Medium to read more blogs.</p><p>Let’s grow together.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c52e182ae920" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 03 -Learning to Think Differently]]></title>
            <link>https://medium.com/@sajahanmasma/day-03-learning-to-think-differently-f9f913e2aad9?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/f9f913e2aad9</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[thinking-differently]]></category>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Mon, 09 Mar 2026 08:36:07 GMT</pubDate>
            <atom:updated>2026-03-09T08:36:07.958Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*36oVZBXV-x_vXJBgajmbxw.png" /></figure><p>Day 3 of the Leadership Excellence Program focused on something deeper than skills or tools. It focused on <strong>how we think</strong>.</p><p>Often, when solving problems, we rely on our habits or past experiences. But the session introduced us to <strong>mental models</strong> frameworks that help us analyze situations more clearly and make better decisions. These models help us break down complex problems, explore possibilities, and look at challenges from different perspectives.</p><h4>Rethinking Problems Through Mental Models</h4><p>One of the first models we discussed was <strong>thinking from first principles</strong>. This approach encourages us to go back to the most basic truth of a problem instead of relying on assumptions. By breaking a problem into its fundamental parts, we can rebuild the solution in a more innovative way. A well-known example is <strong>Tesla</strong>. Instead of improving traditional petrol cars, the thinking shifted to a deeper question: transportation does not actually require petrol, it requires <strong>energy</strong>. This shift in perspective opened the door for electric vehicles.</p><p>Another interesting model was <strong>second-order thinking</strong>, which encourages us to look beyond immediate results. Many decisions appear beneficial at first, but their long-term consequences may be very different. For instance, companies sometimes provide incentives or extra rewards for sales executives who bring new customer connections. While this may increase short-term sales, second-order thinking asks what might happen later, pressure on employees, unhealthy competition, or unsustainable practices. Thinking about these deeper effects helps us make wiser decisions.</p><p>We also explored the <strong>inversion model</strong>, which suggests solving problems by looking at them from the opposite direction. Instead of asking how to succeed, we ask how failure might happen. By identifying possible mistakes or negative outcomes, we can avoid them more effectively. Sometimes preventing failure is just as powerful as planning success.</p><p>Another creative approach discussed was the <strong>thought experiment</strong>. A thought experiment involves imagining hypothetical situations to explore complex ideas that cannot easily be tested in reality. For example, if we were designing a society from the beginning, we would need to consider differences in language, abilities, financial situations, and vulnerabilities among people. This exercise highlights the importance of values such as inclusion, equality, diversity, and social safety. Thought experiments allow us to visualize possibilities and evaluate ideas before implementing them.</p><h4>From Ideas to Solutions: The Ideathon Approach</h4><p>After exploring mental models, we moved on to a structured approach for generating ideas known as an <strong>Ideathon</strong>.</p><p>The process begins with clearly defining the problem. Once the problem is identified, we analyze the context and constraints surrounding it. These constraints could be related to resources, environment, or time. Finally, the problem statement is reframed from the perspective of a real user. Looking at the problem through the eyes of the user ensures that the solution addresses real needs rather than assumptions.</p><p>This approach reminded me that innovation often begins with asking the right question.</p><h4>Understanding Behavior with the Fogg Model</h4><p>The final concept of the day was the <strong>Fogg Behavioral Model</strong>, developed by <strong>BJ Fogg</strong>. According to this model, behavior occurs when three elements come together: <strong>Motivation, Ability, and Prompt</strong>.</p><p>Motivation is the desire to perform an action. Ability refers to how easy it is to perform that action. Prompt is the trigger that reminds or encourages someone to act at a specific moment.</p><p>A simple real-world example can be seen in social media platforms like <strong>Instagram</strong>. These platforms increase <strong>ability</strong> by keeping users logged in, removing the need to sign in repeatedly. They increase <strong>motivation</strong> through social engagement such as likes, comments, and interactions. Finally, they send <strong>prompts</strong> in the form of notifications whenever someone reacts to a post. When motivation, ability, and prompt come together, the behavior, opening the app and engaging with it happens naturally.</p><h4>My Reflection</h4><p>Day 3 made me realize that leadership and innovation start with <strong>better thinking</strong>. Mental models give us tools to question assumptions, explore consequences, and imagine possibilities.</p><p>If Day 1 was about setting goals and Day 2 was about communicating them, Day 3 was about <strong>training the mind to think differently</strong>.</p><p>And sometimes, changing the way we think is the first step toward changing the world.</p><p>If this sparked something in you, follow me on Medium to read about Day 4 of this transformative experience.</p><p>Let’s grow together.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f9f913e2aad9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 02-Learning to Think Before We Present]]></title>
            <link>https://medium.com/@sajahanmasma/day-02-learning-to-think-before-we-present-15d15f282ab3?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/15d15f282ab3</guid>
            <category><![CDATA[think]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[present]]></category>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Wed, 04 Mar 2026 07:39:03 GMT</pubDate>
            <atom:updated>2026-03-04T07:39:03.239Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6YCSiGpNIDrecreWvwP1GA.png" /></figure><p>Day 2 began by revisiting what we had learned on the first day. It was refreshing to reflect on leadership and goal setting before moving into something equally powerful communication.</p><p>Because no matter how strong a leader we become, at some point we will need to present. In classrooms, meetings, interviews, pitches, or conferences presentations are unavoidable. Yet many of us prepare slides without truly understanding how to prepare our thinking.</p><p>That was the focus of Day 2.</p><p>We explored a mental model discussed in the book <strong><em>Presenting to Win</em></strong> by <strong>Jerry Weissman</strong>. The core idea was simple but transformative: before designing slides, define the goal of your presentation.</p><h4>Step 1: Define the Goal of the Presentation</h4><p>Every presentation must have a clear goal. But not just any goal ,a goal that drives three outcomes in the audience:</p><h4>1.Understand (Why)</h4><p>The audience must understand the reason behind the message.<br> Why does it matter?<br> How does it fit into the bigger picture?</p><p>Without understanding, information remains shallow.</p><h4>2.Believe (Conviction)</h4><p>The audience must emotionally and intellectually buy into the idea.<br>They need confidence in the message and trust in the presenter.</p><p>Without belief, there is no commitment.</p><h4>3.Act (Execution)</h4><p>Finally, the goal of a presentation is action.<br>When understanding and belief are established, action becomes natural and focused.</p><p>This framework made me realize something important:<br>A presentation is not about speaking. It is about transformation.</p><p>A presentation must do three things. It must help the audience understand why the topic matters. It must help them believe in the idea and trust the message. And finally, it must move them to act. Without these three elements understanding, belief, and action a presentation is just information delivery, not influence.</p><p>That realization made me rethink how I approach speaking opportunities. I used to focus on “What should I say?” Now I started thinking, “What should they understand, believe, and do?”</p><h4>Step 2: Consider the Settings</h4><p>Before speaking, we must ask:</p><ul><li>Who is the audience?</li><li>Where is the venue?</li><li>When is the presentation?</li></ul><p>These factors change everything tone, examples, depth, even body language.</p><p>A presentation for students is different from one for executives.<br>A classroom environment is different from a formal conference hall.</p><h4>Step 3: Audience Analysis -The Shift in Perspective</h4><p>One powerful idea stood out:</p><p>We must see the presentation through the audience’s eyes — not our own.</p><p>This requires understanding:</p><ul><li>Their background knowledge</li><li>Their expectations</li><li>Their motivations</li><li>Their concerns</li></ul><p>And most importantly, we must answer the silent question in every listener’s mind.</p><p>One concept that stayed with me was <strong>WIIFY “What’s In It For You?”</strong> Every audience silently asks this question. If we fail to answer it, we lose attention. Effective presenters don’t speak from their own perspective; they speak from the audience’s viewpoint. That shift from self-focus to audience-focus felt powerful.</p><h4>Building the Mind Map Before the Slides</h4><p>Before preparing slides, we learned to create a mind map.</p><p>This process had three steps:</p><p>1.List all related ideas freely.<br>2.Connect ideas and remove unnecessary points.<br>3.️Finalize the logical flow.</p><p>I realized that many presentations fail because they jump directly into slide creation without organizing thoughts first.</p><p>Clarity in thinking leads to clarity in delivery.</p><h4>The 5P Mental Model — Structuring an Initiative</h4><p>The next major learning was the <strong>5P Mental Model.</strong> we explored the 5P mental model to structure an initiative properly positioning, portfolio, people, process, and performance. It pushed us to think strategically which helps structure an initiative clearly and strategically.</p><p>We were asked to apply this model to our own initiative.</p><h4>1. Positioning</h4><p>How do you introduce your initiative?<br> What is its identity?<br> Name, website, social media presence.<br> We also explored tools like the Message House technique to structure communication.</p><h4>2. Portfolio</h4><p>What exactly are you offering?<br> What value or services does your initiative provide?</p><h4>3. People</h4><p>Who supports or runs the initiative?<br> Employees? Co-workers? Stakeholders?</p><h4>4.Process</h4><p>What structured methods ensure quality and consistency?<br> For example: quality-checking processes.</p><h4>5. Performance</h4><p>How do you measure success?<br> For businesses, it may be revenue.<br> For projects, it may be impact or growth metrics.</p><h4>The Power of Checklists</h4><p>We ended the day with something simple yet powerful: creating checklists. For every task of an initiative, we can create structured tracking with:</p><ul><li>Deadline</li><li>Status</li><li>Assignee</li><li>Action steps</li></ul><p>It reminded me that leadership and execution are not only about vision they are about systems.</p><h3>My Reflection — Day 2</h3><p>Day 2 taught me how to communicate them.</p><p>I learned that effective presentation is not about slides or speaking skills alone. It is about clarity of purpose, understanding the audience, structuring ideas, and measuring performance.</p><p>Most importantly, I realized:<br>Before we try to influence others, we must first organize our thinking. <br>And that was a powerful lesson.</p><p>If this sparked something in you, follow me on Medium to read about Day 3, and Day 4 of this transformative experience.</p><p>Let’s grow together.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15d15f282ab3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Day 01- The Day I Redefined Leadership and Goals]]></title>
            <link>https://medium.com/@sajahanmasma/day-01-the-day-i-redefined-leadership-and-goals-739877589bce?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/739877589bce</guid>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Wed, 18 Feb 2026 06:07:31 GMT</pubDate>
            <atom:updated>2026-02-18T06:07:31.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Fame4mtuCUZXImVD25knHw.png" /></figure><p>The first day of the Leadership Excellence Program did not begin with a lecture.It began with introductions.</p><p>At first, it felt simple the facilitator introduced themselves, and then each of us shared who we were. But as the session unfolded, I realized something important: the facilitator wasn’t just collecting names. They were creating a space where everyone felt comfortable, heard, and valued.</p><p>And that was my first lesson in leadership.</p><h4>“Leadership is Creating the Environment for Others to Succeed”</h4><p>One sentence stayed with me throughout the day:</p><p>“Leadership is creating the environment for others to succeed.”</p><p>Until that moment, I had always connected leadership with authority, decision-making, and responsibility. But this definition shifted my mindset. Leadership is not about standing in front ,it is about building a space where others can grow confidently.</p><p>We also reflected on insights from <strong>Sheryl Sandberg</strong>, particularly her perspective on stepping forward and supporting others. Her ideas encouraged us to think beyond titles and focus on impact.</p><p>Then came a powerful activity.</p><p>We were asked to think about one leader we admire and explain why. Different names were shared some global leaders, some personal mentors, some family members. As I listened to others, one key realization stood out:</p><p>Not everything a leader does is right.We should not blindly admire someone. Instead, we should admire the right qualities in them ,their resilience, integrity, discipline, or compassion and consciously adopt those traits.</p><p>That discussion felt honest and mature. Leadership is not about perfection. It is about learning selectively and growing intentionally.</p><h3>From Leadership to Life Goals</h3><p>The session then moved into something deeply personal: goal setting.</p><p>But this wasn’t the usual “write your goals and work hard” advice. It was structured, practical, and thought-provoking.</p><p>We started with a <strong>SWOT analysis</strong>.</p><p>Looking at our Strengths and Weaknesses forced us to be honest with ourselves. These were internal part of our personality. Then we identified Opportunities and Threats, which come from our environment.</p><p>It made me realize something important: success is not only about ambition. It is about understanding both yourself and your surroundings.</p><h4>Writing My Wish List</h4><p>Next, we were asked to write a “wish list” — everything we want to achieve in life.</p><p>No filtering.<br>No judging.<br>Just writing.</p><p>Financial goals. Health goals. Professional goals. Spiritual goals. Personal development goals.</p><p>As I wrote mine down, I noticed how wide my ambitions were. But then came the challenging part.</p><p>We had to identify:</p><ul><li>Competitive goals (goals that clash with each other)</li><li>Dependent goals (goals that rely on another goal first)</li></ul><p>I had never analyzed my goals in this way before. It made me realize that not all goals can be chased at the same time.</p><p>Then we prioritized them.</p><p>And finally, we were told something simple but powerful:</p><p>If your goals are more than seven, reduce them.<br>Five goals are ideal. That moment taught me that clarity creates focus. Too many goals can become distractions.</p><h4>Testing the Goals .Are They Really Strong?</h4><p>We evaluated our shortlisted goals using the <strong>SMART</strong> method:<br> Specific, Measurable, Achievable, Relevant, and Time-bound.</p><p>It helped refine vague dreams into structured plans.</p><p>But the learning didn’t stop there. We were introduced to the <strong>PACT</strong> framework- a system that focuses more on daily actions and outputs rather than just final outcomes.</p><p>That was eye-opening. Sometimes we focus so much on the end result that we forget about the daily discipline required to reach it. PACT reminded me that leadership and success are built in daily habits — not in future celebrations.</p><h4>Staying Committed to What We Set</h4><p>One of the most practical parts of the session was about reminding ourselves of our goals.</p><p>We discussed creative methods:</p><ul><li>Creating a dream board</li><li>Choosing a unique keyword for our goals</li><li>Setting reminders as phone wallpaper</li><li>Pasting goals on mirrors or walls</li><li>Keeping them near our bed</li></ul><p>Why?</p><p>Because sometimes we feel like we have “already achieved” something just because we talked about it or wrote it down. Visual reminders keep us grounded and accountable.</p><h4>Two Questions That Made Me Pause</h4><p>Before closing the session, we were asked to reflect on two questions for each goal:</p><ol><li>What distractions can stop me from achieving this goal?<br> And how will I overcome them?</li><li>If I do not achieve this goal, what will happen?</li></ol><p>The second question stayed with me. It was uncomfortable,but powerful.</p><p>Thinking about the consequences of not achieving my goals created a deeper level of responsibility inside me.</p><h3>My Reflection at the End of Day 1</h3><p>When I walked into the program on Day 1, I expected to learn about leadership techniques.</p><p>Instead, I learned about myself.</p><p>I learned that leadership starts by creating space for others.<br>I learned that admiration should be selective and thoughtful.<br>I learned that goals need structure.<br>And most importantly, I learned that daily disciplined action matters more than big dreams alone.</p><p>Day 1 did not just teach me concepts. It challenged my thinking.</p><p>And it was only the beginning.</p><p>Leadership is a journey, not a destination and I’m documenting mine in real time.</p><p>If this sparked something in you, follow me on Medium to read about Day 2, Day 3, and Day 4 of this transformative experience.</p><p>Let’s grow together.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=739877589bce" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Beginner-Friendly Introduction to Code Quality and Security Tools]]></title>
            <link>https://medium.com/@sajahanmasma/a-beginner-friendly-introduction-to-code-quality-and-security-tools-de7ecad7e629?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/de7ecad7e629</guid>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Mon, 22 Sep 2025 06:13:16 GMT</pubDate>
            <atom:updated>2025-09-22T06:13:16.204Z</atom:updated>
            <content:encoded><![CDATA[<p>In today’s world, software is everywhere from mobile apps to cloud platforms. But writing code is not just about making it work; it’s also about making it <strong>safe, clean, and easy to maintain</strong>. That’s where code quality and security tools come in.</p><p>Recently, I explored three popular tools: <strong>Snyk, Semgrep, and SonarQube</strong>. Each of them helps developers write better and more secure code, but in different ways. In this blog, I’ll share what these tools do, why they matter, and when you might use them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q1OrEDB-wmXcTXegaGIxFA.png" /></figure><h3>1. Snyk — The Security Specialist</h3><p>Snyk is mainly about <strong>security</strong>. It scans your code, dependencies, containers, and even cloud configurations for known vulnerabilities.</p><p><strong>Best for</strong>: Developers who use a lot of third-party libraries (like npm packages in Node.js, Maven in Java, or pip in Python).</p><p><strong>Strengths</strong>:</p><ul><li>Finds vulnerabilities in dependencies.</li><li>Suggests fixes or safe versions.</li><li>Integrates with GitHub/GitLab/CI-CD pipelines.</li></ul><p>Example: If you install a library that has a security hole, Snyk will warn you before you deploy.</p><h3>2. Semgrep — The Pattern Finder</h3><p>Semgrep is like a <strong>super-smart search tool for code</strong>. The name comes from “semantic grep.” It looks for patterns in code and can detect security issues, bad practices, or even enforce coding style.</p><p><strong>Best for</strong>: Teams that want <strong>custom rules</strong> for checking their code.</p><p><strong>Strengths</strong>:</p><ul><li>Lightweight and fast.</li><li>Easy to write your own rules.</li><li>Works with many languages.</li></ul><p>Example: You can create a rule that flags whenever someone uses eval() in JavaScript, since it can be risky.</p><h3>3. SonarQube — The All-in-One Quality Platform</h3><p>SonarQube goes beyond security. It checks for <strong>bugs, code smells, duplications, maintainability issues, and vulnerabilities</strong>. Think of it as a health report for your entire codebase.</p><p><strong>Best for</strong>: Teams working on large projects where <strong>long-term code quality</strong> matters.</p><p><strong>Strengths</strong>:</p><ul><li>Detects “code smells” (bad patterns).</li><li>Tracks technical debt.</li><li>Supports 20+ languages.</li><li>Provides dashboards with detailed reports.</li></ul><p>Example: SonarQube can point out that your method is too long, duplicated in many files, or not following naming conventions.</p><h3>How to Use These Tools</h3><h4>Snyk</h4><p>Snyk can be used by connecting it to your GitHub, GitLab, or local project. Once linked, it automatically scans for vulnerabilities in your dependencies and suggests safer versions to use. It’s very handy if your project relies on a lot of third-party packages.</p><h4>Semgrep</h4><p>Semgrep works by scanning your source code with ready-made rules from the community or with custom rules you define. It’s lightweight and can run directly from the terminal, giving instant feedback about risky code patterns or style issues.</p><h4>SonarQube</h4><p>SonarQube is usually set up on a server and works best for teams. After connecting your code repository, it provides a detailed dashboard showing bugs, code smells, duplications, and security issues. It’s especially powerful for tracking long-term code quality across big projects.</p><h3>Comparison at a Glance</h3><h4>Snyk</h4><p><strong>Focus:</strong> Security + Vulnerabilities<br><strong>Best For:</strong> Projects with many dependencies<br><strong>Key Strengths:</strong> Finds known issues fast, suggests fixes<br><strong>Limitation:</strong> Mostly about security, not overall quality</p><h4>Semgrep</h4><p><strong>Focus:</strong> Static analysis + Custom rules<br><strong>Best For:</strong> Teams needing specific code checks<br><strong>Key Strengths:</strong> Flexible, fast, easy to customize<br><strong>Limitation:</strong> Requires writing/choosing rules</p><h4>SonarQube</h4><p><strong>Focus:</strong> Overall code quality + Security<br><strong>Best For:</strong> Large or long-term projects<br><strong>Key Strengths:</strong> Comprehensive reports, multiple metrics<br><strong>Limitation:</strong> Heavier setup, needs a server</p><p>Exploring these tools opened my eyes to how much easier it is to keep code secure and clean when you have the right helpers.</p><ul><li><strong>Snyk</strong> protects against hidden vulnerabilities.</li><li><strong>Semgrep</strong> lets you enforce coding rules your way.</li><li><strong>SonarQube</strong> keeps your entire codebase healthy over time.</li></ul><p>If you’re a developer or a student learning about software engineering, I recommend trying these out. Even small steps in improving code quality can make a huge difference in the long run.</p><p>If you found this helpful, consider<strong> following me on Medium</strong> for more tech explorations.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de7ecad7e629" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Journey into Angular: Learning the Basics as a Beginner]]></title>
            <link>https://medium.com/@sajahanmasma/my-journey-into-angular-learning-the-basics-as-a-beginner-1c735f2ff9e1?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c735f2ff9e1</guid>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Tue, 02 Sep 2025 10:40:39 GMT</pubDate>
            <atom:updated>2025-09-02T10:40:39.176Z</atom:updated>
            <content:encoded><![CDATA[<p>When I recently joined my new company, I discovered that their front-end stack is built with <strong>Angular</strong>. To be honest, I had only heard about Angular before, but never had hands-on experience with it. Since it’s a core part of my work now, I decided to start learning it step by step.</p><p>In this post, I want to share my initial journey and the <strong>Angular basics</strong> I’ve learned so far. Hopefully, this helps anyone else who is just starting with Angular (and also helps me remember what I’ve learned).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BLiauVUZbd5yaROoqzRNiA.png" /></figure><h3>What is Angular?</h3><p>Angular is a <strong>TypeScript-based framework</strong> developed and maintained by <strong>Google</strong>. It’s used to build modern, scalable, and dynamic web applications. Unlike libraries like React, Angular is a <strong>full-fledged framework</strong> that comes with everything you need routing, HTTP client, forms, state management, and more.</p><p>Some reasons why companies love Angular:</p><ul><li>Strong structure → good for large teams</li><li>TypeScript built-in → safer and more maintainable code</li><li>Supported by Google → long-term reliability.</li></ul><h3>Setting Up My First Angular Project</h3><p>The first step was setting up the environment. I installed <strong>Node.js</strong> and then installed Angular CLI globally:</p><pre>npm install -g @angular/cli</pre><p>After that, I created my first Angular app:</p><pre>ng new my-first-app<br>cd my-first-app<br>ng serve</pre><p>Running ng serve opened the app at http://localhost:4200. Seeing “Welcome to my-first-app!” on the browser felt like a small victory .</p><h3>Understanding Angular Basics</h3><h4>1. Modules</h4><p>Modules in Angular are like <strong>containers or organizational units</strong> that group related parts of your app together. Every Angular application starts with a <strong>root module</strong>, usually called AppModule.</p><ul><li>Modules help Angular know which components, directives, and services belong together.</li><li>You can create <strong>feature modules</strong> for different parts of your app (e.g., a UserModule or ProductModule) to keep your code organized.</li><li>Example of a basic module:</li></ul><pre>import { NgModule } from &#39;@angular/core&#39;;<br>import { BrowserModule } from &#39;@angular/platform-browser&#39;;<br>import { AppComponent } from &#39;./app.component&#39;;<br><br>@NgModule({<br>  declarations: [AppComponent],  // components that belong to this module<br>  imports: [BrowserModule],      // other modules to import<br>  providers: [],                 // services<br>  bootstrap: [AppComponent]      // starting component<br>})<br>export class AppModule { }</pre><h4>2. Components</h4><p>Components are the <strong>building blocks of the UI</strong> in Angular. Every component has three parts:</p><ol><li><strong>TypeScript file (</strong><strong>.ts)</strong> – contains the logic and data.</li><li><strong>HTML template (</strong><strong>.html)</strong> – defines how the component looks.</li><li><strong>CSS/SCSS file (</strong><strong>.css/</strong><strong>.scss)</strong> – styles the component.</li></ol><p>Each component is reusable and can be added to different parts of your app. For example, a NavbarComponent can be used on multiple pages.</p><pre>import { Component } from &#39;@angular/core&#39;;<br><br>@Component({<br>  selector: &#39;app-navbar&#39;,   // how to use this component in HTML<br>  templateUrl: &#39;./navbar.component.html&#39;,<br>  styleUrls: [&#39;./navbar.component.css&#39;]<br>})<br>export class NavbarComponent {<br>  title = &#39;My App Navbar&#39;;<br>}</pre><h4>3. Templates</h4><p>Templates in Angular are <strong>HTML files enhanced with Angular features</strong>. They allow you to dynamically display data and respond to user actions.</p><ul><li><strong>Directives</strong> are special instructions inside templates:</li><li>*ngIf → conditionally display elements</li><li>*ngFor → loop through arrays to create elements</li></ul><p>Example:</p><pre>&lt;ul&gt;<br>  &lt;li *ngFor=&quot;let item of items&quot;&gt;{{ item }}&lt;/li&gt;<br>&lt;/ul&gt;<br><br>&lt;p *ngIf=&quot;items.length === 0&quot;&gt;No items found.&lt;/p&gt;</pre><p>Templates make your UI <strong>dynamic</strong> instead of static HTML.</p><h4>4. Data Binding</h4><p>Data binding connects your <strong>TypeScript code (logic)</strong> with your <strong>HTML template (view)</strong>. There are different types:</p><p><strong>i.Interpolation (one-way binding)</strong> — display data in the template:</p><ul><li>&lt;h1&gt;{{ title }}&lt;/h1&gt;</li></ul><p><strong>ii.Property binding</strong> — bind component data to element properties:</p><ul><li>&lt;img [src]=&quot;imageUrl&quot; /&gt;</li></ul><p><strong>iii.Event binding</strong> — call a function when an event happens:</p><ul><li>&lt;button (click)=&quot;onClick()&quot;&gt;Click Me&lt;/button&gt;</li></ul><p><strong>iv.Two-way binding</strong> — keep input and component data in sync using[(ngModel)]:</p><p>&lt;input [(ngModel)]=&quot;username&quot; /&gt; &lt;p&gt;Hello, {{ username }}&lt;/p&gt;</p><p>Data binding is <strong>what makes Angular interactive</strong> changes in your data automatically update the UI, and user actions can update your data.]</p><h3>What’s Next for Me?</h3><p>Right now, I’m still learning. My next steps are:</p><ul><li>Exploring <strong>Angular Routing</strong> (navigating between pages)</li><li>Understanding <strong>Forms</strong> (template-driven and reactive forms)</li><li>Connecting Angular with a backend API</li></ul><p>Learning Angular felt overwhelming at first because of its structure and terminology. But once I started with the basics components, templates, and data binding ,it became much clearer.</p><p>This blog is my way of documenting what I’m learning. If you’re also starting out with Angular, I hope this helps you too. And if you’re already an Angular pro, I’d love to hear your tips.</p><p>If you found this helpful, consider<strong> following me on Medium</strong> for more tech explorations.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c735f2ff9e1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From Windows to Ubuntu: My Journey with a New Operating System]]></title>
            <link>https://medium.com/@sajahanmasma/from-windows-to-ubuntu-my-journey-with-a-new-operating-system-1751299b61b7?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/1751299b61b7</guid>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Tue, 19 Aug 2025 10:01:36 GMT</pubDate>
            <atom:updated>2025-08-19T10:01:36.592Z</atom:updated>
            <content:encoded><![CDATA[<p>For most of my academic journey, I relied entirely on <strong>Windows</strong>. It was the only operating system I knew, and I never had any hands-on experience with anything else. Everything from assignments to coding projects was done within the comfort of Windows.</p><p>That changed when I started my <strong>undergraduate research</strong>. My domain is <strong>Software Defined Networking (SDN)</strong>, and many of the tools and simulations required for SDN are best supported on <strong>Linux-based systems</strong>. That’s when I decided to try <strong>Ubuntu</strong> for the first time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9_tyWV47L8njXxhHkXtxWw.png" /></figure><h3>First Encounter with Ubuntu</h3><p>At first, the switch felt intimidating. Unlike Windows, Ubuntu required me to get familiar with <strong>Linux commands</strong>. However, as I kept working on my research experiments, I realized how powerful and efficient Ubuntu was. Running network simulations, configuring environments, and managing resources became much smoother.</p><h3>Using Ubuntu in My Internship</h3><p>When I started my internship as a <strong>Front-end Developer</strong>, I continued using the same laptop with Ubuntu. It was exciting to see how Ubuntu supported not just research work but also software development. Working with code editors, version control, and project setups felt smooth and reliable.</p><h3><strong>Benefits I Experienced with Ubuntu</strong></h3><ol><li><strong>Better Performance</strong><br> Ubuntu felt lighter and faster than Windows. Even when running multiple processes, my laptop worked smoothly without slowing down.</li><li><strong>Developer-Friendly Environment</strong><br> Installing tools, managing dependencies, and using Git became much more efficient. The package manager (APT) saved me so much time compared to downloading and installing software manually.</li><li><strong>Power of the Command Line</strong><br> At first, commands felt difficult. But once I got used to them, I realized they made tasks faster and more flexible compared to clicking through menus.</li><li><strong>Stability for Research Work</strong><br> Running simulations for SDN required a stable environment, and Ubuntu provided exactly that. I didn’t face unnecessary crashes or slowdowns.</li><li><strong>Learning Opportunity</strong><br> Using Ubuntu gave me practical exposure to Linux, which is an important skill for anyone in tech. It pushed me out of my comfort zone and improved my confidence as a developer.</li></ol><p>What started as a requirement for my research turned into a <strong>great learning journey</strong>. Today, I not only know Windows but also have the capacity to <strong>work confidently with Ubuntu</strong>.</p><p>If you are a student or developer who has always relied on Windows, I encourage you to give Ubuntu a try. It might feel unfamiliar at first, but the benefits you gain will definitely be worth it.</p><p>If you found this helpful, consider<strong> following me on Medium</strong> for more tech explorations.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1751299b61b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TrueNAS: A Beginner’s Journey into Network Attached Storage (NAS)]]></title>
            <link>https://medium.com/@sajahanmasma/truenas-a-beginners-journey-into-network-attached-storage-nas-2e5fcaa97c25?source=rss-61f212668cef------2</link>
            <guid isPermaLink="false">https://medium.com/p/2e5fcaa97c25</guid>
            <dc:creator><![CDATA[Masma Sajahan]]></dc:creator>
            <pubDate>Tue, 29 Jul 2025 04:46:06 GMT</pubDate>
            <atom:updated>2025-07-29T04:46:06.423Z</atom:updated>
            <content:encoded><![CDATA[<p>I recently discovered a fascinating tool during my internship that changed the way I think about storage and file sharing which is <strong>TrueNAS</strong>.</p><p>One day at the office, I was given access to a small server loaded with movies, web series, and songs. With just a username and password, I could log in and stream or download anything over the local network. That server? It was powered by <strong>TrueNAS</strong> and that opened a whole new world to me.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M4iHbMvaGNWI96qkIRL9sw.png" /></figure><h3>What is TrueNAS?</h3><p><strong>TrueNAS</strong> is a free, open-source operating system that can turn almost any computer into a powerful file storage system, also known as a <strong>Network Attached Storage (NAS)</strong> server. It allows you to store, organize, share, and back up files over a network all from one central location.</p><p>Whether you’re an individual who wants to manage personal files like photos and videos, or part of a company that needs a secure way to store and share data between team members, TrueNAS offers a flexible and reliable solution for both.</p><p>It’s used by individuals, small businesses, and even enterprises to manage storage securely and efficiently.</p><p>There are two main versions:</p><ul><li><strong>TrueNAS CORE</strong> (free, open-source, based on FreeBSD)</li><li><strong>TrueNAS SCALE</strong> (Linux-based, supports containers and clustering) TrueNAS SCALE is now officially known as <strong>TrueNAS Community Edition.</strong></li></ul><h3><strong>How I Explored It?</strong></h3><p>Once I got curious, I visited<strong><em> </em></strong><a href="https://www.truenas.com/"><strong><em>truenas.com</em></strong></a><strong><em> </em></strong>and started reading. I found that it supports advanced features like:</p><ul><li>ZFS file system</li><li>Snapshots &amp; data protection</li><li>User management</li><li>Plugin support (like Plex for streaming)</li></ul><p>I also tried accessing it through the web UI and saw how well organized and clean the dashboard was.</p><h3>Why TrueNAS?</h3><h4>1. It’s Free and Open-Source (TrueNAS CORE)</h4><p>TrueNAS CORE doesn’t cost a single cent. You can download it from the official website and start using it right away.<br> Since it’s <strong>open-source</strong>, the code is freely available which means the community constantly improves it, and there’s no hidden lock-in like with some commercial tools.</p><h4>2. Runs on Old Hardware or Virtual Machines</h4><p>Have an old PC or laptop collecting dust? You can turn it into a NAS server with TrueNAS!<br> It’s very efficient and doesn’t need high-end specs even basic hardware can handle file storage, media streaming, and backups.</p><p>If you don’t want to use physical hardware, you can also install TrueNAS on a <strong>virtual machine (VM)</strong> using software like <strong>VirtualBox</strong> or <strong>VMware</strong>, which is great for testing and learning.</p><h4>3. Beginner-Friendly Web Interface</h4><p>One of the best parts is the <strong>user interface</strong>. TrueNAS offers a clean, easy-to-navigate web dashboard where you can:</p><ul><li>Manage storage and drives</li><li>Create user accounts</li><li>Set up shared folders (SMB, NFS)</li><li>Monitor system performance</li><li>Install plugins (like Plex, Nextcloud)</li></ul><p>No command-line skills required ,just open your browser and log in.</p><h4>4. Huge Community &amp; Support Resources</h4><p>There’s a strong, active TrueNAS community. You can:</p><ul><li>Ask questions in forums</li><li>Read documentation and tutorials</li><li>Watch videos on YouTube</li><li>Get advice from Reddit or Discord groups</li></ul><p>If you ever get stuck, chances are someone else has had the same issue and found a solution.</p><h4>5. A Great Learning Tool</h4><p>By using TrueNAS, you naturally start learning important tech skills:</p><ul><li>How storage drives and pools work (ZFS, RAID, etc.)</li><li>Basics of <strong>file systems</strong>, <strong>backups</strong>, and <strong>data redundancy</strong></li><li>Network protocols like <strong>SMB</strong>, <strong>NFS</strong>, and <strong>FTP</strong></li><li>Concepts in <strong>virtualization</strong>, <strong>containerization</strong>, and <strong>server management</strong></li></ul><p>This kind of hands-on experience is super valuable if you’re studying IT, working in tech, or just curious about how things work behind the scenes.</p><h3>Use Cases of TrueNAS</h3><p>1. At our office: Used for hosting shared media<br>2. At home: Can be used as a personal cloud (like Google Drive alternative)<br>3. For developers: Store code, databases, and backups<br>4. For media lovers: Stream your collection using Plex<br>5. For teams: Central storage with controlled access for users.</p><p>TrueNAS taught me that managing data doesn’t always require expensive cloud solutions sometimes, a small server in the corner of the room can be smarter.I’m planning to experiment more by setting it up in VirtualBox or on an old PC at home.</p><p>If you’re a tech enthusiast, intern, or someone who loves building things yourself ,I highly recommend checking out TrueNAS.</p><p>You can explore it here:<strong><em> </em></strong><a href="https://www.truenas.com/"><strong><em>https://www.truenas.com</em></strong></a></p><p>If you found this helpful, consider<strong> following me on Medium</strong> for more tech explorations.</p><p>👉<strong><em> </em></strong><a href="https://medium.com/@sajahanmasma"><strong><em>https://medium.com/@sajahanmasma</em></strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2e5fcaa97c25" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>