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 -
Without even getting into the "decade of legacy being heaped upon legacy" bit, boy, do I know how you feel! I tend to be insecure, and so I keep second-guessing myself, but there came I point where I wanted to slap anyone who uttered the word "microserives", still if the idea caught on to such an extent, it felt like I'm wrong / being arrogant. Then recently I saw a Twitter Space from around the time of Elon's takeover, where some hotshot hacker that briefly worked for Elon was tearing the Twitter architecture a new one, and one of his throwaway lines was "usually when you call something a microservice it's supposed to mean a 100 lines of code, not 10 000". Oooooh, suddenly it all makes sense. Maybe I'm not insane, and neither is the person who came up with the idea of microservices. Maybe if you have so many asynchronous jobs you can't trace where the bit of data that interests you came from without wanting to claw your eyes out, it's the architect that needs to be given a gentle push down a flight of stairs.
Another experience I had semi-recently was when I was asked to quickly build a proof of concept for something. I dug out a framework I haven't worked with in ages, but remembered fondly, and... what is this feeling? I can work without having an aneurysm? If I don't know something, finding it in the documentation is maybe 5 minutes? Madness.
I don't know your situation, but maybe you're not as bad as you think, it's just that your circumstances suck.
My advice would be to try and get ahead of it. Maybe you'll find something more enjoyable, but in any case, it takes off the stress of "when is the hammer gonna drop?" The job search will probably also be a easier to handle.
More options
Context Copy link