Janardhan's insights
Home PageEmotional Intelligence book
  • About Insights
  • Janardhanpulivarthi.com
  • Books I've read
  • Bridge Engineering
    • code and books
    • Pier calculations
    • Suspension cables
    • Seismic coefficients
    • Shear check in pilecap
    • finance tasks
    • /bin/sh: 1: flex: not found
    • Biology animations
  • 🏕️SEASON 1
    • Social formulation
    • Words in Computer Science
    • Best use of internet
    • Products for sustainability
    • Tools for parents in digital age
    • Identify books in library
    • Control digital footprint
    • Search like a Pro
    • Dev productivity tips & tools
    • McKinsey, How it operates
    • Secrets, which ones to share
    • How to be Straightforward
    • Productive procrastination
    • Everyday things
    • Future of waste
    • Emotional weather
    • Money rules
    • Qualities of an Artist
    • Shameful Inconsistency
    • Mean Sea Level
    • Screenshot on Windows
    • Edu loan EMI calculation
    • Advanced Gmail tips
    • 24 hours before an exam
    • FAQ - git
    • Life skills by 25
    • Install Microsoft IIS server
    • gcloud commands hang
    • Google Cloud Data Engineering
    • Google Cloud Architect
    • find location of the command
    • JNI short tutorial
    • Civil distance
    • Being a friend to children
    • How to talk to a teenager
    • Resilience and relationship
    • 9 to 5 vs 4 hour workweek
    • Return on Investment
    • Alternative to PFA
    • Hand position for Ctrl key
    • Education: The Good Parts
    • Education: The proposed parts
    • On feeling stuck
    • How to read Financial news
    • What is in my hands
    • Mistakes founders do
    • On Self Worth
    • Emotional draining situations
    • Time
    • Hygiene
    • 5 Percent rule
    • How not to build a startup
    • How to lead a mediocre life
    • Day-to-day tips from extraordinary people
    • Who owns .com domain
    • Do not make bed first thing in morning
    • How to read kubernetes docs
    • Do not use morning alarm
  • ☀️Season 2
    • Practicing self care
    • Payment methods
    • Things to learn before MBA
    • Hum toh udd gaye
    • Time windows
    • How to quit a job emotionally
    • Journal on a year after quitting
    • Engineering the future
    • Build linux kernel
    • Important inventions
    • bashrc and bash_profile
    • $TERM
    • How Kubernetes pod get terminated
    • What data does google collect? when you search...
    • Should I build a personal brand?
    • The better startup ideas
    • Regex in Visual Studio Code
    • Few pieces to read before breakfast
    • core file
    • How to keep home for ambience
    • 🐬A story on repetition
    • Basic Unicode characters
    • Java operator precedence
    • Install latest maven on Ubuntu
    • Build ecosystems, not only products
  • ⛈️SEASON 3
  • ❄️Season 4
    • Be original
    • Change and Contingency
    • Read and write email
    • How to use Pomodoro
    • Humans and software
    • Saving money without money
    • Five skills for Civil Engineers
    • Que sera sera
    • Keep scrolling
    • Being unemployed
    • Friendship and modularity
    • Happy is not a default emotion
    • The missing piece in the online courses
    • How to build products
    • I am always tired
    • Instead company subscribe to user
    • Car electric or diesel ask google ngram viewer
    • Emotional currency and binge watching
    • ADR
  • Known Nokia 7.1 problems
  • Coursera-dl HTTPError: 400
  • Failed to retrieve identities from agent
  • Custom domain email
  • Qwiklabs tips and tricks
  • Online shopping rules
  • Protect a apt package from upgrade
  • Kubernetes troubleshooting guide
  • TOOLS
    • Lenovo Ideapad
    • Quantum - Holevo's theorem
    • Install VPP on Ubuntu
  • Phone camera slider
  • Physical internet infrastructure
  • 100 Days Of Code - Learning Java
  • Blogs I found interesting
  • 5g
    • 5G Glossary
    • Archive
      • Latex and gitbook
      • Japan Progress
      • Online buying guide
      • ఏవిధంగా కృషి చేయాలి?
      • Tech prediction 2030
      • Alphabet Financials
      • Apachecoin does not exist
      • non profits
      • What to Google Search
      • Resume tips
      • Discussion before marriage
      • Wi-Fi
      • How to read
      • Basic soil test
Powered by GitBook
On this page
  • Why original
  • How to be original
  • Practice

Was this helpful?

Edit on GitHub
  1. Season 4

Be original

Can we improve our originality with practice?

Let us explore the concept a bit, originality is often associated with things that are either made from scratch or made with solid input from the originator. The originator can verify their work contentedly and with certain familiarity. It does involve an amount of time and effort.

The things to which originality applies: People, thoughts, things, concepts.

Why original

Why do we need to be original? - Looking at this question more closely, why we don't need to be unoriginal. After a sense accomplishment with the objective at hand, we tend to think more clearly of its intricacies - the process, the properties, and the incomprehensible material that is inherent but discloses itself over time and with an involved effort.

Although being unoriginal feels okay and easy for a while, going through the work for more time makes work uninteresting, creates a fear of surprise and consequent lethargy.

Do I have a choice? - If the objective for one is to simplify life, the originality is the best path forward and a good deal compared to the loss done for one's emotional wellbeing and anxiety associated.

How to be original

Did you crosscheck something such as an answer paper, an email before sending, or a bit of intentional preparation for a presentation? - then you are being original.

Since the tasks mentioned above can be practiced so does the task of being original.

Practice

No.

Task

Practice

1.

Writing a presentation

  1. Have an outline.

  2. Stick to it, change often, rewrite/improve.

  3. Get a consensus before a presentation

2.

Email

  1. Do you need to send an email?

  2. Write the email body first as if you are writing to questions that this email should answer

  3. Write/rewrite subject based on the body

  4. Mention the expectation from the reader in clear lines.

3.

Code

  1. Do you need to write new or refactor existing?

  2. Add working code with a test case

  3. Improve code with involved test cases

4.

Processing emotions

  1. Have sometime for acknowledging (write it down on a piece of paper) certain feeling

  2. You will get the grip over that feeling after a few tries

  3. Take the help of a book or a friend to systematically approach

  4. Find the possible causes, circle around the seemingly relevant ones.

  5. Wait until you get mastery with time

PreviousBuild ecosystems, not only productsNextChange and Contingency

Last updated 3 years ago

Was this helpful?

For example,

❄️
Read and write email