The Wednesday Wellness threads are meant to encourage users to ask for and provide advice and motivation to improve their lives. It isn't intended as a 'containment thread' and any content which could go here could instead be posted in its own thread. You could post:
-
Requests for advice and / or encouragement. On basically any topic and for any scale of problem.
-
Updates to let us know how you are doing. This provides valuable feedback on past advice / encouragement and will hopefully make people feel a little more motivated to follow through. If you want to be reminded to post your update, see the post titled 'update reminders', below.
-
Advice. This can be in response to a request for advice or just something that you think could be generally useful for many people here.
-
Encouragement. Probably best directed at specific users, but if you feel like just encouraging people in general I don't think anyone is going to object. I don't think I really need to say this, but just to be clear; encouragement should have a generally positive tone and not shame people (if people feel that shame might be an effective tool for motivating people, please discuss this so we can form a group consensus on how to use it rather than just trying it).
Jump in the discussion.
No email address required.
Notes -
I'm not really convinced I need to be more than "experienced computer user with good taste" in the end. Probably not much more than a product manager.
I was mentioning io_uring or JITs etc as examples of extreme customizations the agents can do. But if you just tell it what you want and then complain "it's not fast enough, make it faster" it will, on its own, come up with and implement optimizations. The standard ones like better algorithms or pre-computing stuff, but they will get increasingly sophisticated and extreme if you keep saying "make it faster".
My specialized knowledge helps us not get painted into a corner as much, but does it matter when the paint dries instantly and it can repaint the entire house in minutes?
My biggest advantage for now may be that I can approximate in my head the theoretical limit for how fast something could be physically driven on the hardware, so I'll know when to stop saying "make it faster". I'll also know that when the coding agent says "I'm going to bake in hardware assumptions and weaken consistency models" that it might be worth stopping as well.
But this edge won't last for too long.
More options
Context Copy link