GoodBye to .NET

  • Thread starter Thread starter Kelmen Wong
  • Start date Start date
K

Kelmen Wong

Though I been many spent many years onto M$ tech for development, this
will probably be the end of my pilgrim on it.

My employer is practically switching to J2EE now, as the last .NET
project give us some real nasty shits in the client production sys,
hence gone the faith of .NET in it.
 
My employer is practically switching to J2EE now, as the last .NET
project give us some real nasty shits in the client production sys,
hence gone the faith of .NET in it.
Click to expand...

Well, good luck with J2EE then!! Write once, debug everywhere - have
fun

Marc
================================================================
Marc Scheuner May The Source Be With You!
Bern, Switzerland m.scheuner(at)inova.ch
 
Though I been many spent many years onto M$ tech for development, this
will probably be the end of my pilgrim on it.

My employer is practically switching to J2EE now, as the last .NET
project give us some real nasty shits in the client production sys,
hence gone the faith of .NET in it.
Click to expand...

Which begs the question: What events conspired to bring on
disaster in the client production system that were not
exercised and detected in the project's testing environment?

Bottomline: if .NET was to blame it should have been
detected before the project went into production.

Both J2EE and .NET are huge and complex; naive solution
implementations will get you into trouble with both.
 
Just by chance was there a new employee on staff or some other advocate of
'other' solutions? A new project manager? A new vp?

Its not unrealistic to suggest the project may have been sabotaged. In fact,
its very common for developers or the slime they take their orders from act
subversively to sabotage projects for political objectives.
 
So developers are saboteurs and managers are slime? You must be an
arkeeteckt.
 
I'd agree that the boss should start looking for a better team, not a
better implementation technology, sorry mate ... :D

Angel
O:]
 
Hey. I learned it all the hard way and the facts are that many arkeeteckt's
can also be amongst the slimiest on the planet which is why I changed
careers only to discover how niave I was.

You are not suffering from Pollyanna syndrome are you? You do recognize that
such people and such behaviors do exist do you not?

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET (e-mail address removed)
URL http://www.metromilwaukee.com/clintongallagher/
 
Nah. :-)

clintonG said:
Hey. I learned it all the hard way and the facts are that many
arkeeteckt's
can also be amongst the slimiest on the planet which is why I changed
careers only to discover how niave I was.

You are not suffering from Pollyanna syndrome are you? You do recognize
that
such people and such behaviors do exist do you not?

--
<%= Clinton Gallagher, "Twice the Results -- Half the Cost"
Architectural & e-Business Consulting -- Software Development
NET (e-mail address removed)
URL http://www.metromilwaukee.com/clintongallagher/
Click to expand...
 
By all means, if a .NET Deployment failed it couldn't possibly be anything
other than Microsoft's fault. Like I always say, if you get a flat tire,
the best way to fix it is to flatten the other three.
 
Dateline and poor SDLC gave a lot of damn shits onto the developers,
the 3 main core engineers left the project looking for better
development vendor.

Screwed up prj mgmt produced screw up product. Worst is that I'm the
one being take over the leftover.

The fault is nothing totally on M$ (at few cases, they are). Just
wonder how lousy development company can bring in so much biz?
 
... that's just so typical, mate. I feel your pain. i'm at more or less the
same spot here as well :]

I suggest you [we] take a deep breath, and just keep going the best we can
.... shit happens all the time and, personally, I wouldn't give up my job
over it again.

Angel
O:]


Kelmen Wong said:
Dateline and poor SDLC gave a lot of damn shits onto the developers,
the 3 main core engineers left the project looking for better
development vendor.

Screwed up prj mgmt produced screw up product. Worst is that I'm the
one being take over the leftover.

The fault is nothing totally on M$ (at few cases, they are). Just
wonder how lousy development company can bring in so much biz?

"Angelos Karantzalis" <[email protected]> wrote in message
I'd agree that the boss should start looking for a better team, not a
better implementation technology, sorry mate ... :D

Angel
O:]
Click to expand...
Click to expand...
 
I certainly do mate, unfortunately. But that's no reason to blame a [any]
technology. It's the man, not the machine :]

Angel
O:]
 
Like others have said, it's never the equipment, it's always the rider
(oh wait, that's a mountain biking analogy). I find myself in peculiar
position in which I can empathize with both sides of this situation.
I have been Microsoft developer since 1995. I recently found myself
looking for work after my company succumbed to gross mismanagement. I took
up shop with a mentor of sorts who owned his own consultancy, the problem was
that he was a J2EE guy all the way. In years past, I'd come on board with
him in my spare time when there was only an MS solution, and he didn't want
to turn away from a potential relationship. My first big project with him,
was to team up with an MCP hosting Co. that dabbled in development to develop
a data warehouse. This was just a step on the way to getting a much larger
contract that was to be a Web Order Entry system in Websphere that tied back
to J.D. Edwards. With the contract secured, there were many architectural
decisions along the way, and there's an odd enough mix of technologies
between MS products and J2EE that I'm beginning to feel uniquely qualified to
speak on this subject, because I feel that I've let down my prejudices. On
one side, I have the MCP and on the other, the J2EE guy and they constantly
battle over which product camp best suits our objectives. IMO, it all boils
down to platforms, and in some cases how much a third party tool might cost.
For instance, I had been asked to develop a solution to convert an AS/400
spool file that had been stuffed into a BLOB in SQL2K over to a PDF. We went
from J2EE (scrapped because of Adobe's high price for LiveCycle), to VB
(Persits AspPDF - a great product BTW) back to J2EE (Open Source XML PDF
forms). Both the VB and Open Source J2EE solutions work great, it just so
happened that J2EE made more sense in this case and was worth the wasted
hours building the VB app for the lessons learned (the customer was aware of
and approved of our decision). To look at development as all or nothing when
it comes to this issue, is to start limiting your potential. I have worked
very hard at becoming as proficient in Java as I am in VB/C++ which hasn't
been easy since it gets in the way of life so much and would be so much
easier to just stick with what I already know. Both technologies have their
place, and technically speaking, both products make each other better.
Kelman, in your situation, I'd be leary. From your posts it sounds
like someone was successful in blaming the equipment, which suggests that
person is still around (I could very well be wrong). If that person is still
around, the next time he/she needs an excuse, the equipment one's already
been used, and if I'm right about this, that person will shift blame for
their next failure which may come your or your associates' way. Be careful.
 
I working out move onto DBA.

Whether who's this "blamer", nothing I will bother or can do anything
on it.
As someone mentioned, I tired of changing job. Its practically the
same everywhere.

Those capable and potential peoples already left. What left here, as
include myself are practically sucker or loser. May as well truly
become one of them, play some snaking once awhile to get on the life.
Lesser expectations lesser dissappoinment.
 
Back
Top