https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/frontend/-/blob/WEB-APP-FRONTEND/src/frontend/src/components/UPCScanner.vue?ref_type=heads

This is a link to the UPC scanner component that I recently implemented.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/frontend/-/blob/WEB-APP-FRONTEND/src/frontend/src/layouts/MainLayout.vue?ref_type=heads

This is a link to the Main Layout for the Web App, this is essentially the homepage.

Reflection on What Worked Well

One of the biggest strengths of our team has been our ability to delegate and handle specific tasks effectively. Each team member has taken ownership of different aspects of the project, whether it’s the frontend, backend, or database. This clear division of work has helped ensure that progress is made across all areas of the application. Since I am working on the frontend, I have been able to focus on designing and implementing the UI while relying on my teammates to manage the backend and database.

Reflection on What Didn’t Work Well

Despite our strong ability to divide tasks, one area that has posed challenges is communication. There have been instances where misunderstandings or lack of updates led to delays in task completion. Additionally, not all tasks have been finished in a timely manner, which has put extra pressure on certain aspects of the project. This lack of synchronization has occasionally resulted in blockers, where one team member is waiting on another’s progress to move forward.

Changes to Improve as a Team

To enhance team efficiency, we need to establish better communication channels. This could include:

• Holding short daily stand-up meetings to discuss progress and blockers.
• Setting more reasonable due dates that account for individual workloads and unexpected obstacles. By implementing these changes, we can reduce miscommunication and ensure that tasks are completed within a reasonable timeframe.

Changes to Improve as an Individual

On a personal level, I recognize that I can make improvements by:

• Checking in with my teammates more frequently to see if they need help with their tasks.
• Setting personal deadlines to ensure I complete my work on time.
• Being more open to suggestions and feedback from my team, as collaboration often leads to better solutions. By making these adjustments, I can contribute more effectively to the team and help ensure the overall success of our project.

Apprenticeship Pattern: “Be the Worst”

Summary: This pattern emphasizes surrounding yourself with more skilled individuals so that you can learn and improve at a faster rate. By putting yourself in challenging situations where you are not the most knowledgeable person in the room, you can grow and develop your skills through observation and experience.

Why I Chose This Pattern: During this sprint, I have noticed that I can learn a lot from my teammates, especially in areas I am less experienced in, such as backend development and database management. Rather than just focusing on my own tasks, I want to take the opportunity to learn from their expertise and improve my overall skill set.

How This Pattern Would Have Helped: If I had adopted this mindset earlier in the sprint, I would have been more proactive in asking questions and seeking guidance from my teammates. This could have helped me avoid certain mistakes and speed up my development process. Moving forward, I will embrace this approach to accelerate my learning and become a more well-rounded developer.

From the blog CS@Worcester – Software Dev Capstone by Jaylon Brodie and used with permission of the author. All other rights reserved by the author.

Throughout the first sprint there were many learning experiences earned, and a great amount of progress was completed for our server. For a first sprint together as a team, I would say we did very well overall; and the second sprint will only be better. What we did best overall in the first sprint, was completing our manageable goals. In our initial sprint planning, I felt that we set attainable and workable goals. These goals were met by all members of the team in some capacity, demonstrating an equal workload across the team. We were very transparent in our communication, and our communication was frequent and on-topic. It felt that we were very efficient in coming to decisions and working towards a greater goal. I spent my time doing three major tasks; setting up and testing Thea’s Pantry on the server, researching Docker volumes and coordinating with Gio of team 2, and troubleshooting SSL certificates to allow the back-end and front-end to connect without an HTTPS error. 

What didn’t work well in the sprint was our lack of knowledge going into it. Our team in particular is charting entirely new ground, which requires us to learn a good deal before moving anywhere with our project. We also ran into a major issue quite early (SSL error above), which sidelined any progress with Thea’s Pantry on the server. We were able to overcome most of our obstacles, and prepare for an even better sprint two, but there was a rough start with the freshness of the material and our inexperience running sprints. 

