| |
.
. . |
|
| |
 I
started learning JAVA because I was fascinated with its similarity
to C++. Although it lacked pointers I considered its distributed
nature to be very powerful. After about six weeks I was distracted
by a contract position to re-build the DNS Tables for a local ISP.
Yet, I continued to implement class applets on future Internet projects.
Technical
Description of the Fade-In / Fade-Out JavaScript
The
Internet is very much uncharted. It's
the present showcase - the mirrored exposure
for technology at time: t(zero).
A frequent mistake for newcomers too the
net is equating the "Net" with other utilities
in their lives. Like: radio, television,
and the telephone.
As a result of there being so much "development,
the direction technology is a variable.
Not alone, I started to use this Web to
help me build my own site. I grabbed Java
scripts and mouse-overs. Offering it back
to explain what I noticed.
|
Days
Alive Calculator (too simple!)
 As
a result of there being so much
"development, the technology started to
control variables. Applets began to be
compiled in distributed environments over
the Web.
I wrote a program to calculate the time
(days, seconds, etc.) a person had been
alive given a birthday. I got as far as
version 1.0 of this practice program.
|
5
Points Virtual Walk Through Project
 Some
projects don't get past the design
phase. Wait. Did I say "some"? "5-Points"
is a commercial and social center
in the city of Columbia, South Carolina.
The project was to make a visual multi-media
interactive slide-show presentation
of the shops and streets of this area.
I started the design, compiled a few
test programs; but got tired of the
project. These things happen.
|
|
|
| |
|
|
Frame
Relay Installation |
 Our
ISP's remote POP needed an increase in bandwidth. After implementing four
new phone connections the bandwidth needs were causing problems for our
customers. I detailed and logged my implementation of a Frame Relay connection
to this remote POP. I was pretty much alone on this one, but I "pulled-it-off".
The project took more than twelve two-hour rides to the remote POP - thank
goodness it was close. My partners in management were swamped with the
business side of the company; the customers were concerned, and the pressure
was on. |
| |
|
| Web
Camera |
Back in late 1997, using a T1, I attached a Web Camera to monitor
our company’s below-ground network hub. (our NOC = Network Operations
Center ). Via Perl, I refreshed a directory on the webserver (a
Netscape Suite Spot bundle ). HTML just pointed to the webcam
photo. The Perl program updated the photo via a timed ftp process
from the machine where the camera was to where the webpages were
served to the WWW. Click (here)
for a goofy {?} graphic of this process. |
| |
|
|
Proposals
|
Web-Catalog / Web-Commerce
Internet
Gambling Project
All proposals after a few months seem ridiculous. The saying:
Life is lived forward but understood backward. Holds
true here. Technology moves at light-speeds, measured in changes
- and the best a proposal can do is illuminate a process and
slap a price tag on it.
The predictions of the proposal turn out to be only a "scout's
view". A proposal is a "first-dunk" and a paper road-way.
Selling
an idea to a client can be sticky business. It is easier to
be "sold" on a job (...as in `to be offered a job`)
- then it's yes or no. Companies need proposals in order to
encapsulate complicated projects into simple categories. This
helps them understand the full ramifications of what they
are getting into. This, to me, is acceptable.
Proposals also help company representatives feel that designers
have their shit together. This makes a pet-project or a good
cover-up easier to sell to upper management. Realizing that
most managers are in-tune with what their peers are proposing,
proposals form the contract between the outside programmer
and these many internal departments.
|
