Author Topic: Second chance in IT?  (Read 446 times)

JavaMouse

  • Trusted Member
  • Wise Sage
  • ******
  • Posts: 1626
    • View Profile
Re: Second chance in IT?
« Reply #15 on: July 30, 2010, 10:01:52 pm »
Or a more realistic example - I am proposing to create Java applet for a public facing web site.
I know I could to a great job. The applet will work ... just a small glitch. Every client of this company must have the Java Web Start installed. That's not a problem right ?
Agreed; I've seen a few niche markets for applets, all for internal company use. Sometimes I see them used for science demos online (not a money-making proposition, although I wonder, if you had a giant science demo site loaded with applets, if it wouldn't generate ad money). Just about nowhere else though.

lorb

  • Trusted Member
  • Guru
  • ******
  • Posts: 314
    • View Profile
Re: Second chance in IT?
« Reply #16 on: July 30, 2010, 10:12:30 pm »
I am basically opposed to Applets unless it's something like a chess program that runs over the internet - only cool app I ever saw that used one.  Just because I have a problem with the word obsolete doesn't mean I think applets are okay! (even if/though they probably are).   ;D

Peter Gibbons

  • Guest
Re: Second chance in IT?
« Reply #17 on: July 30, 2010, 10:33:57 pm »
Quote
they bought an 'upgrade'  - this DOS system.  YES, it happens!!

Sure it could happen.

I would say that writing office type applications in assembler is obsolete but Michael Riddle ( the original creator or AutoCAD ) was still developing his flagship product FastCAD in assembler until few years ago when finally switched to C++:

http://www.michaelriddle.com/

Quote
The other tool that needs understanding is just what our compilers do with our code, and that means understanding assembler. I wrote our company’s FastCAD product entirely in x86 assembler. I actually started with the old Selector:offset horror, which I recommend everyone ignore as an historical bubonic plague. Once the 80386 and WIN32 supported the “flat memory model”, assembler became an order of magnitude (or more) easier.

I don’t recommend that you write programs in assembler. Modern compilers are efficient enough to please even me, and I no longer create in assembler. But the insight it gives me helps almost every day. It lets me judge the cost of various techniques used in C++. I learned that switch statements are no longer awful, since they are now implemented in optimized release code as a very efficient binary search. In fact, the more different cases, the more efficient such a test is. I learned that multiple inheritance is a real horror and can kill efficiency, and also lead to issues of functional duplication that can hide bugs.

...

So what were we arguing again?

You did make the switch from DOS to Windows - right? Why?
Your chess works under DOS. You could use Word Perfect to write you letters and Lotus 123 ...
...

So why then not make the switch to Mobile computing? Even though smart phones today are much more powerful than the DOS boxes we used in the past - it's still very important to know how to conserve memory and write tight code.

I am sorry. You mentioned a few days ago that you had trouble landing contract or full time job.
So what I am trying to say - don't fight the market forces. Go with the flow.

If you are completely not interested in mobile development - you could find some other area where you could use your existing skills with just a few weeks of retraining the you could do on your own.

This assumes that you are not completely burned out by IT work and still have some interest in learning new things in that area.


The Gorn

  • Your agonizer, please. And be sure to keep the batteries charged!
  • Trusted Member
  • Wise Sage
  • ******
  • Posts: 13730
  • Gornix user
    • View Profile
Residual Value vs Economic Activity
« Reply #18 on: July 30, 2010, 11:42:51 pm »
There is a bone of contention latent in this discussion.

Lorb argues that the value and functionality of the applications and the installed base does not decline and in fact remains substantial.

I agree. However, that is only part of the picture.

What is important in earning a living or running a business is what someone will actually pay you to make. Today, and going forward. Yesterday just doesn't matter. It's done. It's been delivered. That DOS system that runs a factory was delivered yesterday (or in past years.) There may be funding available to pay a guy or two to maintain and improve it, but there are no more installations. Nothing new. Just bandaging the old.

Just like a Model T.

