Skip to main content

Take a focused approach when you search for a new job

This is the general route chosen by youngsters when searching for a new job - 

  1. Shoot off resumes (sometimes tailored to different companies / roles)
  2. Seek referrals (sometimes from random strangers at LinkedIn)
  3. Start liking and commenting on posts from spammers at LinkedIn
  4. Update LinkedIn headline as 'Seeking new opportunities'
The first two approaches can be successful in a timely manner but the last two are literally wasted time. Another phenomenon that is often relied upon by many is Job Shopping. I made an attempt to underline the importance of focused efforts when it comes to job search. Check out my first post at LinkedIn - Job Shopping or Job Searching? Which is better for your Career?

Comments

Popular posts from this blog

Turning off a Dell Laptop Monitor: Keyboard shortcut(s)

I am someone who is particular about power savings and I don't leave appliances powered on when not in use. The same applies to computing devices - be it a smartphone or a PC/Laptop. I power off the desktop monitor when I step out for a tea break or hit Fn+F2 on my Lenovo laptop that turns off the display. Recently, I got a Dell Laptop and I was surprised to discover that Dell does not provide any shortcut to turn off the display. This led to some exploration and I found two ways to achieve that which are outlined below - 

Resolving INS-20802: Oracle Net Configuration Assistant failed error on Windows 10

I was all excited about the migration to Windows 10 until I had to install Oracle client 12.1.0.2 on it. The Oracle client installation used to fail miserably at the last stage with this error named INS-20802.

Nginx - Solution for 10060: A connection attempt failed because the connected party did not properly respond

I was in the process of setting up Nginx to serve as the reverse proxy for Nexus Repository Manager OSS. However, the Nexus repository started loading really slowly post this and used to repeatedly display disconnected and reconnected messages. The Nginx log file used to log the below error - <timestamp> [error] 3240#3632: *1 upstream timed out (10060: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond) while connecting to upstream, client: <ip address="">, server: <fqdn>, request: "GET /nexus HTTP/1.1", upstream: "http://[::1]:8081/nexus", host: "<fqdn>"