.NET is a pretty flower that smells bad.

topic posted Wed, October 25, 2006 - 10:13 AM by  Unsubscribed
just kidding. sort of.

has anyone experienced a situation similar to the following?:

i work for a state that shall remain nameless (hint: it's name rhymes with Bore-a-duh).

one of the bosses decided it would be cool if all our apps were rewritten in C# and we used .NET and blah blah blah.
ok. that's fine. _finally_ we'll be able to ditch powerbuilder 6.5 and do some fun new stuff.

wait.

microsoft's framework isn't good enough for him. he'd be the envy of all the other bosses if he got his pets to develop a whole 'nother framework to sit between .NET and the non-pet programmers, then he'd be able to suck every last drop of fun out of the programming life of his employees.

so he had it done.

and now we are sort of using .NET but not really so much. we're using C# and our own special (special as in 'short bus', not special as in 'cool') framework.

anyone else had something like this pulled on them?


posted by:
Unsubscribed
  • Re: .NET is a pretty flower that smells bad.

    Wed, October 25, 2006 - 2:54 PM
    Tell him it would really be cool if he made everyone do everything from a web page written in Java. :)
    • Unsu...
       

      Re: .NET is a pretty flower that smells bad.

      Thu, October 26, 2006 - 8:03 AM
      if he read in an article that 'all the k-rad companies are doing it' he'd probably have us do it. he's an ass. actually, he _was_ an ass. elections are coming up, and so all the bosses are scurrying around, changing agencies, trying to make sure they don't get hit by any fallout when the administration changes. He went to another deptartment. education, i think.

      that's what these guys do - show up, jack stuff up, move some people around, start some stupid projects, then go somewhere else before the damage tally is available.

      pssssh.
      • Re: .NET is a pretty flower that smells bad.

        Mon, November 6, 2006 - 3:20 PM
        I work for a health tip website, and they made me write a bunch of com wrappers for some horsehit and also use a crapload of classic asp.net. To add insult to injury, they write in VB.NET. Its like having the choice of Salma Hayek (C#) and a dog turd (VB.NET) and choosing to breed with the dog turd.

        Ah well.
        • Unsu...
           

          Re: .NET is a pretty flower that smells bad.

          Tue, November 7, 2006 - 5:54 AM
          heheahahaha!

          why? why don't they just let programmers program? our agency used to be pretty independent - we kept our own severs, selected our own database brands, established our own standards, &c. yes, it was chaos, but it was managed chaos. we wrote good software, our systems went up and stayed up, and it was fun. our users didn't care what was behind the curtain. when an old timer left, he wrote some documentation, we picked his brain for awhile, and since it was a good place to work and we were all friends, we could call him any time for info.

          they rolled us into another department four years ago, came down with all these best practices, ISDM stuff (www.myflorida.com/myflorida/s...m/index.html ) and it's now a mess, morale is in the pits, and quality is even lower. man but i can do me some paperwork though! our failures are well documented! heh.
          • Re: .NET is a pretty flower that smells bad.

            Wed, November 8, 2006 - 7:20 AM
            I am in pretty much the same situation. We currenlty have about 200 developers, of which there are about 80% .net and about 75% of the .net coders are vb.net. We have an arch group that thinks they know what they are doing (but are actually a java-biggot filled, anti MS group) that set "standards" for our place. They don't have a clue about VB.net, but because c# looks like java, they are forcing a c# standard. They are also pushing a .net ui, java middle tear paradigm for future projects. Morale around here is dropping fast, we have already started loosing people.
            The thing that concerns me here is that a lot of vb coders are not sharp enough to be able to handle some of the more powerful (and in my opinion unnecescary functions) in c#. VB has always pretty much protected us from someone messing with the internals.
            But, the main thing, as you state it, is "Why don't they just let programmers program". The original .Net vision was let people use the language they are the most comfortable with--that is why there are more than 20 .net compliant languages.
            This place used to be fun, too, but not anymore. Hidden agendas really suck!!!