Obsolescence happens for three principle reasons, as I see it:

1) Functional obsolescence. Example - 300 baud modems. Functional and useful, but not competitive. Simply nowhere as good as modern equivalents for data communication. And in fact, somewhat wasteful of resources (IE, a modem requires an analog phone connection using copper wire.) Another example: iron waste pipe. PVC is the only waste pipe used in plumbing today. Easier to work, to work with, to cut, and to install. Iron pipe required some gunk called oakum for connections, and was a specialized thing to deal with. Today you use PVC cement in a can with a brush for PVC pipe.

2) Obsolescence due to sheer boredom. Clothing, housing and auto fashions (generally.) New designs must come out in order to induce the customer to buy something.

3) Competitive obsolescence. Technology advancements for the purpose of refreshing existing markets or making new markets. DOS --> Windows, for instance. And in fact, this describes most of the computer and IT industry.

No matter how useful DOS still is in existing applications still in use, all economic activity that is associated with it is stagnant and is at a minimal survival level today.

The one single constant that underlies all of IT is competitive obsolescence. If you didn't have competitive obsolescence, you would not have had mainframes, then timesharing, then PCs, then whatever else.

I think competitive obsolescence is in a different category entirely than fashion/boredom obsolescence or functional obsolescence. It borrows traits of both, though.

The difference is that the competitive obsolescence is a strong innovator's way of gaining or maintaining market share. And, competitive obsolescence tends to make the old stuff not only obsolete, but perhaps even impractical, costly and/or painful to keep maintain, due to ... obsolescence itself (incompatibility.)

There are many old Model Ts and Model As giving their owner-collectors great pleasure, I'm sure. But they are not a source of economic vitality, except in a tiny way if you run a vintage car shop or you're a collector-merchant.

In like manner there are quite a few businesses and maybe even home users still running DOS and Windows 3.1 and Commodore 64s. In the same way, none command any economic opportunity.

If you want to be where the economic activity is, you have to go there... that now means the newest technology. This has always been the case but in the current tight economy this effect has been exaggerated.

Me - I am still writing C++. How long has it been in wide use, 20 years? So, I'm a hypocrite.  8) Rather, I blundered into an intersection between what I know already, and a direction that my client wants to proceed in next. I use old techniques to develop new products for a current and future need.

If you could do this kind of thing with DOS or 16 bit Windows then you could stay on using those technologies...
« Last Edit: July 31, 2010, 12:14:03 am by G0ddard B0lt »
Gornix is protected by the GPL. *

* Gorn Public License. Duplication by inferior sentient species prohibited.


The Gorn

  • Your agonizer, please. And be sure to keep the batteries charged!
  • Trusted Member
  • Wise Sage
  • ******
  • Posts: 13730
  • Gornix user
    • View Profile
Staying Relevant and Recycling Skills
« Reply #19 on: July 30, 2010, 11:52:10 pm »
Everything Lorb says on the topic of competing against younglings for scraps of contracts in the newer technologies is mostly true. Yes, it's a kid's game. Not even a young man's game. Chasing neato tech for its own sake is an exercise for 18 to 23 year olds. (That's the smart ones. The dumb 18 to 23 year olds watch "Jersey Shore" or something... )

The real issue, to continue with my comments about economic activity vs residual value, is what anyone is willing to pay you or me to work on currently.

The economic activity is in NEW stuff, not established stuff that is on the way out.

So the task of a senior person in this industry is to determine what the intersection is between what he or she already knows that is valuable, and what the industry is interested in doing next.

Know event-driven OOP GUIs? Learn mobile development.

Know server databases? Learn how to apply the knowledge to the problems found in dealing with WANs and mobile networks.

The point is, the kids are only going to know the one current tool placed in front of them that they dove into. They have no practical judgement, know no context, and are bobbing like corks in the water.
« Last Edit: July 31, 2010, 12:14:40 am by G0ddard B0lt »
Gornix is protected by the GPL. *

* Gorn Public License. Duplication by inferior sentient species prohibited.



Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf