Retrospective P2 - Revature-Salesforce-Training/Vanquish-IV-A-New-Code GitHub Wiki

Alex Griggs

  • Post-Project2 retrospectives: I haven't been able to get anything nontrivial to completely work in Visualforce; it was a major source of frustration. But testing and triggers seemed to go pretty well. It seems kind of awkward to make tests assert the finest details of a method, which leads to those details being overlooked, so I'm not sure if the solution is to make everyone write super rigorous tests or to make them test things manually. Or maybe I could specialize in testing.
  • Sample of code I am proud of: I thought I would have to hardcode a map to convert letters to gematria values, but then I noticed that the gematria table is just the ascii table plus two lines of code. Beautiful structure.
private static Integer ASCIIToGematria(Integer ascii)
    {
        if (ascii < 97 || ascii > 122) return 0;
        return 6 * (ascii - 96);
    }
  • Future improvements: I've been a little overwhelmed by some of the new content and I feel like I didn't put as much of it in the project as I should have. It's also been hard to find time for Trailhead, so I've resolved to use it more.

Kathryn Olsen

  • Post-Project2 retrospectives:
  • Sample of code I am proud of:
  • Future improvements:

Kory Iwahashi

  • Post-Project2 retrospectives: Adding two new members to the group and losing two of our own members of the group was the most difficult adjustment to make. We were also limited to 5 members instead of 6, so more work for each of us individually. Using the Scrumban board for a project as a group for the first time was also new, and trying to figure out our schedules and time zones was a bit tedious.

  • Sample of code I am proud of: Very happy with how the Navbar turned out and the respective background colors and images for our experience cloud. We were all able to get triggers to work as well.

  • Future improvements: Getting the Platform Event to function correctly and adding an external API. Testing was also difficult and could be more complete.

Nate Kappler

  • Post-Project2 retrospectives: I had some difficulty implementing the Visualforce controllers, but overall I think this project was very good practice for me and gave me good insight into how to efficiently code in apex. It was a bit strange hopping onto a new group/project but in time I got used to it and settled down with it.
  • Sample of code I am proud of: I like how clean i was able to make this controller method in particular public void clear(){ //Tells the page that it is no longer filtering results filterd = false; //Indicates that the filter button has been "unpressed" for offset calculations later reset = true; //Resets offset off = 0; //Tells the page that it should not call filter() or clear() when executing next() pushed = false; //Resets pageblock product = [SELECT Brand__c, Price__c, Name, Type__c FROM Store_Product__c WHERE RecordType.name='Furniture' OFFSET :off]; }
  • Future improvements: I need to make sure I get more used to testing my code

Yury Pushkarev

  • Post-Project2 retrospectives: I feel more comfortable with subjects learned during the lectures now. It was exciting to see different ways in which we accomplished the same/similar objectives. Looking forward to larger group.
  • Sample of code I am proud of:
  • Future improvements: I have to create a functioning platform event, a functioning API that is NOT Chuck Norris.

Group:

  • Post-Project2 retrospectives: The most difficult part of this project was the loss of team members and addition of team members at critical stages of development. The former members of Alchemy started a project that they didn't finish, then finished a project they didn't start. Two of Vanquish's members left the team, which left their assigned features in a precarious state. We expect things to go more smoothly now that the teams have settled.

  • Future improvements: We didn't get the API or platform events figured out well enough, and we would likely benefit from customizing and specializing more apps. Testing would be easier if we did it incrementally for new features instead of saving it for later. We've just started getting used to coordinating each other's schedules.