switching from .net developing to pure sql developing

As C# developer for web aplications we follow simple web forms model. Never used interface. The only place we used inheritance is in creating an abstract accessor class. I was a coding machine writing data access code over and over again in both C# and SQL. I'm working on to get out from such monkey's job and try to do better programming

I got offer as SQL developer job with 30% hike which is pure SQL developing. In that company they are using their own tool for generating UI(front end). So no chance to work on any programming language other than SQL.

Basically I am curious to learn and explore things. In 2 or 3 years I want to switch back to .net programming,but there is no possibility for that in the offering company.

I am afraid that if I take this offer for pay hike, Could I found programming job(C# , java or any .net/jvm platform programming) in future by learning and updating knowledge on any c# or java programming?

I observed the following 2 factors for job change:

Need to exit the monkey-style coding in present company
Need for 30% hike at least

Both are normal & programmers used to go through this stage.

I see the following problems going with your new sql-only job:

Lock up in SQL world
Loosing of .Net skills
Re-problem of monkey-sql-coding in future

Although, I cannot completely agree about creating UI dynamically, as there will be custom validations code, formatting code requirements. Even SharePoint is generating UI & Database dynamically, still there exists custom solution requirement.

Considering all the cases, I recommend you the following:

Study one .Net certification, there you will learn interesting things that make you ENJOY current job
Learn Entity Framework, Reflection, Design Patterns so you get better quality code developed, earn satisfaction & save much time.. above all increase in CAREER-VALUE
Ask your current company to use the above quality style of development, instead of traditional-monkey style, Add hike requirement too
If they do not agree, you are already ready to change company, with the above skills you can get 30 to 50% hike in .Net arena itself.

In this 1, 2 efforts of around 3 months, you will get rid of troublesome work, retain .Net development, adapt quality methods, gain certification, gain hike as well.

If you do not wanted this hard ship way, then you can find another .Net Job with Hike. :)

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

Jean Paul13y ago
Accepted answer
I observed the following 2 factors for job change:
- Need to exit the monkey-style coding in present company
- Need for 30% hike at least
Both are normal & programmers used to go through this stage.

I see the following problems going with your new sql-only job:
1. Lock up in SQL world
2. Loosing of .Net skills
3. Re-problem of monkey-sql-coding in future
Although, I cannot completely agree about creating UI dynamically, as there will be custom validations code, formatting code requirements. Even SharePoint is generating UI & Database dynamically, still there exists custom solution requirement.

Considering all the cases, I recommend you the following:
1. Study one .Net certification, there you will learn interesting things that make you ENJOY current job
2. Learn Entity Framework, Reflection, Design Patterns so you get better quality code developed, earn satisfaction & save much time.. above all increase in CAREER-VALUE
3. Ask your current company to use the above quality style of development, instead of traditional-monkey style, Add hike requirement too
4. If they do not agree, you are already ready to change company, with the above skills you can get 30 to 50% hike in .Net arena itself.
In this 1, 2 efforts of around 3 months, you will get rid of troublesome work, retain .Net development, adapt quality methods, gain certification, gain hike as well.

If you do not wanted this hard ship way, then you can find another .Net Job with Hike. :)