Deleted Comment
The feeling of seeing something the person will never use again is soul wrenching. I wept when I read the line "No salt. No salt means that he’s not cooking. He’ll never cook again."
The child is a ray of light for me whenever I see it, I hope the family can find a little comfort in this piece of him that will be brought into the world.
I have followed this story for a while now and wish the family a brighter path in the future. Thank you for focussing my thoughts on what is important, instead of the daily tech grind.
A few things:
* The main thing that makes ChatGPTs ui useful to me is the ability to change any of my prompts in the conversation & it will then go back to that part of the converation and regenerate, while removing the rest of the conversation after that point.
Such a chat ui is not usable for me without this feature.
* The feedback button does nothing for me, just changes focus to chrome.
* The LLaVA model tells me that it can not generate images since it is a text based AI model. My prompts were "Generate an image of ..."
Especially if there are complex dependencies between required containers it seems to be pretty weak in comparison. But i also only used it like 5 years ago, so maybe things are significantly better now.
I had a more recent 65" Vizio (2020, I think?) in my living room, which was also a great TV. It was something like $600 (crazy cheap for the size!), great picture, never connected it to the net, always worked like a charm. Was a great panel for my Nvidia Shield.
That TV was broken in an unfortunate incident involving a toddler and a thrown wrench, and was replaced with a similarly priced TCL TV (which was the best rated one in my price range on Rtings at the time).
That TV is nothing less than a hunk of shit - constant sound issues, molasses slow UI, built in Roku stuff is all crap. Picture is decent, but I liked the Vizio better.
I've often considered shelling out the big bucks for a better model TV, but given the industry trends I'm terrified of the thought of spending triple the price of my current TV and still hating it. Happy to pay for good quality, but just extremely skeptical of most offerings in the market these days.
Shouldn't have bought an expensive big monitor for work without OLED the year before, but i hear that OLED is not that great for close up text rendering.
I have a single ultra wide screen and would like to share a virtual area that has a normal size (16:9) with people via Google Meets, Slack, etc. Otherwise I have to share a window, stop, share another one etc.
Really bad, especially during some on call emergency session.
So far I couldn't make it work, only Zoom had this feature at some point but nobody uses Zoom where I have worked.
When congestion spikes start showing it is helpful to know some queuing theory to estimate how close the situation is to eating someone's weekend. Congestion collapses are an interesting time because most people don't know queue theory or how to reason using balance equations, it is possible to misdiagnose the problem or waste a stressful few days trying to work out a congestion situation by experiment.
Only exception is you should use my migration library [0] instead of tern — you don't need down migrations, and you can stop worrying about migration number conflicts.
One other suggestion I'll make is you probably at some point should write a translation layer between your API endpoints and the http.Handler interface, so that your endpoints return `(result *T, error)` and your tests can avoid worrying about serde/typeasserting the results.
[0] https://github.com/peterldowns/pgmigrate
I guess having a new up migration to cover the case is better, but its nice to have a documented way of rolling back (which would be the down migration) - without applying it programmatically. But it helps if other team members can see how a change should be rolled back ideally.