My oh shit moment was when I thought it was going to be the future but it ended up leaving me disappointed, frustrated and annoyed. It's closed down tech, stealing work, ruining our climate and it doesn't work remotely as well as advertised.
It's hard enough to get the same model to be consistent around it's vision let alone multiple of them.
I'm building an EMR and the other day asked Claude what a decent model would look like for capturing wound orders. Then, I took the output, started a new session and asked the new session to critique that model and the response made me want to pull my hair out. It blasted the model from it's former self and suggested making a ton of updates.
I'm sure more scoped tasks would fair better, but it was pretty frustrating.
> Then, I took the output, started a new session and asked the new session to critique that model and the response made me want to pull my hair out.
I do this with all my important code, before I’ve even looked at it. And not just a critique, I ask “does this solve the problem X and was it built to spec Y”. Then I do my own review once the robots stop arguing.
If your expectations are that the quality of the code matches the confidence level of the robot’s tone, you’re gonna have a bad time.
If I don't see the point of Elixir, or I don't like it, or I simply straight up hate it, why would I go into HN submissions about new Elixir versions and spew my personal opinion that has nothing to do with the topic at hand?
You can just skip commenting unless you have something actually useful to add. Even if it's criticism of the specific thing, but at the very least make it on topic instead of general digressions that just add noise to the conversation.
Seems pretty useful to be able to write your documentation videos as steps and generate new videos everytime the platform changes. Let’s say you have 200 videos showing how to do different things and now the UI changes.
You can either leave the videos as is (and get more confused customers) or you can spend a lot of hours recording 200 videos again. Or you can run this and get the 200 videos done in the background. Let’s say that your app is changing every month because you are early in your iteration. That is a lot of time saved every month.
Say you have documentation with a video showing the user how to open a page, click a button, scroll, etc. Instead of having to re-record those videos every time you update the UI you can use this library to automatically recapture it on every push.
Firstly, you had to pay so much money for that screen that you had to consider buying a new device.
Secondly, Apple Products seem specifically engineered to easily break catastrophically (see SSD power supply below speaker grill, zapping the NAND modules if liquid enters the conveniently placed holes. Or a loose metal plate slicing a crucial ribbon cable when the phone was dropped. And many more such cases
This mix of overly fragile design and ridiculously expensive first-party repairs combined with parts pairing and the resulting inability of third-party, non-apple-certified repair shops to level the playing field is what I call a scam.
reply