Ask HN: Why does writing code physically hurt my brain?
I come from a traditional hardware / os level "Sysadmin" background. Over the past 4, maybe 5 years I've been having to write (and interact with) more and more code, and it literally clouds my brain, makes me very agitated, and makes me physically feel like I've had a seizure
At work we're moving from one cloud provider to another, and the new cloud provider is pretty much "scripting only" for administration.
Trying to work through the certification materials for said cloud provider, and it's literally got me feeling like I want to jump off a cliff due to their confusing syntax, and general wonkiness. At least with Linux, there's man pages, and the -h --help, etc. flags
So, to get to my point, how are non-developers making the switch to this "infra as code" paradigm without giving themselves a stroke?
37 comments
[ 3.0 ms ] story [ 90.9 ms ] threadIt is just exercising your short term memory that hurts your brain and causes all that stress and you’ll get better. Soon all those layers of abstraction and the way they relate will be more muscle memory. Like driving. You’ll “glance at your mirrors” when merging and it won’t seem so stressful. It just takes time and practice
Also, stackoverflow is man pages for programmers
Can't use stackoverflow on a certification exam.
Production programming as opposed to academic programming is about writing as little of your own code as possible. Because we all suck at writing code :-)
Certifications are another matter. I’ve found the ones worth having take a career to prep for and the ones your boss tells you to get can be passed by studying a cheat sheet online for a couple hours.
Based on the labs I've done, and other materials, I'd say it's NOT a "cheat sheet" exam.
It's really sorting out syntax and structures that fries my brain. Code never "sticks" with me, and I'm in a constant state of bootstrapping, for lack of a better term.
Are you taking the cert to get a job or is your job making you get the cert?
Getting your employer to pay for training and the actual cert is definitely the way to go. I have always discouraged anyone looking to get the cert first
There's a lot to the exam I get, simply from experience. I'm getting slaughtered on the Azure CLI stuff since I simply cannot get the syntax to stick, no matter how many times I re-run through the labs.
Do you feel you're not getting it or that you're not getting it fast enough? The latter can evolve into the former. And perpetuate the anxiety loop.
Losing just an hour of sleep per night results in 30-70% reduction for all of the above, without us perceiving the difference. It’s crazy how underestimated the importance of sleep is in our culture.
Check out this interview with Mathew Locker, one of the lead sleep researchers in the world. Blew my mind.
https://overcast.fm/+RxHE3jC4w
My last actual migraine was in December of 2015
And you spend half your time wondering, "who would allow such a thing to exist like this, where is the pattern?"
This just further erodes at the stack of items you hold in your head while trying to process all the edge cases and other unexpected crap.
One thing though, and I have no idea if relevant, but many people get anxious or struggle because they don't breath out enough.
Especially when a little confronted in some way, they unconsciously keep on topping up on breath without fully breathing out.
Then they find they can't breath in enough, a little panic starts and goes from there.
The number of people I have come across that were "topped up" like this is amazing, and many did not even realise until it was pointed out to them.
Three deep, push out breaths, and start again - fresh oxygen, room to breath, often calming and feels a whole lot better.
It might "physically hurt" if you aren't really comfortable with the language, too. I've found this especially true with Bash, as I just don't like the syntax, so you might be trying too hard to understand it.
Anyways, you should have fun developing at one point. Good luck :D
Honestly, given the direction things are heading (Startups wanting generic worker drones, and not specialists) I'm about a hair's breadth from selling everything I own, and buying a $30,000 farm house somewhere in a rural flyover state.
Scripting and automation is one thing, but startups putting ops/architect roles through Fizzbuzz bullshit is a little annoying after a dozen or so interviews.
Not much separating you from a help desk tech.
Treat mistakes as learning process
Treat errors as a tool
Treat difficult workmates and bosses as children
Treat scripts as writing stories for computers in different language.
If it affects you physically, it may be stress. Try to think that the whole process, whether it results in a good thing or a bad thing, is actually a progress.
There are indeed some frustrating part in scripting, unclear library docs, no static typings, slow feedback loops.
Keep in mind your end goal, being sysadmin right now is where you are and maybe a stepping stone. Do it one by one. Take a step back, calm yourself, see what's around you and take some steps to easen the pain and achieve your goal, whatever that is.
I used to have the same problem, but not when writing codes.
I love writing codes, and someday I was put in a lead/management position and the context switching between having to solve technical and managerial was giving me pain.
Then I allowed myself to make some mistake. Giving myself a sandbox to play in. That really helps.
Totally agree about context switching. I'm pretty much worthless at it.
The industry is trending towards AWS + “the cloud” because people who know how to code are providing themselves the tooling required to bypass traditional IT.