[09/12/2023] Build 2023.6.1.219, j Silvestri Application Assembly BETA v 2023.6.1.219 Release: Updates to Bugs, Fixes & Releases Sections (ongoing updates), in addition to Producing Latest Resumes, Update to Occupation Details, and More

Current Workflow State:
Completed

Web/Mobile Developer:
Jason Silvestri

Primary Reason for Release:

The Application Assembly jSilvestri BETA v 2023.6.1.219 Release handles This release (2023.6.1.219) handles the Bugs, Fixes & Releases section ongoing updates, in addition to producing latest resumes, update to Occupation Details, and more.

Completed Action Items:

The action items with the workflow state Completed that made this release possible are as follows:

In-Work Action Items:

The action items with the workflow state In-Work that contributed to this release being possible are as follows:

In Closing:

This release has already been deployed to Production successfully!

I expect the BETA v 2023.6.1.220 release to include the final implementation of one or more action items that still had the workflow state In-Work described in this build.

[09/09/2023] Build 2023.6.1.218, j Silvestri Application Assembly BETA v 2023.6.1.218 Release: Not a Good Day to Be a Door Dasher DoorDash blog post update and creative, Monster TinyUrls replacement, & Work Offer Solicitation Responses

Current Workflow State:
Completed

Web/Mobile Developer:
Jason Silvestri

Primary Reason for Release:

The Application Assembly jSilvestri BETA v 2023.6.1.218 Release handles the Door Dash End Blog Post (a.k.a., Not a Good Day to Be a Door Dasher), as well as updating a new version of Monster resumes, Work Offer Solicitation Responses, etc.

Completed Action Items:

The action items with the workflow state Completed that made this release possible are as follows:

In-Work Action Items:

The action items with the workflow state In-Work that contributed to this release being possible are as follows:

In Closing:

This release has already been deployed to Production successfully!

I expect the BETA v 2023.6.1.219 release to include the final implementation of one or more action items that still had the workflow state In-Work described in this build.

[03/14/2023] Build 2023.3.2.040, j Silvestri Application Assembly BETA v 2023.3.2.040 Release: Changes relative to all major View Data Objects we are using in META

Current Workflow State:
Completed

Web/Mobile Developer:
Jason Silvestri

Primary Reason for Release:

The Application Assembly jSilvestri BETA v 2023.3.2.40 Release focuses on changes relative to all major View Data Objects we are using in META.

Completed Action Items:

The action items with the workflow state Completed that made this release possible are as follows:

In-Work Action Items:

The action items with the workflow state In-Work that contributed to this release being possible are as follows:

In Closing:

This release has already been deployed to Production successfully!

I expect the BETA v 2023.3.2.41 release to include the final implementation of most (if not all) action items that still had the workflow state In-Work described in this build.

Update 005. Added Epic Talent Acquisition to Final Offer Lifecycle Process Blog Post

Status: Implemented

Defnitely check out the blog post related to this updated, entitled, “ Jason Silvestri On Talent Acquisition to the Final Offer Lifecycle Process”. You have never seen a lifecycle created specifically for the lifecycle process of talent acquisition quite like this.
Please read the “Jason Silvestri on Talent Acquisition to Final Offer Lifecycle Process” article reference for more details.

Figure 5: Talent Acquisition to Final Offer Lifecycle Preview:

Update 004. Updated All Big Footer Sections to Include New Content

Status: Implemented

As shown in Figure 4 below, I updated all, what we call, Big Footers, to include new content, such as updates to social media followers, new Blog Posts & and of course the new Bugs, Fixes & Updates section.

Figure 4: Big Footer Sections:

Update 003. Added a Few New Blog Posts with More to Come

Status: Implemented

It has been a very long time since I made a blog post of any kind. Whether it is hunting for the next big contract or fulltime, working with Recruiters and Talent Acquisition Specialists around the World (literally) or on site working with one of their clients, there really hasn't been enough time to make the time required to make a post. In my defense, however, as shown in Figure 3 below, I really do not want to make blog posts just because and/or for SEO (Search Engine Optimization) purposes. The content matter must.... Well... Matter.

Figure 3: New Blog Posts:

With that said, I have a couple really important topics with respects to the complex Lifecycles and Workflows I developed, and use, every day with recruiters and talent acquisition specialists to obtain that offer letter all sides once, to the new and exciting development technologies I use today, like Asp.NET Core 6 & Blazor, both 2022 versions of the .NET flavor, that is so powerful, it is now 7x faster than Java, NodeJS and many more technologies. It is baffling to say the least and a very exciting time to be a developer. Check out my blog section for more details.

Update 002. Added a New Bug Fixes and Updates Section to the Application

Status: Implemented

You guessed it! Yes, as shown in Figure 2 below, the section you are viewing now is the new Bugs, Fixes and Updates section of the jSilvestri.com Web Applicaiton. Most recent bug fixes and updates will be found here.

Figure 2: New Bugs, Fixes & Updates Section:

Bug 004. If I fill Out the Contact Form and try to Submit It, I get an Error.

Current Workflow State: In-Work

If a user tries to fill out the contact form to reach out to us for support or service, they get an error. The mobile and web application experiences do make the user aware of the issue, explains that the team is working on the issue, and that they do not need do anything more to help solve the issue. Still, they cannot submit the form! This is an issue that is unacceptable. The plan is to…

The Problem:

There is a bug where any user that tries to use the Contact Form gets an error upon submission of that form.

