Live data from Hacker News

Programmers’ emotions

blog.sidebits.tech

1–10 of 143 posts

Re: Programmers’ emotions

#6
I've been thinking about this A LOT over the last year. Knowledge work is Emotional work.

Software developers make software for PEOPLE. Making things for people requires empathy to be successful or else a whole lot of luck.

Having empathy means putting myself out there. It means asking questions that sound ignorant.

It means going from feeling like I had a great idea to seeing all the flaws and shortcomings of that idea, and being willing to accept the shortcomings of that idea and change my mind.

It means doing all of this and being 100% technically perfect. One extra space - computer says no. Number in the wrong place - computer says no. Off by one - computer says no. Tyop - computer says no.

Re: Programmers’ emotions

#8

I don't know if confusion should be considered an emotion. Depending on the situation you can be confused and feel fear, or you can be confused and be excited. Same applies to "silliness" and "hesitation".

I don't know if shell scripts should be considered a programming language.

Re: Programmers’ emotions

#9
post #7

Missing: frustration.

Also missing: blind fury I occasionally find myself feeling like this after frustration builds to a crescendo, and I've spent hours trying to get something to work that should have taken no time at all!

That is when I truly hate technology and how bad all UX is.

Re: Programmers’ emotions

#10
Couple more for me

Surprised, when something non trivial worked the first time around. How could this be? This can't be right?

Floored, when I see the quality and quantity that some developers are able to contribute or create.

Post reply on HN