.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: After staring at the domain space for what seemed like an eternity yesterday, I finally broke through the analysis paralysis and designed a new model for the product content files used in the New Publishing Wizard. It's essentially a model rewrite, and I feel much better about its design. It's a bit of a detour from the quality assurance passes, or not. The point of the quality assurance passes is to assure quality, after all. Overall, not much has changed from the previous model, but the changes made will really help with the friction points currently experienced, namely the signatures being applied to non-image file types. It will also address the "Jenga"-like nature/feeling of the current design. Now is the fun part: completing the model and sending it through the components that work with it. That will be the goal for today and tomorrow. Hopefully, there isn't too much grief around this. 🤞 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An external shot of a futuristic space station in another universe made of shiny bright neon glowing metal, prominently featuring bright glowing contrasting neon colors, epic lighting, there may be a Dyson sphere nearby --ar 9:16`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: I'm OK with a little "Jenga" in my code, and it seems like it's always a process in monitoring how much chaos is in there, but sometimes it gets to a point where one block is too many for my tastes, and that is what happened yesterday with the New Publishing Wizard content model. Well, it's not all THAT terrible, but it could use one more pass now that everything is mostly settled. The signatures were a late (and valuable) addition, and there have been changes with how we use preview/display files. It's probably worth going through there and getting that all squared away before the big release. It's another hiccup in the schedule, but hey, two years into this rewrite, that seems to be par for the course. 😁 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An internal shot of a futuristic space station in another universe made of shiny bright neon glowing metal, prominently featuring bright bold contrasting glowing neon colors, epic lighting, there may be a Dyson sphere nearby --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: I was able to dig into the signature fixes yesterday, but unfortunately, I found more issues. I am sort of doing a facepalm somersault (or somersaulting facepalm?) of what I actually accomplished here. 😅 Signatures work great on a new product that is an image, but they do not for anything else. I am not sure how that slipped through, but I am taking care of it now. So today will be focused on getting signatures to work on all product types on a new product, and then I will work on reissuances. Hopefully, with a little luck, I will get through this today. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `vibrant digital cityscape of A sprawling metropolis on a distant alien planet, viewed from orbit, featuring towering spires, hovering traffic lanes, and massive holographic advertisements, all radiating bright bold beautiful contrasting glowing neon colors, extraordinary painterly photorealism , exquisite detailing, epic postcard composition --ar 9:16`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: Work continued yesterday on the user experience details around signatures in the New Publishing Wizard. Specifically, when the user follows the link to define their signature and then returns to the wizard, we detect any changes and apply them accordingly. There's been a lot of improvement around the model design around this, too, and a lot of code has been (thankfully) removed, so I took some time to clean up code and remove unused/unnecessary parts as well. There's still work to be had here, however. Signatures work great on a new product, but reissuances are kind of a disaster and need further analysis. Recall that for a reissuance, we use previously created and hosted files so as not to re-charge the customer. But what happens when a signature is changed/made in the meantime? Well, that means the image needs to be regenerated, which means a new image, which means a new charge. Those details are tricky, huh! This is the life I lead now. 😅 So, I need to find a way to handle this scenario. That will be my goal focus for today. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `a comic book illustration using inking pens and black fine-liner pens for outlining , depicting A sprawling metropolis on a distant alien planet, viewed from orbit, featuring towering spires, hovering traffic lanes, and massive holographic advertisements, all radiating bright bold beautiful contrasting glowing neon colors., on glossy comic paper stock , extraordinary comic photorealism , exquisite detailing , layering of saturated colors for depth and shading , smooth noiseless digital textures --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: Work continued yesterday on the re-issuance quality assurance passes, and I was finally able to square away all the identified state issues. Now the reissuances work alongside the issuances in the New Publishing Wizard, which is by far and away our most involved view in the application. With that, Quality Assurance passes for v2 continue. I will start by ensuring beneficiaries continue to work as expected and that those key scenarios remain intact for v2. That will be my focus and goal today. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An awesome epic profile background for social media, featuring a scene in space with a space station and a cool starship, based on the series Expanse, with a hint of The Fifth Element, prominently featuring bright bold contrasting glowing neon colors --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: Work continued on the Re-issuance story, and I landed on some interesting bugs with the signatures that I am looking into now. Apparently, the re-issuance screen didn't like the new signatures feature we added earlier this year, so I have to get that squared away. That will be my focus here today. Outside of this, making some good progress and cleaning up a lot of bugs/issues as I find them. For the most part, everything is working well and feeling great. 👍✨ #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An epic feature shot deep of space, prominently featuring bold, bright, colorful, glowing, contrasting neon colors --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: Dang, a bit of a rollercoaster yesterday, as I managed to address a bunch of display/rendering issues with the New Publishing Wizard while testing the Re-issuance story. THEN I found out the model no longer worked with the reissuance due to "optimizations" made back in January to help simplify the model. Yes, over-simplified and broke the thing. Fortunately, I was able to restore the previous design with very little effort (20 minutes), and I was AMAZED to see the re-issuance work complete without any errors after standing it back up. 🤯 Yes, roller coaster indeed. Well, I am ironing out the wrinkles here with v2, which is the whole point of these tests. I am feeling much better now about re-issuance, and recalls work as well. I will test a few more scenarios around re-issuance today and then move on to beneficiaries and the proofing system. Then it's the biggie, the user merge story, which is far and away the biggest story we have. I should have testing done either tomorrow or Monday if all goes well. 🤞 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An external shot of a futuristic space station in another universe made of shiny bright neon glowing metal, prominently featuring bright glowing contrasting neon colors, epic lighting, there may be a Dyson sphere nearby --ar 9:16`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: Finally, some good testing yesterday without *much* friction, but I did encounter caching issues with our new v2 caching setup. We're using Redis now, which is a little different from v1. So we need to make sure that when certain events occur, invalidation occurs as well. In this case, when a license is transferred, we want to ensure that any collection views for that license are cleared by both the sender and the receiver. I got that working easily enough, but realized that the invalidation was too broad in other areas. So, I need to find a way to ensure that when invalidation clears, it only clears the subset that needs clearing, not the entire set. That will be my focus for today. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `iridescent holofoil highlights shinmering, sticker illustration of futuristic space station from another universe in hyperspace, prominently featuring bright bold beautiful contrasting glowing neon colors , clean crisp black outlines, clean modern design --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: Testing didn't go as well as I had hoped yesterday, as I faceplanted directly into a rendering bug. I suppose that is to be expected after all the modifications over the weekend. I did manage to fix some issues, but a tricky one now persists, which I hope to resolve today. Then, it is back onto testing v2 as a whole and all its major/minor scenarios. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `a fleet of starships in peaceful transit, prominently featuring bright bold beautiful contrasting glowing neon colors, in the style of California plein air ,extraordinary painterly realism , exquisite detailing,layering of colors for depth and shading,clean tones no yellowing , color palette uses sandy browns eucalyptus greens and cobalt blues --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: Some good progress yesterday as I wrapped up a lot of the outstanding quality-related issues and actually started testing, fixing up a few issues along the way. Everything seems to be working well with the new improvements, and I hope this continues. Today should be focused on more testing and getting all the major scenarios of v2 completed at least once. I probably should have done this before data migration, but there were model changes during this process, so we're at a chicken-egg sort of deal with that. Well, in any case, the testing is finally being done now, and that will be the focus here. Once this is complete, I will resume data migration, which was going well in its own right, needing only file transfer to be completed. Overall, I am feeling pretty good about the quality of v2, and I hope I feel the same way about this after some testing today. 🤞 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `mixed media , starship from another universe in hyperspace, prominently featuring bright bold beautiful contrasting glowing neon colors , created with smooth even water-soluble pastels using crisp linework and fine-tipped saturated alcohol markers for atmosphere and highlights with no drips or runs, extraordinary photorealism , exquisite detailing, seamless transitions layering of colors for depth and shading , smooth noiseless textures --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes - Visual Glitches Notes: I spent another day working on the visual rendering issue and became more acclimated to the core issue. I am not sure how we escaped this with v1, but a LOT has been done with Blazor rendering in v2 to reduce the rendering/flickering. Well, somewhere along the way, I did too good a job of this, because elements now render with their loading screens, and these screens are smaller than the final rendering. This is OK for the first render, but for subsequent renderings (think: back and forth on the mouse, a particular use case when you are scanning/exploring catalogs) this causes the browser to land on a different place than where you left it because the content isn't there yet. There are several ways of dealing with this, and I am trying to land on the best one. This may take another day or so as I wrangle the details. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An epic feature shot deep of space, prominently featuring bold, bright, colorful, glowing, contrasting neon colors --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Quality Assurance Passes Notes: I got caught up yesterday in a blasted rendering issue with the browser. The browser works awesomely and is by far my favorite platform, but it does have its moments, and yesterday was one of them. The. entire. day. was spent figuring out why the scroll position does not retain its accurate value when navigating back and forth. The scrollbar jumps to an unexpected location, which is unacceptable, especially on the front page. I unfortunately left yesterday without much of a resolution. I hope to continue today and figure out what is happening here. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An external shot of a futuristic space station in another universe made of shiny bright neon glowing metal, prominently featuring bright glowing contrasting neon colors, epic lighting, there may be a Dyson sphere nearby --ar 9:16`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration - Quality Assurance Passes Notes: Yesterday was spent migrating old code over to the newer program initialization code that I have had for some time now for client work. Everything was migrated without any issues, which always makes me do a double-take. 😅 Past this, I started weaning down the few items I have noticed on my TODO list and made some good progress there, too. There are a few issues left, and after that, I think I am going to start running quality assurance passes on the v2 codebase. I should have done this before I did data migrations, as I have noticed a few bugs due to the new code. Once I have everything squared away there and feel everything is in place, then I will continue data migrations, which should be around this weekend. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An internal shot of a futuristic space station in another universe made of shiny bright neon glowing metal, prominently featuring bright bold contrasting glowing neon colors, epic lighting, there may be a Dyson sphere nearby --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration - Quality Assurance Tasks Notes: I spent yesterday dealing with some outstanding quality assurance issues. The solution as we have it now has four major applications, and they are all based on .NET5 project startup mechanisms. Yeah, a little old. I have a new .NET9-10 way of initializing projects, and have been using it in client work. So I spent some time yesterday organizing the Gateway (www) project to get it up to date. There's a lot of work in there, but I was able to get things migrated. Today should be more of the same here to get the other projects upgraded. Once that is complete, I will get back on track with the Data Migration story. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `a 90s anime cell shaded illustration of futuristic space station from another universe in hyperspace, prominently featuring bright bold beautiful contrasting glowing neon colors, created with smooth even saturated fine-tipped Nijii markers , extraordinary bbq photorealism , exquisite detailing a crisp clean linework , layering of saturated colors for depth and shading , clean tones no yellowing --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration - Product Display Notes: It's rare that a new feature (or fix -- feature fix?) goes as smoothly as this one did. I was able to complete the Product Display adjustments yesterday, and we now have the ability to let users choose their preferred product display when they publish it. For editing this display, I chose to keep this functionality at the publish level. We have a confirmation checkbox to ensure the user understands that it cannot be changed. Not the most ideal experience, but it's OK for the first pass. Besides, we have really addressed many of the issues that caused problems with product displays anyway. In some ways, I think I am battling ghosts with getting this in place. 😅 But it's a difficult problem, and I think I finally got it squared away... or squared enough for the release. Beyond this, I also allowed the user to edit the Generator used on their product after the fact while in the Edit/Manage issuance. I think this may be a more real problem than the Product Display. The generator is there, but I am sure people will miss it if they are not looking for it. Now they have a way to apply this if they miss it after the first publishing. I found some bugs yesterday while doing this. I will attend to these today and finally get back to data migration. 👍✨🚀 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `a split digital image , starship from another universe in hyperspace, prominently featuring bright bold beautiful contrasting glowing neon colors, the entire left half of the image is rendered only in glowing gold 3d wireframe meshes , showcasing the lines and vertices of the hollow mesh objects, striping away textures and color , while the right side of the image is beautifully rendered digital art , seamless transitions. extraordinary photorealism , exquisite detailing --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration - Product Display Notes: Progress continued as expected (for a change 😅), as I was able to complete the Product Display story yesterday for new products. Now, when the product has multiple display files, the user can select which one they want to serve as the file displayed in the general marketplace. I am happy not only with this solution but also with how quickly I was able to implement those adjustments without many side effects. The New Publishing Wizard code is also greatly simplified, as I ended up removing a bunch of it. All around, this feature is much simpler than before, and that is a good feeling. What's left? While we have this working for new products, I still want to allow the user to select a display file after the product is published. I will look into this today. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `prompt:mixed media, a fleet of starships in peaceful transit, prominently featuring bright bold beautiful contrasting glowing neon colors , created with a blend of glossy acrylic paint markers and smooth saturated even Nijii markers, seamless transitions , extraordinary natural photorealism , exquisite detailing , layering of colors for depth and shading --ar 9:16`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration - Product Display Notes: Progress (thankfully) continued at a good clip yesterday, as I was able to get the new Product Display functionality bolted into the New Publishing Wizard without much fuss. This has actually been a rewarding effort, as it has greatly simplified the wizard and allowed me to remove a lot of code. I was able to create a new order and send the necessary data to the API, which is where I wanted to end the day before resuming the server integration today. I should be able to get this done, which will mark the first portion of this story complete. Then it will be a matter of revisiting the Edit/Manage Issuance screen and enabling the Product Display there. I am feeling fairly confident I will have this completed this week. 👍 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An awesome epic profile background for social media, featuring a scene in space with a space station and a cool starship, based on the series Expanse, with a hint of The Fifth Element, prominently featuring bright bold contrasting glowing neon colors --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration: Product Display Notes: Work started on the Product Display story for Data Migration yesterday. I made a good deal of progress after spending some time with analysis to figure out the best path forward. We have five file types: image, video, text, book, and audio. Both images and videos already work exactly as desired. Which is convenient, as they are also the most popular file types. 😀 Audio does not have a visual file, and we prompt for a cover instead. That will also stay intact, but I need to review the experience and workflow. However, the text and book file types were generating "sample" files that should really be our preview files, and that is what I ended up doing yesterday. It actually wasn't all that involved, and I was able to route the behavior to the appropriate process with little effort. I was able to greatly simplify the interface, too, which was riddled with complicated code. All of that is gone now, and everything is much simpler. We still have some issues presenting a dialog to the user when adding "non-visual" elements, and I hope to address this today. #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An epic feature shot deep of space, prominently featuring bold, bright, colorful, glowing, contrasting neon colors --ar 16:9`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration - Product Display Notes: Alright, after a week of unexpected effort on quality assurance, I finally cracked open the New Publishing Wizard to resume work on implementing a good solution for Product Display -- only to be punched in the face by even more bugs. 😅 These were not terrible, but they were tricky, and ended up taking most of the day, unfortunately. I did a big refactor on how the wizard stores (and cascades) state to its children elements a few months ago, and that's what we're running into here. Despite the wrinkles, everything is working really well now. Our display refreshes are minor and expected now. In v1, our views/displays refresh terribly due to a few really bad bugs, mostly stemming from my misunderstanding of how Blazor rendering works. In v2, that's all been smoothed over, and our components refresh once or twice per action. So, that was good to at least see and verify. Now that those issues have been addressed, I can resume work on the Product Display and incorporate it. This is sort of an involved story, and I can see it taking the next week easily. It will impact how files are saved and categorized, particularly for file types that do not have a visual representation (e.g., audio). One foot in front of the other here... #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An external shot of a futuristic space station in another universe made of shiny bright neon glowing metal, prominently featuring bright glowing contrasting neon colors, epic lighting, there may be a Dyson sphere nearby --ar 9:16`

.@StarbeamOne Daily Status* Current Story: v2 Data Migration / Quality Assurance Notes: Finally, some good progress on the component rewrite for asynchronous operations yesterday, and I committed it. That only took 3 days. 😅 But that component is much better now, and we have one less asynchronous wrinkle to worry about in our solution. There is one more component to look at, then I need to figure out the exception-handling part of this, and I can finally mark this part as complete. THEN I can finally resume the data migration story and get those product display images in order. 👍 #DailyDeveloper #Status #BuildingInPublic * The attached image was AI-generated via #Midjourney with the prompt `An internal shot of a futuristic space station in another universe made of shiny bright neon glowing metal, prominently featuring bright bold contrasting glowing neon colors, epic lighting, there may be a Dyson sphere nearby --ar 16:9`