Yes, if a user tries to fill out the contact form to reach out to us for support or service they get an error. Conversely, the mobile and web applications do make the user aware of the issue, explains that our team is working on the issue, and that they do not need do anything more to help solve the issue. Still, you cannot submit the form! This is an issue that is unacceptable, and it is being worked on as we write.

The steps we had to take to replicate the issues are as follows:

In Closing:

As soon as we can release a fix to this issue we absolutely will deploy to production. It is an obvious bottleneck that should not be, and is not, acceptable.

I expect the 2023.0.0.22 release to have this final implementation. It will not be considered a bug fix. If anything, an update.

Top

Social Networks Promoting this Update

The Social Media Networks organically promoting this fix are as follows:

1. LinkedIn
2. Twitter

Bug 003. Anywhere a Phone Number is Required You Must Provide Hyphens for Phone Numbers to Validate Successfully, and for the Form to Submit.

Current Workflow State: Completed

This release is solely to make a fix to a bug that went from a medium, important enough, “We’ll get to it soon fix” priority, to a full-blown, critical “43% of all users can’t submit a contact form”, with the issue effecting all end user experiences that rely on their iPhone 12+ Pro (or lower) phones to submit our primary Contact forms successfully. Like, wait, what? Right… Exactly…

The Problem:

There is a bug where any phone number used, on any form across our mobile & web applications, encounters the issue where the phone number must have hyphens that separate each phone number segment of their phone number, for it to be valid. The form will not submit until you use the hyphens. This went from a "I'll get to it" bug to a critical "All iPhone users can't submit forms" issue, within literally a minute or two upon discovery, as most errors of that caliber do, after Bella Silvestri, a member of my personal Q&A team, discovered the issue when testing the primary contact form just hours ago, using versions of iPhones.

The young and talented Bella Silvestri discovered that iPhone users, using iPhone 12 or lower, do not have the characters (like hyphens) within the native, digital, keyboard/keypad, when using their native phone's browser’s to fill out common forms you find on most sites. In our case, it was the very important Contact form.

The steps we had to take to replicate the issues are as follows:

The Solution:

There is a bug where any phone number used, on any form across our mobile & web applications, encounters the issue where the phone number must have hyphens that separate each phone number segment of their phone number, for it to be valid. The form will not submit until you use the hyphens. This went from a "I'll get to it" bug to a critical "All iPhone users can't submit forms" issue, within literally a minute or two upon discovery, as most errors of that caliber do, after Bella, a member of my personal Q&A team, discovered the issue when testing the primary contact form just hours ago, using versions of iPhones.

The young and talented Bella discovered that iPhone users, using iPhone 12 or lower, do not have the characters (like hyphens) within the native, digital, keyboard/keypad, when using their native phone's browser’s to full out common forms you find on most sites. In our case, it was the very important Contact form.

To aid in the QA (Quality Assurance) of our mobile & web applications, and to prove this fix is present in this build, the steps you can take to replicate the proof-of-the-fix are as follows:

In Closing:

The one thing I would add, better said, the one thing this fix doesn’t have, (e.g., a fix I want implemented as soon as possible), is that there is nothing stopping a person from using a combination of those characters that make up the conditions, and although still considered valid phone numbers, inconsistent, nonetheless. For example, using a hyphen to make the first delimiter separation of numbers, followed by a space instead of a hyphen to make the next, or vice-versa, and so-on, and so-forth (i.e., 508-555 1212, 508555-1212, etc.). Are these valid phone number formats? Sure, but it’s the inconsistency of the data that might one day cause a conflict with this process or that process, even if the current build handles the issue gracefully like it does now.

I expect the 2023.0.0.22 release to have this final implementation. It will not be considered a bug fix. If anything, an update.

Social Networks Promoting this Update

The Social Media Networks organically promoting this fix are as follows:

1. LinkedIn
2. Twitter

Bug 002. Password Resets Don't Work. I Don't Receive an Email and I also Get an Error Page.

Current Workflow State: Completed

Users reported having issues with contacting the jSilvestri.com team initially. Then, however, the issue became a broader emailing issue. New visitors and existing users were having problems with things like doing a password reset, which is actually a more important issue and took priority.

The steps we had to take to replicate the issues are as follows:

Figure 1.1: Before Submission

Figure 1.2: After Submission

Figure 1.3: Final Fix - Confirmation Page

Figure 1.4: Final Fix - Email Sent

It ended up being an issue with Azure and a subscription service with respects to our primary Email API service. Figure 1.1, Figure 1.2, Figure 1.3 & Figure 1.4 above shows the progress of change.

Now, as shown in Figure 1.3 above, if you are trying to reset your password and you submit the form with appropriate information, you should see a page that tells you an email was sent. Most importantly, you should now receive an email with instructions on how to reset your password as well, as shown in Figure 1.4 above.

Social Networks Promoting this Update

The Social Media Networks organically promoting this fix are as follows:

1. LinkedIn
2. Twitter

Top

Bug 001. Home Page Blog Posts Section Links Don't Work

Current Workflow State: Completed

You have no idea how happy I am this is fixed! This problem has been around since the release of the jSilvestri.com web application. It also haunted my dreams. The issue was that no one could click links off to new blog posts. However, mobile device users could touch and click. The issue was on tablet and desktop computers in specific.

Figure 1.1: Before:

Figure 1.2: After:

It ended up being a bug in a 3rd party helper script, Owl Carousel, and it took some serious digging and custom updates to the JavaScript original source code. Figure 1.1 & Figure 1.2 above shows the change.

Aside from the actual bug fix, I also cleaned up the post, including copy-writing, look and feel, content positioning and more, as shown in After shot, above.

Top