5 ms·
Mirror other comments in that you should probably get checked out by a medical professional. If it's at the point where you are asking HN, you should probably a
by johngalt 9y ago
Mirror other comments in that you should probably get checked out by a medical professional. If it's at the point where you are asking HN, you should probably also be telling a Doctor.
Specific to your stated concerns:
1. Family Commitments: No comment here, but remember that it's OK to set boundaries even with your close family.
2. Complexity of web dev: Narrow your focus. Often people will begin their careers in a very general role, but have a difficult time continuing to hold onto their entire scope as the world expands. Complexity increases faster than human abilities increase. Let go of some areas in order to focus your competence in others.
3. Work Stress: Say 'no' more often. It doesn't have to sound like 'no', it could be something along the lines of 'we will revisit this at the next planning meeting'. Then at the meeting bring up all of those suggested items at one time. Then it's not a question of "should we do X" but instead "what should be stopped so that work on 'X' can begin".
4. RSI: This should be #1. Ergo setup should be what you do today. Getting your setup wrong is a certain path to poor performance.
5. Age: 32 isn't a factor. It's ridiculous that we even have to address this. Your brain doesn't disappear at 30.
Make sure you have the following squared away:
Sleep, Diet, Exercise, Sunlight
Whenever I'm foggy/lethargic one of these is usually missing.
- tboyd47 9y agoYou're technically right, but I guess I'm just getting tired of having to organize my entire life around being prepared for work Monday - Friday. I mean, am I a machine whose only concern is achieving optimal operating conditions, or am I a human being with a life outside of work? I've resisted specializing for some time because I personally don't like working with technical people (excluding present company and our friends on HN of course!). I actually much prefer working with non-technical people, because I've found that they usually have a lot more common sense and are a lot less egotistical about their work. Maybe I just haven't been exposed to the "right crowd" but my experiences collaborating with other programmers have been very unpleasant across my career. So I always try to position myself where I can take a top level view of the product and not be pressured to move in a certain technical direction. Maybe it's time to give that strategy up, though, because it hasn't worked out very well for me.
- jaredcwhite 9y ago"my experiences collaborating with other programmers have been very unpleasant" This might very well explain your panicky/foggy feelings when programming...if your subconscious is associating negative emotions from past events with that activity, it'll keep coming up and up.
- tboyd47 9y agoThat's a strong possibility, as I have definitely come to associate programming with every negative emotion over the past few years.
- imhoguy 9y agoThis looks like a generalist's scope explosion - you might have tried to do too many things both horizontally and vertically. Maybe you could consider reducing your coding activities and only focus on higher level project aspects? Some roles like Analyst, Product Owner, Solution Architect etc.
- deleted 9y ago[deleted]