Ang Kape Ni LaTtEX

55 responses so far ↓

• 1 bugsybee // Apr 20, 2008 at 9:41 pm

  Wow. I used to always buy my tickets from Cebu Pacific online and I was always happy with the results. I didn’t know they changed their system. (By the way, I just checked how the system works on Safari and it seemed okay – of course, I stopped where it was about to ask me details for the ticket.)

  Coincidentally, a friend asked me to book her for a round trip ticket on PAL and I was happy with how the online ticketing system improved (although you have to work fast because they log you out if you don’t print out your ticket right away). I also used to book Cebu Pacific because of the lousy PAL online system.

  So maybe they switched web developers?

  That’s a pity – so early for Cebu Pac to deteriorate, no? I was hoping it would put PAL on its toes (competition is always good for the consumers).

• 2 Justice~! // Apr 21, 2008 at 2:47 am

  I’m not trying to be too devil’s advocate here (btw, speaking of usability the font size for these textboxes is something like 5px on Firefox for my mac )

  but it is possible it got switched because of a technology refresh. I don’t know all the background but sometimes depending on how old the tech driving a system is, the company will do a refresh on it because geting resources to work on the system is cheaper. (e.g. if your system is written in 1.1, sometimes companies will upgrade to 3.5 (and in the process try to “redo’ pieces of the system) simply becuase it is cheaper.

  That being said, from a usability standpoint that is pretty horrid nonehtless.

• 3 Jon Limjap // Apr 21, 2008 at 11:12 am

  bugsybee,

  Thanks for checking it out. I guess that clears it.

  Justice,

  Yes I know about the font size issues on my blog, I do have to change the template and it’s been years overdue doing it.

  I do think that this is a technology refresh. My impression is the old system was indeed written in 1.1, and it was probably moved to 2.0 or 3.5, and then a couple of other features were integrated — checking their press releases Cebu Pacific said that their system changed integrated a lot of things like Check-In, which used to be a totally separate system from their web-facing system.

  However I still think that QA did a really, really bad job here, especially since they put up a website where you have to accommodate all sorts of users. So that’s ultimately where the problem is.

• 4 reyna elena // Apr 21, 2008 at 11:39 am

  DANG! hahaha!

• 5 aboy pogi // Apr 21, 2008 at 2:42 pm

  Hi Lattex,

  Just a comment. Its better I think if you didn’t mention any names in your blog. I know you are a programmer. Dont you have bugs in your codes? Microsoft does have plenty I believe… So its better if you’ve contacted someone from CP or the provider and give an open feedback about the application. It seem like you were hacking something just to expose it and not help the hacked system fix it.

• 6 Jon Limjap // Apr 21, 2008 at 3:06 pm

  aboy,

  Me, naming names?

  No, Cebu Pacific was quite proud of publishing it themselves during the rollout:

  http://www.cebupacificair.com/aboutus/press/2008/04162008.html

  And no, we couldn’t even talk to customer support because it takes 1 hour (on average, the past few days) before a human answers the phone in Cebu Pacific’s customer support.

  So, hacking something? Don’t think so. More like just blackbox testing it from the public net side. It’s not things only hackers will find — it’s experiences real customers are encountering.

  Are you, by any chance, from NAVITAIRE?

• 7 d3mons_howl // Apr 21, 2008 at 3:36 pm

  Hi Jon nice read very informative of what is happening with our favorite low cost carrier! I’m a loyalist of 5J flights, I save more with my trip home

  There are a lot of factors that might have resulted to this issue right here. There is no point solely blaming QA(Yes I am a QA wooohoo so don’t bash my kind heheheheh *peace*) for such bugs as such bugs may not appear in the testing environment and may only appear in live environments. You are a developer right? Have you experienced that what you did is working in your local machine but is not working in an environment a QA is using? And we’re talking about web components here which ummm is very unpredicatable based on experience hehehehe.

  There should have been a UAT (User Acceptance Testing) activity where 5J should have tested if the new system functions well. 5J should have tested every nook and cranny of their new system to catch any bugs missed during QAT since 0 bugs can’t be assured by anyone. After this UAT, then they decide if the new system is good to go or not. I think this is where the problem is, the testers in the UAT. Ummm are they considered QAs as well? hehehe got confused there because 5J can get a handful of their actual agents to just do what they normally do during UAT Which QA where you pointing at btw? the developer’s QA or 5J’s QA for UAT? hehehe

  I did my research and saw that 5J is not the first one to be in this new system. There are foreign carriers in the system as well way before 5J got it and no issues being encountered like what 5J is experiencing. Hmmm there must be a problem then but not with the developer’s QA.

  I was also thinking that web pages are customizable right. With knowledge of XMLs, XSLTs etc that would be easy. Would there be any chance that 5J tweaked such pages resulting to what happened? Would you know Sir Jon? I am not the expert in that since I’m no developer, I was once but got tired hehehe

• 8 aboy pogi // Apr 21, 2008 at 3:37 pm

  Hi Jon,

  Actually im not trying to make a bad conversation about this. I think as a developer ( and you know that Navitaire is also located here in the Philippines) you should help others improve their work by positive criticism.It seems like this blog is in a negative note. In msnforums we help one another solve problems right? I believe you can construct the blog in a positive way without putting down CP or the system provider. Filipinos helps filipinos… lets be proud of what we can do…

• 9 pops // Apr 21, 2008 at 3:41 pm

  Hi Lattex,
  You’ve mentioned that you’re a developer, do you have any idea of the software QA process? Post development, software is deployed to QA and that’s when “QA phase” would, of course, happen. Pre-production, the software would go to UAT or the User Acceptance Test and that’s when software is tested by the client itself. If they found bugs in the system, that’s when they would report this so as to get fixed either immediately or wait for the next release for this to get resolved. So what’s seen in the production, hence the website you’re apparently criticizing, has already gone through client testing. I believe the system you’re developing is also not bug-free, it just so happened that Navitaire’s client which is Cebu Pac is hugely patronized by customers.

• 10 Jon Limjap // Apr 21, 2008 at 3:42 pm

  d3mons_howl,

  I know, but then a public-facing website has to be QAed more intensively. As I said, the UI problems are excusable, as they are not blockers.

  But phen’s experience is a MAJOR BLOCKER.

  I also have another friend (who I will not name here, since she’s lodging a formal complaint) who lost PHP5,500 pesos to the system.

  With money involved — especially customer money, it’s not a simple QA problem anymore.

• 11 Jon Limjap // Apr 21, 2008 at 3:46 pm

  aboy,

  Does Navitaire of Cebu Pacific’s being Filipino excuse them from making mistakes which involve money?

  Phen, who was gravely inconvenienced, is a Filipino. My wife, a travel agent also gravely inconvenienced, is also a Filipino. My friend who lost PHP5,500 in a transaction in the new system is also a Filipino. Should I ignore their valid grievances because the accused parties are also Filipino?

  Yes, this blog is in a negative note, because we can’t view the world in rose-colored glasses all the time. We have been very, very happy and satisfied resellers/clients of Cebu Pacific — my wife and I flew with them 3 roundtrips already within the last 12 months — yet I cannot for the life of me let mistakes that involve time AND large sums of money go unnoticed.

• 12 Jon Limjap // Apr 21, 2008 at 3:50 pm

  pops/d3mons_howl,

  Yes, I am quite aware, because where I come from we work closely with QA when big problems occur. In fact I have been to client sites during UATs in previous projects.

  And from what I understand, ANY PROBLEM THAT INVOLVES MONEY IS A BLOCKER. As in it means TAKE THE SYSTEM DOWN. Because it involves client’s money, which if left unattended would result in lawsuits and legal headaches.

  I do not know why Cebu Pacific did not operate this way with their software.

  Or maybe they simply do not listen to their customers?

• 13 aboy pogi // Apr 21, 2008 at 4:07 pm

  Hi Jon,

  Im sorry about the money. I hope CP can do something about it. But anyhow, I just dropped by and shared my 2 cents about this. I hope we can still help one another in a positive way. Thanks for the info by the way. I’ll see if I can foward this to someone I know from Navitaire. See you in msforums dude!

• 14 Jon Limjap // Apr 21, 2008 at 4:11 pm

  aboy,

  Thank you. I would appreciate that, because I seriously think fixing this whole brouhaha will be for the benefit of both Cebu Pac and Navitaire.

• 15 d3mons_howl // Apr 21, 2008 at 4:13 pm

  Yes I hear you there Jon, I was just reacting with pointing hands to QA which may not be the real issue behind what customers is experiencing right now as QAT is not the last phase of the process.

  I would agree that any issue that has something to do with MONEY is a BIG SHOW STOPPER. I would fight with management if I find an issue involving money matters but will still push that the software be released. Heck, I would be in rage if I find I lost money during a transaction and I would take measures to get it back in some form or another. I won’t file a law suit, I don’t have that much money

  I don’t know if Cebu Pacific listens to their customers, I haven’t filed any complaint yet so I have no experience of it first hand.

• 16 ali-kat // Apr 21, 2008 at 4:17 pm

  Jon,

  what do you have in mind when you said: “a public-facing website has to be QAed more intensively”? Can you provide examples perhaps to enlighten all of us with what SHOULD have been done to avoid this.

• 17 Jon Limjap // Apr 21, 2008 at 4:30 pm

  ali-kat,

  It really depends per-company how they do it, but this is how I know it should’ve been done. Note that this should be done AFTER QA testing, User Acceptance Testing and Technical Acceptance Testing:

  1. Replicate production environment. Ghost the drives of the existing disks or use one of its RAID mirrors to set up a clone of the production server

  2. Set up the SkySales system in the mock production server

  3. Run closed private beta using the mock production server. This can be done by setting up that only fixed IPs (probably those assigned to Cebu Pacific offices) will be able to access the mock prod server even if it’s already publicly hosted.

  4. Do real world credit card transactions on the system. Cebu Pac can easily arrange this with their Metrobank Go! Mastercards

  5. Run several scenarios thrice over, e.g., a customer booking a flight within the same day, a customer booking a flight a few days off, etc.

  6. If bugs are found, fix, repeat from step one.

  7. Open the system to a public beta. Have the old system up and running put on standby: put the new system in production.

  8. If customer complaints considered as a SHOW STOPPER/BLOCKER come in, fire up the old system while fixes are applied to the new one. Communication with users should be VERY VERY OPEN at this point, so that any problems they encounter could be taken into account.

  I might have missed some steps, and I have NO IDEA how CebuPac and Navitaire did this, but this is a rough idea on how it should’ve been done. Clearly, there have been cases wherein problems where encountered that can be considered SHOWSTOPPER/BLOCKER but the system is still up and running.

  And to illustrate just how responsive Cebu Pacific is to customer feedback, read this:

  http://aileenapolo.blogspot.com/2008/04/i-lost-money-because-of-cebu-pacific.html

• 18 ali-kat // Apr 21, 2008 at 4:40 pm

  Hi Jon,

  that’s a long list. You mentioned in your notes that the steps you provided SHOULD BE DONE AFTER QA testing, User Acceptance Testing and Technical Acceptance Testing. If it’s after QAT (then QAs aren’t responsible to do the steps), and UAT (then the client’s QAs aren’t responsible to do the steps), and TAT (then the QAs for this arent’ also responsible to do the steps), then who should do this??? Doesn’t this mean that it’s not the QAs (QAT, UAT, TAT) fault then?

  I believe that the steps you’ve mentioned are part of what is being done during QAT, UAT, TAT. However, also consider that some bugs that appear are caused by other factors. Not all companies can set a real-life testing – there is a limit to the number of people that can test the system during QAT, UAT, TAT. I don’t know how you do it in your company, producing a bug-free system. But in real-life, there is no such thing. ALL SYSTEMS are BUGGY. there is no perfect system.

• 19 Jon Limjap // Apr 21, 2008 at 4:48 pm

  ali-kat,

  No, QAT, UAT and TAT will sometimes overlook those tests because they’re not live. What I described is more akin to a BETA. BETAs come after QAT, UAT and TAT in the case of public-facing/non-intranet site.

  Whichever way it goes however, it does not remove the fact that there is a big, big blocker existing in the system, and these concerns have to be responded to. Yes, you are absolutely correct: All systems are buggy. And All software are buggy. BUT, buggy systems which cause customers to lose money should be shut down immediately.

  Or at least mitigated properly offline.

  In the case of Aileen (link posted above), the mitigation is NOT happening at all.

  And the problems concerning the system continue.

• 20 C-SIW // Apr 21, 2008 at 4:55 pm

  Hey Jon,

  I read your friend’s blog about the incident and I just wanted to let you know that I already encountered this problem with CebuPac way before they decided to upgrade their system. I don’t think it’s right to blame everything on their new system, we should probably blame the admin itself for being not being able to handle their customer inquiries and reports better.

  Also knowing from what d3mons_howl was saying, i do believe that the QAT environment is a little more stable than the live environment. Having said that, maybe CebuPac didn’t alot enought time and resources to make sure that their new system is working well in production.

  Just my 2 cents

• 21 And I Am Not Flying Cebu Pacific « BuLOnG // Apr 21, 2008 at 4:55 pm

  [...] of this and this, and perhaps more to [...]

• 22 ali-kat // Apr 21, 2008 at 5:02 pm

  Jon,

  Here’s what i got from what you’re saying: Cebu Pacific should address the issue – in any way they see fit. It’s not the QAs fault nor the software companies fault (in this case Navitaire). You are just simply asking that there is resolution. If that is the case, then it is beyond our (customers), QAs, Navitaire’s hands. It’s up to cebu pacific to make a resolution – to either stop

  I agree that a show stopper should be addressed. We may not know what’s going on in the background but for sure, as this is causing so much money issues and trouble to the customers, cebu pacific, and perhaps even navitaire, this is being discussed and addressed. It may not be visible to the public just yet, but as any company would do when faced a show stopper, things are definitely being done to resolve the issues in the background. We just hope that it comes sooner.

• 23 Jon Limjap // Apr 21, 2008 at 5:09 pm

  ali-kat,

  Well, with the story of Aileen out, it appears (at least to me) that there is NOTHING being done in the background. And that is why I wrote this.

  I do admit that I might have been a little bit harsh in dragging Navitaire into this, but nobody can deny that they *are* part of that failure. And the way their separate payment/reservation pending/confirmed statuses aggravated the confusion.

  Nonetheless I hope both companies work together to solve this soon.

  C-SIW,

  Indeed, that is evidence of a much, much deeper problem on the side of Cebu Pacific. How many people out there have lost money because of their incompetence, however?

  Should someone put up a consumer-group to consolidate complaints against CebuPac similar to the Pepsi 349 movement of the early 90s?

• 24 Should I Worry About Cebu Pacific? « The Life & Times of The Renzie Man // Apr 21, 2008 at 7:51 pm

  [...] Lattex’s blog entry on how unsatisfied he is with Cebu Pacific’s new Navitaire system.  Read the rest of his [...]

• 25 Ang Kape Ni LaTtEX » Blog Archive » Cebu Pacific’s failure isn’t in the software, it’s on the phone // Apr 22, 2008 at 10:41 pm

  [...] the ensuing comments in my previous post, Cebu Pacific’s monumental failure: A new online reservation system, several people questioned why I appeared to be singling out Navitaire and its online reservation [...]

• 26 amiwebguy // Apr 23, 2008 at 12:12 am

  Lattex,

  I agree with aboy pogi, you should focus more on how to help than try to degrade their efforts.

  I would also try to understand the Navitaire software before you bash it. It looks like most web-based software in that it’s highly customizable. Look at some of the other customer sites (http://navitaire.com/company/customers_all.asp) and you’ll see a wide array of designs for very large airlines like JetStar, Ryan Air, AirTran and more.

  Your analogy is like saying WordPress is bad blogging software because someone designs a poor skin for it. Just because the outside wasn’t implemented the best doesn’t mean the product is bad.

  A good example is your own page. If you run it through the W3C Validator you’ll see you have 10 errors on this page alone.
  http://validator.w3.org/check?uri=http%3A%2F%2Fblog.kapenilattex.com%2F2008%2F04%2F20%2Fcebu-pacifics-monumental-failure-a-new-online-reservation-system%2F&charset=%28detect+automatically%29&doctype=Inline&group=0.

  As a software developer you should realize that we’re all human and all make mistakes. The difference is what we do with them, do we try to make things better and move forward or do we concentrate on the negatives?

• 27 Jon Limjap // Apr 23, 2008 at 12:34 am

  amiwebguy,

  Sure, my site aint perfect but, all your EXCUSES become invalid WHEN WE’RE TALKING ABOUT SOFTWARE THAT INVOLVES REAL MONEY.

  Cebu Pacific has caused lost productivity, and in many cases, actually lost money (refer to: http://aileenapolo.blogspot.com/2008/04/i-lost-money-because-of-cebu-pacific.htm ) so “we’re all human” takes a backseat here.

• 28 Aileen Apolo // Apr 23, 2008 at 1:07 pm

  Ay nosebleed ang system problems nila for me. I am just a plain consumer and I really HATE THEM RIGHT NOW. I wasted a lot of time because of them… and worse, I am Php6,000 poorer! RAWR!

• 29 cocoy // Apr 23, 2008 at 2:00 pm

  “we’re all human takes a backseat here.”

  yep.

  Bad PR, when people start losing money.

  i think the proper response would have been an apology and a correction of the bugs in question as quickly as possible.

  hope cebu pacific gets their act together real soon.

• 30 Roy // Apr 24, 2008 at 7:31 am

  Hi Lattex,

  I used to work at Navitaire and was very much involved with this reservation system since it was in its beta version. Your concerns are valid but from what I’ve experienced we get a whole lot of different problems whenever we go live on a customer (and we have been involved with the big names in low cost carriers). What happens is we deploy the system, we find problems and we fix them. These problems are as varied as the landscape of low cost carriers. Cebu Pacific is not the only low cost carrier in the world. You should look at how other major carriers do business and realize the challenge is so much more than div tags and browser compatibility. One of the challenges that Navitaire has to deal with that most people do not see is keeping the SAME system working for different customers in different worlds. Navitaire has done well just being able to meet this challenge. This answers the question why Cebu Pacific decided to change. It’s not because their website would work better, but because this will allow them more flexibility once they begin going into different markets. Sure they are upsetting people right now but in the long run their new system will not restrict them from expansion. Sure Cebu Pacific is losing money because of problems with the new system, but from what I’ve seen, I’ve seen worse and I know this won’t kill them.

  Yes, I agree with you the problems you illustrated are simple and could have been easily avoided, but I also think saying “monumental failure” is wrong. Obviously you do not understand the monumental challenge that Navitaire deals with on a daily basis. Blogs are great but I think most people (such as yourself) do not stop, observe and think before forming an opinion and that is just contributing to all the junk that we get on web.

• 31 Jon Limjap // Apr 24, 2008 at 9:06 am

  Roy,

  So, are you taking personal offense at my statements? Have you read the thread subsequent to this? Please do, I’ve clarified a few things there.

  As for Navitaire being able to customize/implement this across various airlines across the world, I have to point out that that is irrelevant for the thousands of people Cebu Pacific is inconveniencing right now. It doesn’t matter if you’ve got Delta or Jet Blue under your belt if you’re unsure whether the ticket you paid with your credit card for will be accepted once you go to the airport.

  With all due respect, it is Cebu Pacific Sky Sales implementation that looks like “web junk” at its current state, although I believe it would be a beautiful product once all issues are fixed.

• 32 gg // Apr 24, 2008 at 10:09 am

  I am also a solutions provider and I just cant stand when my company produces a bug and the customer suffers from it. When it does, everybody is on a hyper mode as everybody’s horn is honking.

  I earlier took this issue as something of a management problem (both of Navitaire and that of Cebu Pac), but upon reading the responses, I am beginning to see areas that needs some highlighting and perhaps enlightenment.

  (1) the simplest of errors are still seen online. though this is tolerable to Jon, not for me. It clearly shows there is an attitude problem somewhere. “Footer lang yan..” Had that simple error showed “Sebu Pacific” rather than “Cebu Pacific”, I guess everybody, including CebuPac, would start cursing Navitaire. BUt the superficial issues are no show stopper, which I think made the people involved to deprioritize such issues. That is clearly an attitude problem somewhere. Tolerable on both CP’s and Navitaire’s side of the fence but it is bad PR for their site’s users/customers.

  (2) I have also visitied myself the site after reading Jon’s blog and see it myself how true his assertions were. As both a user and a developer, I was shocked to see the UI in disarray. I called up my girlfriend to check on the site and she remarked as “sabog sabog ang page”. I just cant believe those kinds of errors have gone beyond QA. Since those errors went past beyond QA, these problems become a management problem. Those errors that the world can see clearly show that some people are not doing their job well. If I can see those problems a week from now, then clearly, the problem is deeper than I thought. PUede namna cguro ma fix na agad ang mga simpleng bagay right? I think these errors have been left unattended for weeks now? Am i right?

  (3) Some of the responses to Jon’s blog are clearly not aware of the issue raised at hand. Now the questions is not whose fault are all these, but who should own up to these failures? Of course, Cebupac can always come up with a PR job and apologize to the customers, but whose neck should be on the chopping board?

  (4) I have been using the old version of the site and was happy about it. Like another poster said, compared to that of PAL, Cebupac’s older system is fine. I have a confirmed and paid ticket for Singapore this coming August which I bought last March using the old system. Earlier, I checked the status of that ticket and the system just plainly produce an error and offered no guide on what to do next. As much as I am a developer, the customer part in me says, “teka, nasaan na ang ticket ko?”. I think this should be the bottomline and needs to be asnwered.

  I think somebody released an Alpha and forgot to include the usual disclaimer that the system is not fit yet for production.

• 33 Jon Limjap // Apr 24, 2008 at 10:20 am

  Andrei Kirilenko,

  I’ve chosen not to publish your comment until

  a.) You remove all your ad hominems from your comments.
  b.) You reveal your true identity with a real name and email address.

  I’ll listen to you when you stop insulting me as a person and start criticizing my opinion. Sorry dude, kung hindi mo maintinidhan ang pagkakaiba niyan, hindi ako ang bobo.

  =====

  It’s amusing that software developers from Navitaire are apparently taking this as a personal attack when what I’m attacking is the system, not them.

• 34 Stevenson Salvador // Apr 24, 2008 at 10:26 am

  To: Jon Limjap

  hoy kumag…magtigil ka ha kung gusto mo pang umabot ng buhay sa pinapasukan mo…minsan kelangan mo lang mag exercise sa isip…medyo marami ka atang punto eh..apply ka ng navitaire para masabi mo ng buo mga punto mo..hindi yung nagpaparinig ka through blogs…mukang naghahanap ka ng kakampi online eh..mas maganda siguro address mo sa cebu pacific lahat ng reklamo mo at mga magaganda mong nakikita..para nasasabihan nila yung gumawa ng system kung ano ang tamang gawin..sayang naman punto mo kung makakatulong pala sa sistema nila…

  tapos ayon sa kagaguhan na pinagbabanggit mo dito:

  * Reservation is pending and payment is pending. Can you board the plane? No.
  * Reservation is confirmed and payment is pending. Can you board the plane? No.
  * Reservation is pending and payment is confirmed. Can you board the plane? No.
  * Reservation is confirmed and payment is confirmed. Can you board the plane? Yes.

  wag kang gumamit ng opinyon mo tanga! mag research ka muna ng airline process tapos maglagay ka ng footnotes dito..pero anyway..wala naman akong pakialam don…naglalabas lang din ako ng opinyon tulad ng ginawa mo..kaya quits quits lang..antipatiko ko no?

• 35 Stevenson Salvador // Apr 24, 2008 at 10:30 am

  pre pakitanggap opinyon..sayang eh..for the crowd..you know..parang ginawa mo ren..bwahahaha

• 36 Justice~! // Apr 24, 2008 at 10:36 am

  I am astounded that anyone on this site who works in professional development would think that the quality of Navataire’s release is in any way acceptable. Sorry, guys, but as someone who heads up some monumental projects himself, the kind of errors you see on Navaitaire are not things that “should have been caught by QA”…they are things that should have never *even made it to QA* before being fixed.

  As for the person who said “Filipinos help Filipinos out”, frankly how much constructive criticism should Jon offer here for free? Let’s be real here – if Jon is going to fix all of Navitaire’s problems, he should be getting paid to do so.

• 37 Stevenson Salvador // Apr 24, 2008 at 10:38 am

  thanks

• 38 aboy pogi // Apr 24, 2008 at 10:58 am

  Sir gg! Si aboy to ng msforums.

  Based sa comment mo sir I think ok lng kung ganito ang mga comments natin sa ganitong situation:

  “the system doesn’t work well, CP fix it now”,
  “the webpage is messed up they should fix it”,
  “previous system works fine why change it”

  Pero pag hinaluan na natin ng mga QA QA, dev dev, etc etc… sir mukhang may iba na tayo pinupunto…

  Sir sa company nyo may confidentialty na tinatawag diba… ganun din siguro sa CP at Navitaire. hayaan na lng din natin ang CP at Navitaire ang trumabaho nito… d na siguro natin kailangan ng comment na “attitude problem” etc etc… kasi alam ko ang pagiging boastful ay isang attitude problem din…

• 39 aboy pogi // Apr 24, 2008 at 11:06 am

  Sir gg peace tayo ah.. opinion lang… love filipinos dapat! peace

• 40 Andre // Apr 24, 2008 at 12:29 pm

  masyado nyo naman pinepersonal yun pamumuna eh, ayusin nyo na lang yun software/system bugs. para di masayang energy nyo.

  kung kayo rin ang maperwisyo dahil sa system bug, ewan ko kung di rin uminit ang ulo nyo.

• 41 gg // Apr 24, 2008 at 12:48 pm

  Sir aboy, I respect your opinion. pero sir naman, nakita mo namna cguro kung paano ang histura ng website. sa simpleng footer problem ba nde mafix un since it was released? Ilang linggo na yun a. Hinintay pa kase na mapansin ng iba, ayan tuloy.

  Di ba nga may kasabahin, you only hurt the ones you love. hehehe.

  Pero teka, bakit may peace offering ka na agad? Inaway ba kita? o Inaway mo ba ako? nde di ba?

• 42 gg // Apr 24, 2008 at 1:04 pm

  @ Justice

  “Sorry, guys, but as someone who heads up some monumental projects himself, the kind of errors you see on Navaitaire are not things that “should have been caught by QA”…they are things that should have never *even made it to QA* before being fixed.”

  Sir, naku madaming magagalit sa yo nyan. Yung sa akin sa QA level lang pero mas stricto pala sa yo. Pero sobrang agree ako sa yo. Kaso matatakot mga QA sa yo kase baka sabihin na wala silang ginagawa kase sobrang malinis na ang systema pag nakarating na sa kanilang level.

  Ako eh sobrang bagal mag code kase maya maya Build+Run, maya maya Build+Run kahit minsan alam kong wala naman akong ginalaw.

• 43 gg // Apr 24, 2008 at 2:43 pm

  i just checked the website a few minutes ago and guess what, the footer mess is gone. yehey! effective!

• 44 Jon Limjap // Apr 24, 2008 at 2:55 pm

  gg,

  I guess we’ve got their ears and eyes now.

  FYI though, Justice is American

  Justice,

  I’m translating gg’s comment addressed to you:

  “Sir, a lot of people will be mad at you. On my side it must be at the QA level but you’re even stricter. But I totally agree with you. But the QA might get scared of you, they’d not be doing anything if the system is so stringent before it gets to their level.

  I code quite slowly because I do a Build+Run every so often, sometimes I do a Build+Run even if I haven’t changed anything.”

• 45 gg // Apr 24, 2008 at 4:16 pm

  hahahah .. that’s the translation? funny!

• 46 Jon Limjap // Apr 24, 2008 at 4:34 pm

  gg,

  It’s a rough translation. Hope I got the context right.

• 47 Roy // Apr 24, 2008 at 10:41 pm

  No Jon, your review did not offend me. As I said your points are valid. I just think you are BLOWING THIS OUT OF PROPORTION. Yes, losing money is a big deal, but I bet Cebu Pacific will still be around years from now and this whole thing will seem like it never happened. The truth is even if this is pissing off a lot of people, people will still fly Cebu Pacific. I just think you really do not know what you are talking about so stop acting like you know it since it only puts you in bad light. Do us all a favor just shut it.

• 48 Jon Limjap // Apr 24, 2008 at 10:54 pm

  No Roy, I will not shut it. No one has the right to tell me to shut up.

  So I’m blowing this out of proportion? This is a free country, we have freedom of speech, and this is my blog. I can state my opinion, just as long as I can present evidence based on testimonies of Cebu Pacific customers, my wife who is a travel agent, and our travel agent partners.

  I have the right to say what I want to say just as long as it is not defamatory, which I believe it has not been. And I have a right to complain when I or people close to me are inconvenienced by substandard products and services.

  I AM NOT OUT TO BRING CEBU PACIFIC NOR NAVITAIRE DOWN.

  I wrote this that BOTH YOUR COMPANIES would listen to me, AN AVID FAN AND CONSUMER OF CEBU PACIFIC’S SERVICES.

  But what did you guys do? YOU GUYS THREATENED MY LIFE AND INSULTED ME INSTEAD.

  This is PRECISELY the attitude that I want to change. No, Roy, I REFUSE to become beholden to your “I’m a big company you’re just a customer so shut up” attitude YOU are exhibiting here.

  Kahit ano pang pangtututya at pagbabanta ang gawin ninyo sakin hindi ako tatahimik dahil karapatan ko yun.

  So me, shut up? MAKE ME.

• 49 .NET @ Kape Ni LaTtEX » Blog Archive » Unsolicited advice for improving Cebu Pacific’s Sky Sales system // Apr 29, 2008 at 9:30 am

  [...] controversial, death-threat worthy posts regarding Cebu Pacific’s dismal service and the involvement of software development company Navitaire was that they found my posts too negativist and tried to bully me into suggested that I criticize [...]

• 50 Unsolicited advice for improving Cebu Pacific’s Sky Sales system // Apr 29, 2008 at 9:34 am

  [...] controversial, death-threat worthy posts regarding Cebu Pacific’s dismal service and the involvement of software development company Navitaire was that they found my posts too negativist and tried to bully me into suggested that I criticize [...]

• 51 Colt Cooper // May 1, 2008 at 12:36 pm

  Wow guys, I stumbled across this blog and am a little shocked at the emotional response in some of the posts here.

  I used to work for Navitaire under their professional services arm and now consult independently providing implementation services for their NewSkies product.

  From experience, I agree – take care of any issues that cause money problems first, then take care of the rest. Usually the carriers who implement this system are “low cost carriers” and get hurt BAD if they loose money for even a day.

  Cebu Pacific has chosen to go with the Navitaire Web system (SkySales) virtually out of the box with the original flow intact. They “skinned” the website – providing just updates to the CSS and images. This means that any deficiencies came from the original Navitaire XSLT “skin” provided for carriers to base their customizations off of.

  I know Navitaire has an internal push for their web team to get that out of the box skin XHTML compliant (which makes me believe that amiwebguy is a current Nav employee). Most of the carriers who want heavy customization to their flows just throw out that default skin and roll their own from scratch.

  Since this is my line of work, I definitely would like to be a part of the solution (and am more than capable). Cebu, if you’re reading this, I can help!

  For everyone else, lets simmer down the death threats, geesh.

• 52 .NET @ Kape Ni LaTtEX » Blog Archive » A portrait of a software developer as hero // May 2, 2008 at 6:48 pm

  [...] am deeply saddened by what had transpired last week wherein some software developers failed to see the importance of their roles and saw themselves as mere 8-5 worke… who try to make a living. If you are a software developer — you are NOT supposed to be [...]

• 53 On Jon Limjap and Blogger Death Threats // May 8, 2008 at 11:06 am

  [...] a blog post severely criticizing Cebu Pacific’s new online ticketing system, and received a comment saying “magtigil ka ha kung gusto mo pang umabot ang buhay” (rough translation: [...]

• 54 Cebu Pacific is world #1 budget carrier interms of growth // May 29, 2008 at 10:26 am

  [...] is one of the reasons why Cebu Pacific has been gung-ho in expanding their operations, including a change in their online reservation system which led to quite a fuss in this blog a few months [...]

• 55 Cebu Pacific’s One Peso Seat Sale – Fail! // Nov 2, 2009 at 3:32 pm

  [...] to use them. In the past CEB seat sale, the same glitch apparently happened to this blogger. These error bugs, apparently, are not new. So why weren’t they fixed [...]