Employee to Entrepreneur: Taking Initiative is Key

Become an entrepreneur” if you are not already.

When I say ‘become’, it doesn’t mean you have to quit your job and start a new business. You just need to start thinking like “you are an entrepreneur”.


Take the ownership of what ever job assigned to you. That’s it. But, by just completing the tasks assigned to you will make you a good ’employee’ only. You have to think more, like – what value addition you can bring to the ‘environment’ and methods to implement it. No workplace is perfect, you have to make it perfect. Stop the blame games and tell people that it is their responsibility to make it perfect.

What will you do if you find paper cups are finished?…

– If you don’t have requirement specs, you prepare it.
– If you do not have a tester, you test it.
– Another developer is struggling with a bug, you try to help him.
– If the CFL lamp at the bathroom is not working, you notify it to the respective department.
– If the printer bay area is messy, you paste a notice “don’t waste paper’.
– When a new technology is introduced, you send that news to colleagues.
– …

Think about how you can make your environment perfect.

Once the employee-mindset is converted to an entrepreneur-mindset, you will start feeling changes. Better work environment, respect, promotion…


Safe format to save date/time in SQL Server

Below are safe/general formats which can be used with INSERT/UPDATE statements.

yyyy-mm-dd hh:mm:ss.mmm

Delimiters can be / OR – OR space. Examples:

  • 2001-05-21 10:15:50.192
  • 2001-05-21T10:15:50.192
  • 2001-05-21
  • 20010521 10:15:50.192
  • 2001/05/21

SQL example:

    testdate = ‘2001-05-21T10:15:50.192’
    id = 1   

WARNING: Use this only when you are sure your application IS NOT targeting any other databases (Oracle, MySQL etc.) other than SQL Server.

Please check my previous post as well.


How to save date/time from .NET to SQL Server?

Date format exceptions are wired headaches especially when you move your application from one server to another.

So, it is recommended:

  • Always persist date/time information as DateTime type in database
  • Never do custom formatting while passing date time information between different components. Use only .net DateTime types

  • Use custom formatting if required only when information is displayed in UI honoring the current UI culture info.

Below example shows a recommended practice:


How to test your application to see if your application is prone to Date/Time format issues?

Change regional settings in your computer (or server):

Note: Screenshots are based on Windows7, but steps are almost similar on most Windows based OS.

  1. Go to Control Panel –> Date and Time –> Change the time zone


  1. Click Change date and time


  1. Click Change calendar settings


You get two windows invoked when clicking:


  1. Change “Format:


  1. Click “Apply” button and close the window.
  2. Test your window/page/module where a date/time functionality is present.

If you get a wrong date/time format then in the “step-4: Format” OR If you get an application exception, then you can confirm that the developer did not follow safe coding practices.