1. Generate unit tests beyond the best-case scenario. Analogy: Netflix's Chaos Monkey
2. Incremental cleanup: I also use it as a fancier upgrade of Visual Studio's Code Analysis feature and aid me in finding areas to refactor.
3. Treating the model as a corpus of prior knowledge and discussions, I can form a 'committee of agents' (Security, Reliability, UX engineer POVs) to help me view my work at a more strategic level.
My additional twist to this is to check against my organization's mission statement. That way, I hope I can help reduce mission drift that I observe was a big issue behind dysfunctional companies.
> Choosing not to pirate is just an objectively wrong choice. It's a worse experience, with worse quality, worse availability, and at a higher price tag.
Choosing not to pirate and not to consume simultaneously is not necessarily a wrong choice. A difficult one? Yes. But I propose that it could be beneficial for your mental (and maybe physical) health.
The winning move is not to play. The HDMI Forum (and other orgs that behave similarly) prey on our desire for the most/best/(insert superlative here). I get that there's no free lunch. It is also true you see a lot of initiatives and projects do a lot of collective good while demanding much less.
From what I remember, in past bubbles that burst, everyone thought stocks will go up forever.
So, if people are wondering out loud (with widespread traction) if there's a bubble, there's probably not one. It may be self-fulfilling. The awareness of a potential bubble influences us to be more cautious.
Changed from Windows 10 to an Ubuntu with beefy specs. When I saw firsthand the improvement of the user experience, I felt the year of the Linux desktop is nigh.
Seconding steps 1-2. I don't do step 3 because I want to whisk the eggs. It takes some practice, but the end result is worth it. The eggs taste better when cooked on a stainless pan.
ChatGPT's style is like an academic writer's. It's tone and word choice are same-ish across various subjects, but it's coherent and easy to understand. In retrospect, I've seen papers that would pass as GPT-created if they're written after 2022.
I can tell technical papers influenced ChatGPT's outputs the most. Most of the articles generated using it may be regurgitated, but I can't deny how easily digestable the info is when presented that way.
2. Incremental cleanup: I also use it as a fancier upgrade of Visual Studio's Code Analysis feature and aid me in finding areas to refactor.
3. Treating the model as a corpus of prior knowledge and discussions, I can form a 'committee of agents' (Security, Reliability, UX engineer POVs) to help me view my work at a more strategic level.
My additional twist to this is to check against my organization's mission statement. That way, I hope I can help reduce mission drift that I observe was a big issue behind dysfunctional companies.