As a team we could better work independently, as that is our main drawback. We had very little issues communicating, planning, or working; but most work was done as a group and we pooled our brains into individual issues. This slowed us down, and although we reached many of our goals, had we worked more independently we may have gotten through more. This is something we can improve for sprint two, and be more efficient with. As an individual I could better deal with frustrating issues. I got quickly discouraged by major issues that I could not solve, most notably with our SSL errors. My inability to switch tasks held me back from one of my sprint goals, because I was determined to solve an issue that I did not have all the tools to solve. I could also better document my work, as going into this retrospective I realize that outside of completed issues there is very little documentation of what I had done. 

The apprenticeship pattern that best describes my work in this sprint is Confront Your Ignorance. This fit because the work done with the staging and deployment server is something entirely foreign to me. To be able to approach the work, I had to swallow my pride and confront that I know nothing about the topic. And to improve that I did research throughout the sprint to better understand how to make progress. Reading this pattern allowed me to reconceptualize my lack of knowledge into an opportunity.

My tasks:
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/6
This was my first task in the sprint. I installed docker and docker-compose on the server, and got Thea’s Pantry running on our server. I have since tweaked our compose file and have been working on getting the back-end and front-end to connect on the server.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/16
Most of my sprint was spent tackling the issue of SSL certifications for our server. I made progress in getting a self-signed certificate to bind to the IP, but I could not access the index file to allow the front-end to work with the volumes used for the nginx config and certs.
https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/4
Here I made a minor contribution in establishing how we should go about implementing CI/CD, I researched how we could make it work and presented it in class. In the future I plan to implement a Python script to aid Andrew in this task.

From the blog CS@Worcester – WSU CS Blog: Ben Gelineau by Ben Gelineau and used with permission of the author. All other rights reserved by the author.

Hoo boy, where do I even begin with my experience for the Sprint…

If I am to be honest, I felt like I didn’t contribute anything to this current sprint. At every angle I either was either unable to receive a task to do, or when I was, I failed to meet said task or it was taken over by someone else.

Do not get me wrong, I don’t want to blame my teammates at all, in fact, I feel as though my teammates have been quite supportive. But at times, I felt like our communication and divvying of workloads could be a bit better. I also want to admit, because of my other courses, I have been scrounging for time for working on this one, so whenever I have had a task, I’m unable to put a solid dent into it.

If I had work to show, I would absolutely show it here. But in all honesty, most of what I’ve done has just been helping others whose work I am unsure of as to where it is on GitLab, or if it has even been pushed yet. I’m aware that you have been pushing us to use all the features it contained, but we have yet to do so. The one thing I can say I’ve done and show is setting up an issue board for me and Jaylon on the Frontend, which I have been the only one to utilize thus far: https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/inventorysystem-category-based/frontend/-/boards

The other few tasks I was given, were as follows, and the reasons I wasn’t/didn’t do them is also listed.

