Troubleshooting preventer

Posted by mkhairul - September 26, 2007 at 08:09:22 pm -

Categories: blog

I’m in kind of a conflict. I’m expected to be a troubleshooter at my office but what I wanted to be more is a troublepreventer, the troubleshooter is still required for some stuffs but doing the same stuff over and over again is not something I’m looking forward to.

The current way we do things around at work something drives me nuts. Lots of security nightmare, disabling all error reporting and much more. I wanted to do the right way, but my justifications went unheard (or maybe its me who doesn’t know how to explain). Either way, I just have to keep playing ball and fix here and there just to keep things together.

As I mentioned in a couple of my previous post. Interakt (or is it MX Kollection?) is the preferred method of building web stuffs (dynamic forms, thumbnails, etc). Well, it is great and fast but hacking it is kinda tedious, the validation isn’t quite as flexible as I’d expected and the documentation is terrible. It only explains on the frontend with all the GUIs shit, but not under the hood where it really matters.

I’d rather stick with CI (Codeigniter) but then again if I do that, some people couldn’t join in developing it. The learning curve is low but you have to have some basic understanding of how stuff works and doesn’t whine and depend on code generators and IDE.

Enough ranting maybe I should do something else like scamming the scammers by scooping 16 Awards or something. Heh. But then again, its too much work for a procrastinator like me. Oh yeah, I’m doing some screen scraping and hopefully it’ll be up and ready to feed my current project with data.

No Comments yet »

RSS feed for comments on this post. TrackBack URI

Leave a comment

Name (required)

Mail (will not be published) (required)

Website

XHTML: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

Search