Project Pitbull - Back from the Brink

Well its one week to go live and we are coming back from the brink. People have put in some long shifts and more to go in this last week remaining but measurable progress is being made.

Our turnaround strategy involved.
1. Understand true scope of what we need to do. The api status spreadsheet was a big help to show our true status.
2. Prioritize. We decided on a 'Finder First' strategy i.e. we must dedicate API team to completing Finder apis at expense of other APIs. The necessity of this had to be explained to AM/PM etc.
3. Identify workarounds where possible. We identified we could reuse some existing main site apis and started work on using and proxy-ing them immediately on front-end.
4. Keep non Finder team moving forward as much as possible.


At the same time we've been focussing on QA and bug fixing.


Coding a 404 page for your app in Backbone:
  • Put *path as last route on a Router
  • Also code a specific route for 404 page e.g. #404
  • When *path route fired then router navigate to #404, a route which you should have show the 404 page using a Backbone view 
  • We have more than 1 router but only gets to *path if not picked up by other routers, so race condition is not an issue


This note from the SVP for services at Fluid Aug 3:
Hi Team.
Just a quick note to let you know that your work this week has been phenomenal. We have made tremendous progress and your efforts have not gone unnoticed. We’re tracking now to possibly make our deadline if we can keep the momentum. I know the weekend is upon us, but I ask that you all continue to press forward in any way you can to keep us moving forward.
Keep up the great work and please let me know if there’s anything I can do to help (QA, review, bring you food, walk your dog…whatever it takes!).

Comments

Popular posts from this blog

deep dive into Material UI TextField built by mui

angular js protractor e2e cheatsheet

react-router v6.4+ loaders, actions, forms and more