Total Pageviews

Tuesday, April 18, 2023

7 signs of a weak mindset

  1.  Apologizing for everything
  2. Constantly defensive
  3. Afraid of social situations
  4. Allowing critics to control
  5. Complaining more than working
  6. Afraid of other people's opinion
  7. Never express the true feel

Saturday, April 15, 2023

PII data handling & startups

 Handling personally identifiable information (PII) data can be a significant challenge for startups, as it requires a high level of security and privacy protection. Here are some challenges that startups may face when handling PII data:

  1. Compliance with regulations: Startups must comply with various regulations such as the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA), which require businesses to obtain consent from individuals before collecting, processing, or storing their PII data. These regulations also mandate certain security measures that must be in place to protect PII data from unauthorized access.

  2. Data breaches: PII data breaches can have serious consequences for startups, including legal liabilities, loss of reputation, and financial damage. Startups must implement robust security measures such as encryption, access controls, and monitoring systems to prevent data breaches.

  3. Limited resources: Startups may have limited resources to allocate to data protection and security measures. This can make it difficult to implement best practices such as regular security audits, security training for employees, and secure data storage.

  4. Managing third-party vendors: Startups may need to rely on third-party vendors for various services such as cloud storage, data analytics, and marketing. It is essential to ensure that these vendors comply with data protection regulations and have appropriate security measures in place.

  5. Data subject requests: Individuals have the right to access, delete, or modify their PII data under certain circumstances. Startups must have processes in place to handle these requests and ensure that they are fulfilled within the required timeframes.

Overall, startups must prioritize data protection and security when handling PII data to maintain the trust of their customers and comply with regulatory requirements.


Here are some common mistakes that startups make when handling PII data:

  1. Not obtaining proper consent: Startups may collect PII data without obtaining proper consent from individuals. This can lead to legal liabilities and loss of trust from customers. Startups must ensure that they obtain explicit consent from individuals before collecting and processing their PII data.

  2. Inadequate security measures: Startups may fail to implement adequate security measures to protect PII data from unauthorized access, data breaches, and other security risks. This can result in legal liabilities, reputational damage, and loss of customer trust. Startups must implement robust security measures such as encryption, access controls, and monitoring systems to protect PII data.

  3. Failure to comply with regulations: Startups may fail to comply with data protection regulations such as the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA). This can result in legal liabilities, financial penalties, and loss of customer trust. Startups must ensure that they comply with all relevant regulations when handling PII data.

  4. Lack of transparency: Startups may fail to be transparent about how they collect, process, and use PII data. This can result in loss of trust from customers who may feel that their data is being misused or mishandled. Startups must be transparent about their data practices and provide clear and concise privacy policies to customers.

  5. Over-collecting data: Startups may collect more PII data than they need, which can increase the risk of data breaches and other security risks. Startups must collect only the data that is necessary to provide their services and implement processes to securely delete or anonymize PII data that is no longer needed.

Overall, startups must be vigilant when handling PII data and avoid these common mistakes to maintain the trust of their customers and comply with regulatory requirements

Inadequate security measures are one of the most common mistakes that startups make when handling PII data. Inadequate security measures can lead to unauthorized access, data breaches, and other security risks that can result in legal liabilities, reputational damage, and loss of customer trust. Here are some examples of inadequate security measures:

  1. Weak passwords: Startups may use weak passwords or fail to enforce password policies that require employees to use strong passwords. Weak passwords are easy to guess or hack, and they can provide unauthorized access to PII data.

  2. Lack of encryption: Startups may fail to encrypt PII data, which can result in unauthorized access to sensitive information. Encryption is the process of encoding data so that only authorized users can access it. Startups must use encryption to protect PII data both in transit and at rest.

  3. Insufficient access controls: Startups may fail to implement access controls to limit access to PII data to authorized users. Access controls can include password protection, two-factor authentication, and role-based access control. Startups must implement access controls to prevent unauthorized access to PII data.

  4. Lack of monitoring: Startups may fail to monitor their systems for security breaches and suspicious activity. Monitoring can help detect security breaches and other security risks in real-time. Startups must implement monitoring systems to detect and respond to security breaches and other security risks.

  5. Inadequate employee training: Startups may fail to provide adequate training to employees on data protection and security. Employees are often the weakest link in the security chain, and they can inadvertently expose PII data to security risks. Startups must provide regular training to employees on data protection and security best practices.

Overall, startups must implement robust security measures to protect PII data from unauthorized access, data breaches, and other security risks. Inadequate security measures can have serious consequences for startups, including legal liabilities, reputational damage, and loss of customer trust.

