22 Nov 2001 (updated 22 Nov 2001 at 09:40 UTC)
»
ANSI C Interpreter
Spent some time adding printf probes into the grammar,
figuring out how the rules flow from one to another. Managed
to observe how function declarations and pointer/direct
declarator flow. So far, everything seems to be working
fine, feeling lucky I guess (keno?).
Also there's this itch urging to play with it a little
longer as the idea of merging the C grammar against the Ruby
API. It might turn out to be something like an objected
oriented language using C grammar. Sounds like a lot of
fun.
PostgreSQL
Finally decided to scratch the idea of refactoring the code
for a simple reason of doing manual, a.k.a. grunt work. I
can't do
that! No way dude, it's too labor intensive. What I'll do is
make a
program that will read the symbols and produce a report that
will organize them in a orderly way. I'll just use the C
interpreter to spew out the report.
Grunt Work In Coding
The idea led me to believe the reality that certain levels
in the practice of Computer Programming involve large
amounts of grunt work. And I also believe projects have
a wide bar allocated for that as well. Which leads to
another idea that most developers are actually doing grunt
work rather than creating programs that create programs.
IMO, programming can be a trivial task, provided there
exists a methodology of abstracting certain levels of
complexity to a set of grammar and syntax rules.
Imagine the maintenance it would take when our civilization
reaches the third millenium. I bet most of them (third world
countries) will
probably be working as programmers maintaining 20th century
code. That's not a very good picture, IMO.
Grunt work is basically a waste of resources. It doesn't
contribute to productivity and it punishes the programmer in
a dull and repetitive way. If were only a manager, I would
ask my team to stop doing grunt work and work instead on
programs that create programs. But, I'm not a manager and I
don't have a team, tough for me.
Checkup
Just had my checkup done today. One thing I don't understand
is why does it have a test requiring me coughing twice. The
doctor said I shouldn't think about coughing three times.
Two is enough! Grrr.
Fulltime Job Seeker
Got an idea from a friend that I shouldn't stop looking for
jobs even when employed. That's just how was the situation
and I shouldn't rely on the company's financial situation.
So, that got me calling a lot of recruiters asking them for
anything that might match mine.
Second Contact Highly Unlikely
Ramble. While there is a good chance the first contact
happened way, waaaaaaay back. A second contact (coming)
might be highly unlikely. I doubt the possibility for
several reasons:
- Arrogance.
- Superiority Complex.
- Nuclear weapons / Weapons of mass destruction.
- Reliance on low-tech gadgets.
- Lack of inter-specie communication skill.
- Narrow minded view of existence.
- Patriotism.
- Filibusterism.
- Warlordism.
- Religious belief that we're the only one.
- Braindead economic systems.
What I find interesting is the idea of a god or a very
intelligent and powerful being coming back to Earth to meet
mankind. Somehow, there is this simple message that was
passed from generation to generation, civilization to
civilization, religion to religion; going as far as the
present. Though the message may have been garbled, the main
thesis was preserved, that there is going to be a second
contact.