• Create a Mock-up app for the scanner: Project was taken over completely by Jaylon.
• Implement a camera view into the web app: Also taken over completely by Jaylon.
• Download and inspect a MongoDB by OpenFoodFacts (https://world.openfoodfacts.org/files/api-documentation.html): Rendered useless by Marlon, who found something better as I was in the process of de-compiling the DB.
• Creating a README, and verifying our licenses: Small tasks that I honestly have no excuse as for why I haven’t done them. I really should at some point, but I’ve bee so focused on more important homework with due dates.

That last part is absolutely a major reason I feel lost, not only just because there’s a lack of communication and task distribution, but the lack of due dates for things makes me have no sense of urgency nor motivation, which is hard to generate for someone such as me with ADHD. Its no excuse of course, but it is absolutely a factor at play.

If I were to choose a pattern in specific from Apprenticeship Patterns, I would likely choose “Find Mentors” from Chapter 4. It discusses going down avenues not knowing where to turn to or what to do, even though it is a path others are treading. I feel as though this is a perfect summary of my situation during this sprint, and is something I will keep in mind going forwards in the next. Perhaps I should work a bit more closely with my Professor, and see if he has knowledge to imbue or assistance to give. I have already seem to have found a niche for this next sprint, with the design of our web app, so hopefully that ends up going much more swell that this week did.

If I were to say something positive about my team, however, I feel like when we meet up and work together, we are very strong and capable. It’s clear to me that everyone cares not only about our project, but each other. I have felt bad every time I end up late or absent from courses, as I feel like I am unable to contribute to this positive work effort our team is pushing. Hopefully in the future I can improve and build upon this, and make our teamwork even stronger.

Here’s hoping that the next Sprint goes a lot better!

From the blog CS@Worcester – You're Telling Me A Shrimp Wrote This Code?! by tempurashrimple and used with permission of the author. All other rights reserved by the author.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/guestinfosystem/guestinfofrontend/-/merge_requests/49

This is the link showing merged changes into main branch after testing. During this sprint, our team collaboration was strong, with regular meetings during class checking on our progress and open communication that helped us stay aligned. Additionally, our task management system in GitLab was highly effective, helping us track progress and ensure that every team member had a clear understanding of their responsibilities. Another success was our ability to quickly adapt to challenges. When any of my teammates encountered any problems, we worked together to identify solutions and implement fixes efficiently. This adaptability was important in maintaining our project’s momentum and meeting our sprint goals. Despite the successes, there were areas where I struggled. One significant challenge was time. Some tasks took longer than anticipated due to unforeseen problems, particularly when dealing with the display of the First Entry Date in the frontend. I made some changes in the GuestInfoComponent.vue and at first it wasn’t displaying the entry date. With more research, I figured I also had to make changes in the VerifyPage.vue file. With these changes, my Date of first Entry was displayed after making my changes. Looking ahead, there are several ways our team can improve. One is better estimation of task complexity, where tasks can be broken down further and allocate time for unexpected challenges. Reflecting on my own contributions, there are several areas where I can improve. One is time management. Allocating more time for testing will help ensure deadlines are met more comfortably. This I would say is something I am going to do better at in the next sprint, as I believe it will help enhance my own skills as a developer.

The Apprenticeship Pattern I chose is “Expose your Ignorance” pattern which encourages developers to openly acknowledge what they don’t know and actively seek knowledge. Instead of pretending to understand everything, developers should ask questions, collaborate with teammates, and use resources to expand their expertise. I chose this pattern because it closely aligns with my experience during this sprint. When working on merging my work to GitLab after I had completed my issue, I struggled with this and came across many blocks. Instead of immediately asking for guidance, I spent too much time doing it on my own. Eventually, when I reached out to a teammate, I realized how quickly I could have resolved the issue with just a simple discussion. This experience reinforced the importance of embracing learning opportunities rather than trying to figure everything out alone. Had I fully embraced this pattern from the beginning, I would have immediately sought help. This approach would have saved me valuable time and reduced frustration. Moving forward, I plan to be more open about my knowledge gaps, actively seek advice, and continue improving my problem-solving efficiency. This sprint was a valuable learning experience that highlighted both our team’s strengths and areas for improvement. While our collaboration and adaptability were commendable, we also identified opportunities to enhance efficiency and communication. On a personal level, recognizing the importance of seeking knowledge earlier will help me grow as a developer. By implementing these improvements, both individually and as a team, we can ensure even greater success in future sprints. I look forward to working on the next sprint and implementing more changes that will make this sprint easier.

From the blog CS@Worcester – Lynn'sBlogs by lynnnsubuga and used with permission of the author. All other rights reserved by the author.

GitLab Activity

Install npm JWT Library and handle validation on Mock FE/BE issue – created a file called checkRole.js that as of moment takes a token and decodes it, however since Keycloak is not configured yet with the backend, checkRole.js is still not setup for the verification of tokens.

Reflection on What Worked Well

This sprint, I found that my ability to collaborate effectively with my team improved. We established a structured workflow using GitLab issues and merge requests, ensuring everyone was aligned. Team meetings and project reviews were also particularly helpful in maintaining quality and catching potential issues early. Additionally, I felt more comfortable with our tech stack, which allowed me to contribute more efficiently to the project.

Reflection on What Didn’t Work Well

One of the biggest challenges during this sprint was time management and managing expectations of fellow team members. Balancing multiple tasks while delivering high-quality work proved difficult, especially when unexpected issues arose. There were also moments when communication gaps led to duplicated efforts or confusion regarding task ownership.

Additionally, an unexpected bug related to the jsonwebtoken library took longer to resolve than anticipated, impacting our overall sprint velocity. I underestimated the complexity of debugging the issue, and this resulted in delays. Moving forward, I want to improve my debugging strategies by breaking down issues systematically and identifying potential causes earlier in the process.

Another challenge was that some tasks took longer than expected due to unclear requirements. There were times when I started working on a feature only to realize later that I had misunderstood part of the implementation. This led to rework and inefficiencies that could have been avoided with better clarification upfront.

Reflection on Changes to Improve as a Team

To improve as a team, we need to refine our communication and task allocation strategies. One possible improvement is assigning issues to members with clear deadlines and deliverables. This would help eliminate the need to check in constantly about each other’s progress and give everyone enough space to focus on their designated tasks.

Additionally, we could establish clearer guidelines on documentation and issue tracking. Proper documentation would minimize misunderstandings and ensure that we have a reference point if any team member forgets certain project details. This could be as simple as maintaining a shared document with important technical decisions, dependencies, and any issues we encounter.

Reflection on Changes to Improve as an Individual

On a personal level, I need to deepen my knowledge of the technologies we are using and strengthen my overall web development skills. Additionally, I must improve my time management and prioritization strategies to ensure more efficient task completion. Allocating time for debugging and testing earlier in the sprint would help reduce last-minute stress and improve the stability of our work. I also plan to dedicate time outside of sprint tasks to learn best practices and gain a more comprehensive understanding of our tech stack. Finally, I recognize the importance of seeking help sooner when I encounter challenges, as doing so will allow me to work more efficiently and avoid unnecessary delays.

Apprenticeship Pattern: “Be the Worst”

Summary of the Pattern

The “Be the Worst” pattern suggests deliberately placing yourself in an environment where you are the least experienced or skilled person. By doing so, you expose yourself to opportunities for rapid learning and growth by observing and working with more skilled individuals. While this can be uncomfortable, it forces you to improve and challenge yourself continuously.

Why I Selected This Pattern

I chose this pattern because, during this sprint, I often felt like I was struggling to keep up with some of my teammates who had more experience with certain technologies. Instead of being discouraged, I realized that this was an opportunity to learn from them and elevate my own skills. Their feedback and insights helped me refine my practices and problem-solving approach.

How This Pattern Could Have Changed My Behavior

Had I fully embraced this pattern earlier in the sprint, I would have proactively sought out mentorship and learning opportunities rather than hesitating to ask questions. Additionally, I would have taken more initiative in tackling challenging tasks instead of sticking to what I was comfortable with. Moving forward, I plan to embrace this mindset and view my inexperience as an advantage rather than a limitation.

From the blog CS@Worcester – The Bits & Bytes Universe by skarkonan and used with permission of the author. All other rights reserved by the author.

GitLab Issues

SSH Keys:

https://gitlab.com/Libre

FoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/17

I research how to make ssh keys to make logging into the server easier. I created documentation on how and what commands to run to create the keys. Now everyone in the future can create keys to access the server in a safer manner. 

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/4

Researched into how git pipelines work. I looked into the gitlab_ci.yaml files because that is what I thought we would need. But it seems we’re living in the direction of cron jobs for CI.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/5

Tested nginx serving the basic webpage on my browser from the server.

https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/issues/18

Worked on trying to solve the SSL certificate problem with everyone else. 

Reflection

One of the things I think we did well as a team is making use of work class time. Often for our project we hit many roadblocks. We used the class time as a way to put all of our heads together to tackle a problem that was holding us all up. Especially in the first few weeks since I think we are all pretty new to this side of computer science. We would convene and help each understand things like docker-compose or port-mapping. Another aspect that I think we did well was our general attitude and teamwork. I think we were all willing to participate in the conversation and contribute. Though I will admit I was the quietest one. 

One thing I think we need to work on is gitlab issues. First, I think we need to split them up or maybe name them better. I think all of our issues are very broad so it’s hard to talk about what we did because there are so many layers to the issue. For instance, the SSL certificate implementation. It covers a lot of work and troubleshooting so it can be hard to talk about since work can change quickly. Maybe that’s the nature of our project, but I think it’s something we could improve on. On the same note for gitlab issues, you mention commenting on the issue so that it describes what we’ve done. I’m not sure if any of us have done that. And I’m not sure where to do it either. Some of the things I could work on for myself as an individual. I think I need to ask for help more often, either from my team or you. For when I’m stuck or I just need some direction on what to work on next. Sometimes it feels like I’m not doing enough

Pattern

The software pattern that I often talked about during the period of our spring was “Exposing Your Ignorance”. To summarize, in the software industry it is expected that we are professionals and are experienced in our area. However, that is not always the case. Especially for new apprentices like ourselves. It is important to accept that you do not know everything. So ask questions and swallow your pride to allow yourself to learn something new. I chose this pattern because I think we all were a bit inexperienced in this area, but for me especially this was very new. It felt some of this stuff I should have known or I wasn’t really all too familiar with it. Definitely never worked with it before. So very early on I had to accept that didnt much have much to learn as I went along. I read this pattern before the sprint, but I think it’s something I least thought subconsciously. I think it’s just something I incorporate into all aspects of my life. Skill and experience come from time and work. It’s impossible to know everything or understand everything at first. 

.

From the blog CS@Worcester – Code Craft by Kyle Tucker and used with permission of the author. All other rights reserved by the author.

In my CS-448 class, we are working with the Thea’s Pantry system. I was placed on the team that looks at the automated reporting system and we have just finished our first month long sprint. During this sprint one, the first issue I worked on was the Reporting Integration set up issue which was in the backlog from the last team that worked on it (https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/reportingintegration/-/issues/27). Then, after finishing with that, I took the next available issue that we had planned for this sprint and fixed that as well (https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/reportingsystem/reportingintegration/-/issues/29). After testing and requesting a merge for both of my issues, there wasn’t anything else that we had planned for the current sprint and I didn’t want to start on another month long sprint issue, so instead I helped my other teammates troubleshoot, checked their work, and looked into things such as how the final report file is formatted, what information it has, and how we would go about creating a file like that within the code.

I think what worked the best for us was our original plan at the start of the month so that we all knew what we needed to do and could focus on that. For the most part with most problems being from the project backlog, we didn’t work collaboratively that much as the issues were largely separate but during meetings, we would be able to teach each other about the different systems we were working on. We also were able to get all of our issues done with a little time to spare at the end that we used to further develop some of the small things we would have needed to do eventually anyways. As far as what didn’t work well, when starting to help my other teammates, I felt behind in understanding on the system they have been learning for a few weeks and had to catch me up. Fortunately, with the extra time we had, I and others were able to follow along with other’s progress and quickly gained at least a basic understanding of all parts of the system.

During the next sprint, an improvement that I hope we make as a team is to work more collaboratively, even if the problems we are working on are not directly related to development. We didn’t have much of a chance to work on direct collaboration, but for the next sprint given the opportunity now, I hope that we can progress as a team more so that specialized individual programmers. For myself individually, something that I aim to improve on is my workflow. Last sprint I would try to implement code and get it in a semi working state but then would have to go back and reference other parts of the project or research some other system that was involved. In the future I plan to approach the problems first with getting a full understanding of how the system will work when fully operational and then writing the code, rather than going back and forth between coding and learning.

For this sprint, I feel that the apprenticeship pattern that was most applicable to me was Chapter 2’s pattern of emptying the cup. The book’s author talks about this in the context of learning a new language which is somewhat true for myself as I am not very experienced in all the intricacies of how javascript coding works when developing a website. I felt that this pattern described my experience because I had to learn a lot of new systems that I hadn’t used much before. This is my first time working with RabbitMQ or MongoDB and to a lesser extent the workflow of docker and gitlab. Over time, I got better at using these applications but I had to spend time learning them without “working on” the project.

From the blog CS@Worcester – Computer Science Blog by dzona1 and used with permission of the author. All other rights reserved by the author.

Gitlab Deliverables:

• (Issue Board Maintenance): Throughout Sprint #1, I supervised the creation and progression of issues in addition to readjusting them based on our current scope. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/gitlab-profile/-/boards
• (CronJobs Research and Documentation): One of our goals of Sprint #1 was to research CI/CD, and CronJobs was a component of such.  https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/documentation/-/blob/main/Documentation/CronJobs.md?ref_type=heads
• (Set-Up Documentation): After our group installed Docker-Compose and established a connection to Thea’s Pantry’s FrontEnd, I created documentation walking through the steps on how we achieved this. https://gitlab.com/LibreFoodPantry/client-solutions/theas-pantry/deployment/documentation/-/blob/main/Documentation/Set-Up.md?ref_type=heads

Sprint #1 was a rocky path, but through our group’s collective efforts, we all learned new tools and skills we can implement in future sprints. At the beginning of this sprint, our group agreed that I would be the Scrum Master and, by extension, manage our GitLab activity. In hindsight, this was a perfect designation as I’ve had managerial experience in the past and continue to be a very organizationally driven worker. With these traits, I sought to make our workspace as clear and accommodating as possible, which would provide a strong foundation for our team to begin working. One area I could have improved upon is making sure everyone’s voice is heard. During Sprint #1, my confidence with Linux started at a 2/10, so over the next couple of weeks, I had to refresh my memory while learning new skills. Due to this lack of confidence, I was much more reserved during group conversations as I was trying to soak in as much information as possible. Consequently, I did not explicitly check if everyone felt as if their voice was being heard. Towards the end of the sprint, my confidence with Linux grew greatly. As a result, I was able to participate in group discussions and ensure that everyone was on the same page. 

As a team, our biggest developmental challenge was understanding when problems should be taken on individually or as a group. At the beginning of Sprint #1, my bias weighed heavily towards solving problems as a team as it would grant everyone equal opportunities to learn from hands-on experience. As we soon found out, this approach is costly in time and does not let people engage with topics that specifically interest them. The task that gave us the most hassle was getting the FrontEnd certified so that the Backend could connect with it. This task was our “group task”, which we used working classes to try and resolve. Beyond this “group task”, we each had individual tasks we would look into. This approach to distributing work across teammates and holding each other accountable for learning unique material has been effective so far. After learning a new tool or skill, I request that the individual creates documentation listing the steps or sources they referred to so that all team members have access to what the individual learned. So far, there have been no issues with this approach, and we will continue to refine it in Sprint #2.

As previously mentioned in my review of Apprenticeship Patterns, the pattern that has resonated with me the most this sprint was “Be the Worst”. This self-assessment pattern has allowed me to refresh my knowledge of Linux through completing tasks such as organization and documentation of our completed tasks. This pattern has the individual actively learn and listen to their teammates discuss current issues. From this assessment, the individual can learn from the shared knowledge of the group and will slowly catch up to their level of proficiency. In the case of Sprint #1, my Linux skills were beyond rusty, making me the least proficient in the group. Although I was not able to start helping on the server immediately, I was able to help record our steps. By doing so, I could educate myself on how we approached problems as they arose. Towards the end of Sprint #1, I found my confidence in using Linux and began contributing to the server.

Moving forward, I plan on interacting with the server more, and I have already begun that process by researching encrypted volumes. Additionally, I will continue to refine my skills as our group’s Scrum Master. Now that I am nearly as proficient as other members of my team, I can now focus on making sure we all understand our current goals and have everyone’s voice heard. In terms of teamwork distribution, we have struck a fair balance at the end of Sprint #1. If there is any issue in Sprint #2, I will have to reconsider how we organize and assign tasks. Fortunately, we now have assigned days for backlog refinement, so we can discuss what changes we would like to make during those periods.

-AG

From the blog CS@Worcester – Computer Science Progression by ageorge4756 and used with permission of the author. All other rights reserved by the author.