Internal employees can pose a significant security risk to startups when handling PII data. While not all employees will intentionally engage in suspicious activity, startups must have processes in place to detect and respond to any suspicious activity by internal employees. Here are some examples of suspicious activity by internal employees:

  1. Accessing PII data without authorization: Employees may access PII data without authorization for various reasons, such as personal gain or curiosity. Startups must implement access controls to limit access to PII data to authorized employees, and monitor access to detect any unauthorized access.

  2. Sharing PII data with unauthorized third parties: Employees may share PII data with unauthorized third parties, such as friends or family members, for personal gain or other reasons. Startups must implement processes to prevent unauthorized sharing of PII data, such as monitoring employee communications and implementing access controls to limit access to PII data.

  3. Deleting or modifying PII data without authorization: Employees may delete or modify PII data without authorization, which can result in data loss or unauthorized changes to sensitive information. Startups must implement audit logs to track any changes to PII data and limit the ability of employees to delete or modify data.

  4. Installing unauthorized software or hardware: Employees may install unauthorized software or hardware on company devices, which can result in security vulnerabilities and unauthorized access to PII data. Startups must implement policies and procedures to prevent employees from installing unauthorized software or hardware on company devices.

  5. Failing to follow data protection and security policies: Employees may fail to follow data protection and security policies, such as using weak passwords or failing to encrypt PII data. Startups must provide regular training to employees on data protection and security best practices and implement policies to enforce compliance with these policies.

Overall, startups must implement processes to detect and respond to any suspicious activity by internal employees when handling PII data. These processes can include access controls, monitoring, audit logs, training, and policies and procedures to enforce compliance with data protection and security policies

द्वादश ज्योतिर्लिंग स्तोत्रम्


SanskritTranslation
सौराष्ट्रे सोमनाथं च श्रीशैले मल्लिकार्जुनम्।Somnath in Saurashtra and Sri Mallikarjuna in Srisailam;
उज्जयिन्यां महाकालमोङ्कारममलेश्वरम्॥Mahakala (Mahakaleshwara) in Ujjain, Omkareshwara in (Khandwa);
वैद्यनाथम् चिताभूमो च डाकिन्यां भीमशङ्करम्।Baidyanath in Chitha Bhumi and Bhimashankara in Dakinya;
सेतुबन्धे तु रामेशं नागेशं दारुकावने॥Ramesham (Rameshwara) in Sethubandh, (Nagesham) and Nageshwar Jyotirling Dwarka or Naganath in Daruka-Vana;
वाराणस्यां तु विश्वेशं त्र्यम्बकं गौतमीतटे।Vishwesham (Vishweshwara) in Varanasi, Tryambakam (Trayambakeshwara) at bank of the river Gautami (Godavari);
हिमालये तु केदारं घुश्मेशं च शिवालये॥Kedar (Kedarnath) in the Himalayas and Ghushmesh in Shivalay , (Grishneshwar / Ghushmeshwar )
एतानि ज्योतिर्लिङ्गानि सायं प्रातः पठेन्नरः।One who recites these jyotirlingas every evening and morning
सप्तजन्मकृतं पापं स्मरणेन विनश्यति॥is relieved of all sins committed in past seven lives.
एतेषां दर्शनादेव पातकं नैव तिष्ठति।One who visits these, gets all his wishes fulfilled
कर्मक्षयो भवेत्तस्य यस्य तुष्टो महेश्वराः॥:and one's karma gets eliminated as Maheshwara gets satisfied to the worship


  1. Somnath - Saurashtra (Gujarat)
  2. Mallikarjuna - Srisailam (Andhra Pradesh)
  3. Mahakala (Mahakaleshwara) - Ujjain (Madhya Pradesh)
  4. Omkareshwara - Khandwa near Indore (Madhya Pradesh)
  5. Baidyanath - Deoghar (Jharkhand)
  6. Bhimashankara  - Dakinya (Maharashtra)
  7. Ramesham (Rameshwara) - Sethubandh (TamilNadu)
  8. Nageshwar Jyotirling Dwarka or Naganath - Daruka-Vana (Gujarat) 
  9. Vishwesham (Vishweshwara) -  Varanasi (Uttar Pradesh)
  10. Tryambakam (Trayambakeshwara) at bank of the river Gautami (Godavari) - Nasik (Maharashtra)
  11. Kedar (Kedarnath) -  Himalayas Rudraprayag (Uttrakhand)
  12. Ghushmesh (Grishneshwar / Ghushmeshwar) - Shivalay (Maharashtra)

Andhra Pradesh - 1 (2.Mallikarjuna)
Gujarat - 2 (1. Somnath, 8.Nageshwar)
Jharkhand - 1 (5.Baidyanath)
Madhya Pradesh - 2 (3.Mahakala, 4.Omkareshwara)
Maharashtra - 3 (6.Bhimashankara, 10.Trayambakeshwara, 12.Grishneshwar)
TamilNadu - 1 (7.Rameshwara)
Uttrakhand - 1 (11.Kedarnath)
Uttar Pradesh - 1 (9.Vishweshwara)

Saturday, April 8, 2023

Advik

 Advik is a Sanskrit name that means "unique" or "singular." In Hindu mythology, the name Advik is associated with Lord Shiva, one of the primary deities in the Hindu pantheon.

People who bear the name Advik are often thought to possess unique characteristics that set them apart from others. They may be known for their creativity, individuality, and independent thinking. These traits can be an asset in many areas of life, such as the arts, business, and leadership.

Those named Advik may also have a strong connection to their Indian heritage, as the name is rooted in Sanskrit language and culture. However, the name has become increasingly popular in other parts of the world as well, as more parents seek out distinctive and meaningful names for their children.

