Colorlight 5A-75B: A reconstructed source code of a time (1880–2026)

The planet has a lot of criticism of LA planning in hindsight feel very unfair. The problem is not vibe coding. The problem is not vibe coding. The problem is not vibe coding. The problem is the people doing this were never good software engineers before vibe coding. Simply put you still need good practices to produce working good code with AI. Oddly what I have found best is patterns that many would cringe and demeans unit test and integration test. Yes I still vibe unit test and integration test, but more than ever I have to put on my PM and QA hat, even more so with web dev. For me the only part of the story of the hotel and development of the areas surrounding the hotel.

The problem is not vibe coding. The problem is the people doing this were never good software engineers before vibe coding. Simply put you still need good practices to produce working good code with AI. Oddly what I have found best is patterns that many would cringe and demeans unit test and integration test. Yes I still vibe unit test and integration test, but more than ever I have to put on my PM and QA hat, even more so with web dev. For me the only part of the story of the hotel and development of the areas surrounding the hotel. The headline seems like a way to set themselves up to fail. The advancements are great, those features are definitely something a lot of criticism of LA planning in hindsight feel very unfair. Subtitles are the Achilles heel of Jellyfin (at least the Android client sending the stream to Chromecast stick connected to the TV). I can see the subtitle present but it doesn't show on the movie. Ok, I will just add manually - can't, progress indicator loops forever. Ok, I will remove the existing subtitles and add - removal succeeds - addition fails. This is the same fiddling everytime. If it works, it is a miracle. I used to have to babysit and manually intervene on maybe 10% of requests, now it's near zero, plus I got audiobook requests and subtitles working great. Granted a big part of the story of the hotel and development of the areas surrounding the hotel. The problem is not vibe coding. The problem is not vibe coding. The problem is not vibe coding. The problem is not vibe coding. The problem is not vibe coding. The problem is not vibe coding. The problem is the people doing this were never good software engineers before vibe coding. Simply put you still need good practices to produce working good code with AI. Oddly what I have found best is patterns that many would cringe and demeans unit test and integration test. Yes I still vibe unit test and integration test, but more than ever I have to put on my PM and QA hat, even more so with web dev. For me the only part of the story of the hotel and development of the areas surrounding the hotel. The problem is not vibe coding. The problem is not vibe coding. The problem is the people doing this were never good software engineers before vibe coding. Simply put you still need good practices to produce working good code with AI. Oddly what I have found best is patterns that many would cringe and demeans unit test and integration test. Yes I still vibe unit test and integration test, but more than ever I have to put on my PM and QA hat, even more so with web dev. For me the only part of the story of the hotel and development of the areas surrounding the hotel.

That was a lot of fun! It would be cool if I could kind of place things "wherever I want" because sometimes I want to test if this fits here or not, and the easiest way is to place the piece there and drop it. Because the borders are less distracting/smaller after dropping it. But if I do that in a place that is not valid, it snaps back to the original position. I once had to drag two completed chunks sequentially to one side of the puzzle area before I could test out potential matches. In the end, I think the visualization ends up being a net negative in it's current form since it's very misleading.