The intersection of people understanding both Catch-22 and Permit A 38 is probably pretty small.
Maybe you could call it "what would happen if Heller and Kafka tried to co-write a novel."
91–100 of 162 posts
The intersection of people understanding both Catch-22 and Permit A 38 is probably pretty small.
Maybe you could call it "what would happen if Heller and Kafka tried to co-write a novel."
Its a little known secret that managers deliberately promote anxiety driven development because it keeps workers at "peak productivity". A couple of the major things i've seen companies do in the past over and over again to myself and to others I worked with: 1. Ambiguous or no deadlines, frequent check ins, "crunches" when their deliberately poor planning doens't work, keeping an air of uncertainty around everything…
Key developers leave the project for greener pastures, and business people wonder how the project failed despite the fact everyone was working so hard.
I think the serenity prayer, sans unnecessary theological content, is relevant here. Grant me the serenity to accept the things I cannot change, the courage to change the ones I can, and the wisdom to know the difference. For a lot of software products, there is no winning in the long run. You've got good product-market fit and customer loyalty, but your code base is a huge mess and the hard technical problems are so…
If the theological content is unnecessary, then who are you expecting to grant you the things requested in the prayer?
Now, I still don't believe in anything literally supernatural. I don't think any quantum woo or mysterious psychic connection or literal sky daddies exist.
The point is, our mind at its core operates in terms that can be best spoken to in such metaphor. Just like we don't "see" wavelengths or spectra, we see color. If I told you that red is high frequency and blue is lower frequency light, you'd probably believe it, if you hadn't learned the opposite in physics class.
We see color and not light frequency, we see objects, we see tools, we see potential paths to walk on, we see handles to grab, we use tools as extensions of the body (with the brain actually mapping out some tools as if they were limbs).
In the same way much of what we experience in terms of emotional/spiritual life (if you don't suppress it and are mature enough) is very religious sounding old-fashioned terms like good and evil, temptation, redemption, salvation, revenge, punishment and forgiveness, wisdom and contemplation, sin and penance, suffering and attainment, grace and humbleness.
10 years ago all the above words meant jack shit to me, just some mumbo jumbo that bigoted old people use to condemn the youthful because they are too old and impotent and envious of the youth.
The thing is, the more you look into philosophy with a more open mind, you see that it actually has content behind it. To put it in more rational terms, you become aware of and able to discuss things that happen in the more animalistic part of the brain, that makes you excited, anxious, sad, joyful. It's easy to believe that all this is just straightforward "bad events -> sadness", "good events -> joy".
If you meditate, if you wind down in the evening and are mature and have some life stories of both success and disappointment, you will see that a lot of that stuff is best processed in spiritual terms and by relating it to archetypal stories. I've been reading Jordan Peterson on this matter, and while I don't agree with his conclusions in many cases, I do find it to be a good bridge between the rational scientific endeavor (you need to know the frequency of blue light to create lcd screens etc.), and the personal/spiritual manifestation of it (the blue handle of a hammer that I'm already preparing to grab in my mind).
It's not that the magic sky daddy gives us the stuff we ask for in prayer, like a vending machine. But for one reason or another, pretending to act out a sacrifice story or "asking god" why something happened can be useful.
You can substitute other words if you have an aversion to Christian terminology, you can say you're connecting to yourself, your higher self, the consciousness of the universe.
The thing is, ideas and insight doesn't come from forcing. Just like you don't pull on a plant forcefully to make it grow, you nourish it from below and with sunlight and air.
Nobody can make themselves have a great idea. In our experience, ideas just present themselves. Obviously they are not magically handed to us, but it looks "as if". Of course it's a complex brain process that involves long term memory, hormones, interactions of various brain parts, etc. Knowing the details of this can be beneficial, but just because you understand the brain chemistry of alcohol intoxication doesn't mean you won't get black out drunk if you drink a lot. Similarly somehow it is deeply ingrained in us to see things in terms of agents and purposeful patterns. One way to deal with this is to label this as a thinking error, an erroneous heuristic making too many false positives, a mistaken overdrive of the empathic part of the brain, something to eradicate. That's how I used to think.
Once you understand all this, you can be capable of discussing, untangling and managing your emotions and the archetypal/spiritual language can be a way to formulate this.
However when things get intense, I like to freshen it all up a bit with reading Zen koans. Zen koans are somewhat like "serious jokes" and confront your overly analytical mind with freezing shocks. They are playful, non-literal, but sometimes literal, or hanging in the air in between.
I've spent around 34 years writing code so far. My last project was an online order system for a lunch restaurant. To get an idea what kind of problems they're dealing with, I started by working two weeks in the restaurant. To my surprise I found that I actually enjoy delivering food more than writing code. As long as the customers get the food they ordered delivered in time, everyone is happy. And once I'm done, I'm…
As The Little Prince would say were he a coder: you are forever responsible for the code you write. Every new system an organization takes on requires maintenance, training, etc. This takes time from the coders and is frequently not taken into account.
Developers stay at companies for 1-2 years, so it seems like you get frequent resets.
Yes, but what leads to anxiety? Toxic team dynamics. Google did a study and found the number one predictor of strong teams was a feeling of "psychological safety." > Within psychology, researchers sometimes colloquially refer to traits like ‘‘conversational turn-taking’’ and ‘‘average social sensitivity’’ as aspects of what’s known as psychological safety — a group culture that the Harvard Business School professor A…
Maybe improv classes or subsidizing employees to exhibit art or publicly perform music?
I think the serenity prayer, sans unnecessary theological content, is relevant here. Grant me the serenity to accept the things I cannot change, the courage to change the ones I can, and the wisdom to know the difference. For a lot of software products, there is no winning in the long run. You've got good product-market fit and customer loyalty, but your code base is a huge mess and the hard technical problems are so…
I find that emotional compartmentalization is a critical skill. A couple years ago, I faced a very tough time in my life. My business was collapsing, my family's finances were in jeopardy, and there was a serious health issue going on. The emotional stress was incapacitating. I couldn't sleep, let alone focus enough to fix my problems. It was the downward spiral nightmare scenario. If I didn't have dependents (wife +…
I've spent around 34 years writing code so far. My last project was an online order system for a lunch restaurant. To get an idea what kind of problems they're dealing with, I started by working two weeks in the restaurant. To my surprise I found that I actually enjoy delivering food more than writing code. As long as the customers get the food they ordered delivered in time, everyone is happy. And once I'm done, I'm…
As The Little Prince would say were he a coder: you are forever responsible for the code you write. Every new system an organization takes on requires maintenance, training, etc. This takes time from the coders and is frequently not taken into account.
Earlier quoted context omitted.
As The Little Prince would say were he a coder: you are forever responsible for the code you write. Every new system an organization takes on requires maintenance, training, etc. This takes time from the coders and is frequently not taken into account.
> you are forever responsible for the code you write. Developers stay at companies for 1-2 years, so it seems like you get frequent resets.
I've been at the same place going on 8 years. My father in law has been at the same place for 30.
I've had a few engineers who struggled with the issues mentioned at the beginning of the article. They were skilled engineers who typically knew the right thing to do, but felt they needed permission or approval to do the things. And the solution I took was to gently encourage them, but also let them be just a little bit uncomfortable. They need a safe environment they can fail in with no repercussion, but also need…
Well, you're probably training them to be autonomous just like I'm training my dogs to use the dog door. They're still uncomfortable doing so because they're used to me letting them out, but every so often I let them do their own thing and they eventually find their way out. Soon it will become habit and they won't depend on me so much anymore.
How does a dog door prevent rodents and other riffraff from coming in?
I've spent around 34 years writing code so far. My last project was an online order system for a lunch restaurant. To get an idea what kind of problems they're dealing with, I started by working two weeks in the restaurant. To my surprise I found that I actually enjoy delivering food more than writing code. As long as the customers get the food they ordered delivered in time, everyone is happy. And once I'm done, I'm…
At the time, I simply couldn't understand that. Sure, I hadn't been writing code as long as he had, but I couldn't imagine enjoying anything more than that. I absolutely loved twiddling bits and watching mechanical systems do what my code told it to.
Fast forward to now. I still really enjoy software/hardware/mechanisms/coding/design etc., but if I had to give it up tomorrow, I know I could find something I love just as much.
It's a really big world and there are a lot of sandboxes to play in.