Earlier quoted context omitted.
Author here. I think you have a point here. Anxiety can certainly stem from the point you mentioned. But I also think anxiety from other sources can affect your development negatively.
Agreed. Anxiety can also be expressed as a realization that what's being worked on is useless, adds negative value, or just personally unfulfilling or unimportant. Cops firing teargas at peaceful protesters a few blocks away has cause me a good deal of that flavor of anxiety, which I don't think is necessarily a negative outcome. Do you have any insights along those lines?
Anxiety in product development
21–30 of 162 posts
Re: Anxiety in product development
#221. Ambiguous or no deadlines, frequent check ins, "crunches" when their deliberately poor planning doens't work, keeping an air of uncertainty around everything.
2. Giving the same tasks to multiple groups and deliberately pitting them against one another in a kind of unhealthy competition. Constant fear of obsoletion.
3. Little or no positive feedback, only give feedback when things are wrong. Deliberately vague about future career prospects or growth, holding the carrot out but with no promise to deliver.
The problem is that each of these are tied into natural "sources" of anxiety that are likely to happen with or without the company actively promoting it, but the company promoting it can make people work even more frantically. The problem is they don't realize people produce their "best" work when they have creative freedom from anxiety.
Re: Anxiety in product development
#23Re: Anxiety in product development
#24Literally. This is another reason why meditation is important.
Anxiety is always accompanied by patterns of muscle tension. It can be relieved by mechanical relaxation of the tissues. Relaxation is achieved by awareness, which is fostered by meditation.
A calm, clear mind flows from a calm and relaxed body.
- - - -
In my career I've observed that business is a kind of theater for people's ego trips to play out within, and the form and methods of a business reflect the karma, if you will, of the people running it. It's one of those things that sounds trivial once you type it out.
Anyhow, it reminds me of Conway's Law. https://en.wikipedia.org/wiki/Conway%27s_law
Re: Anxiety in product development
#25I 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…
Re: Anxiety in product development
#26The intersection of people understanding both Catch-22 and Permit A 38 is probably pretty small.
For those, like me, wondering what Permit A 38 is: https://asterix.fandom.com/wiki/The_Place_That_Sends_You_Mad I wasn't familiar with it before, but might start using it, as it's unfortunately relevant at work.
Re: Anxiety in product development
#27The author's blog is incredibly good. I'm binging some articles right now :)
Re: Anxiety in product development
#28Re: Anxiety in product development
#29Funny, to see this pop up finally. I've been talking (with my friends) about how all development is 'fear driven development' for quite a while now. Of course I don't mean just software development, but the way it manifests in software is instructive. The different fear responses range from formal methods to FOMO but in general we latch onto something as a source of comfort. Conway's law expanded to how you communica…
> Conway's law expanded to how you communicate with yourself. Can you please clarify?
Conway's law is an adage stating that organizations design systems that mirror their own communication structure.
In a sense, your own self is an organisation whereby we communicate with ourselves in fearful and anxious ways, so the systems we build can only be a reflection of that fear and anxiety.
Re: Anxiety in product development
#30As a new developer, I think I fall into this trap a lot! I always don't want to touch other people's methods or introduce bugs, so I only make tiny, tiny little changes before thoroughly testing everything. It really slows me down.