You'll probably grow more gray hair trying to put out the moss fires. I
would advise against it

If you can take the stress, it would be a good way to further expand your
MOSS experience and skillset. Anytime you expand those, you expand your
potential earnings. Given the outlook on the job market, I personally would
rather be the MOSS swiss army knife. When it comes time to cut staff the guy who
can do it all, is more likely to still have a job.

Yes. Expand your problem set, and you will expand your knowledge... which
makes you more useful.

Besides, some of us actually enjoy playing fireman.

Currently, I'm working with SharePoint Admin and I see the stress it may cause.

SharePoint is a mixture of technologies that entails Windows Server (clustering,
NLB, DNS, AD, etc.), IIS (part of the first one), SQL Server, ASP.NET 3 and its
technologies such as WF, not to say integration with other Microsoft products
and other platforms.

When MOSS happens to have a problem, if you don't have a high level background
on all the technologies relevant to it, you may have headaches struggling to
detect what's wrong. An issue could be a database corruption, a corrupted
web.config, a by-design issue, something wrong with the network, the integration
with another platform does not occur properly and on and on.

If you like problem solving from an Admin perpective, you'll probably enjoy
searching for route causes of MOSS issues. On the contrary, if you enjoy
creation, personalization, adaptation, searching for workarounds, design
changes, Development is for you. The greatest of all thing, in my view, is to
have some experience on both sides, Admin and Dev, that's guarantee a valuable
vision of how the product works and it'll be more difficult for you to get stuck
in front of a problem, you'll have more up your leeves...

In the near future, I want to move on to SharePoint Dev by learning ASP.NET,
what I see as advantageous once it'll represent more opportunities in the
market, such as a "native" ASP.NET developer and as a SharePoint Developer,
being able to cover a wider range of the market.

Keep in mind though, developing  for MOSS also entails
other areas. You could crack open VS.Net 08 and start slinging some custom
workflows, you can really do some cool stuff in there and learn VS.Net doing
that. You also got custom event handlers, integration coding, etc.

The key is to make sure what you are doing is in demand. By learning the
Administration AND development sides, you become more and more qualified to move
into farm architecture, which is really cool. It also helps bring out the true
geek in all of us to play with all these other areas you mentioned (IIS, AD,
SQL, etc). Just rocks your mind getting into all of it.

By doing the admin side of things you tend to get more of an idea of the
impact of the development side as well. You can see what failing to dispose of
all your objects does, or when someone writes an excessive amount of loops into
their code, or some other fun stuff. You also get a good understanding of some
of the serious restrictions in the platform that you may not ever see if you are
not administering it and answering those calls. IMO, getting the admin
experience makes you an even better developer, and as I said before the more
bullet points on the resume, the better the employment opps.

My current job title is Sharepoint Admin/Developer

I have many years working with MS technology. I've actually been on both sides
of the fence. Developing and Administration.

My current Job posing requires that I know from top to bottom and inside out. As
an example; I'm currently developeing a web part, but last week  I built out an
ISA 2006 box for FBA/Extranet extensions.

For me it's more the challange than the money. But with Sharepoint becoming so
popular I suspect the pay rate would be better in the coming years. Espically if
you have the know-how.

Be warned though. You take on both sides you put in the extra work as well.
THAT's the down side for me. Weekends and evenings can be tied up for weeks at a
time.