Overall, the name Advik is associated with strength, individuality, and uniqueness, making it a popular choice for parents looking for a name that stands out from the crowd.

Government initiatives for the Startups

Made a list of government initiatives for the Startups. Hope this helps the early stage founders who are searching those sticks to float-


  1. Startup India: A flagship initiative of the Government of India to promote entrepreneurship and innovation. The program offers various benefits such as tax exemptions, funding, and mentorship to startups.
  2. Pradhan Mantri Mudra Yojana: A scheme that provides loans to micro and small enterprises, including startups, to support their growth and expansion.
  3. Stand-Up India: A scheme that provides bank loans between Rs. 10 lakhs and Rs. 1 crore to at least one scheduled caste or scheduled tribe borrower and at least one woman borrower per bank branch for setting up a greenfield enterprise.
  4. Atal Innovation Mission: An initiative to promote innovation and entrepreneurship in India, particularly among students, through various programs such as Atal Tinkering Labs, Atal Incubation Centers, and Atal Community Innovation Centers.
  5. Pradhan Mantri Yuva Yojana: A scheme aimed at promoting entrepreneurship education and training among young people in the age group of 18-29 years.
  6. National Entrepreneurship Awards: An annual awards program to recognize and reward outstanding entrepreneurs and ecosystem builders in India.
  7. Credit Guarantee Fund Scheme for Startups: A scheme that provides collateral-free loans to startups through banks and other financial institutions.
  8. NIDHI (National Initiative for Developing and Harnessing Innovations): A program that provides various support services to startups such as seed funding, incubation, and mentoring.
  9. Biotechnology Ignition Grant: A scheme that provides financial assistance to startups in the biotechnology sector to support their research and development activities.
  10. Electronics Development Fund: A scheme that provides funding and support to startups in the electronics and IT hardware sector.

Reference - https://www.linkedin.com/posts/vijayrathorenucleus_startups-governmentinitiatives-founders-activity-7050111356175286273-yNFz?utm_source=share&utm_medium=member_desktop

Thursday, April 6, 2023

Plan to learn Go!

 Plan to learn Go!

  1. Start with the basics: Begin by familiarizing yourself with the basic syntax and structures of the Go language. You can start with the official Go tutorial available at https://tour.golang.org/welcome/1.

  2. Read books and articles: There are many good books and articles available on Go. "The Go Programming Language" by Alan A. A. Donovan and Brian W. Kernighan is a great place to start. It covers everything from basic syntax to advanced topics.

  3. Practice: Practice makes perfect. Start with small, simple programs and gradually work your way up to more complex ones. There are many online resources available for practicing Go, including coding challenges and exercises.

  4. Join the community: There is a thriving community of Go developers who are always happy to help new learners. Join online forums, such as the official Go forum or Reddit's r/golang, and ask questions.

  5. Build projects: Once you have a good understanding of the language, start building projects. Think of something you'd like to build and work on it. It could be a small utility, a web app, or anything else that interests you.

  6. Attend meetups and conferences: Attend local Go meetups and conferences. This will give you the opportunity to meet other developers and learn about new developments in the Go community.

  7. Stay up-to-date: Keep up-to-date with the latest developments in Go. Follow the official Go blog and other blogs and websites dedicated to Go. Stay informed about new tools, libraries, and frameworks that are being developed.

By following these steps, you should be well on your way to becoming a proficient Go developer. Good luck!

Tech design document

 A tech design document is a comprehensive document that outlines the technical architecture and design of a software or technology project. The purpose of the document is to provide a clear understanding of the project's technical requirements, design, and implementation details to all stakeholders involved in the project, including developers, architects, product managers, and other project team members.

Here are some key elements that a tech design document should include:

  1. Overview: The document should start with an executive summary that provides an overview of the project, its purpose, and its intended audience. This section should be written in non-technical language and should explain the benefits of the project to stakeholders.

  2. Technical Architecture: This section should provide an overview of the technical architecture of the project, including hardware and software requirements, data flow diagrams, and system design.

  3. Design Considerations: This section should describe the key design decisions that have been made for the project, such as the choice of programming languages, frameworks, and libraries. It should also include details on the chosen architecture patterns and design principles.

  4. Data Model: This section should describe the data model used in the project, including the entities and relationships between them. It should also include details on the database schema and any relevant data validation rules.

  5. API Design: This section should describe the API design, including the endpoints, request/response formats, authentication and authorization mechanisms, and any rate limiting or throttling rules.

  6. Implementation Details: This section should describe the implementation details of the project, including coding standards, version control, testing methodology, deployment processes, and any relevant third-party integrations.

  7. Scalability and Performance: This section should describe the scalability and performance considerations for the project, including the expected user load and any relevant performance testing data.

  8. Security: This section should describe the security measures taken for the project, including encryption, access controls, and any other relevant security features.

  9. Maintenance and Support: This section should describe the maintenance and support plan for the project, including any ongoing support or maintenance required, and any relevant SLAs.

Overall, a tech design document should be detailed and comprehensive, and provide a clear understanding of the technical architecture and design of the project. It should be updated as the project progresses, and should be easily accessible to all project stakeholders