Live data from Hacker News

My guiding principles after 20 years of programming (2020)

alexewerlof.medium.com

191–193 of 193 posts

Re: My guiding principles after 20 years of programming (2020)

#191
post #131
post #7

Earlier quoted context omitted.

I think it's amazing if one can claim with a straight face people should `absolutely` be paid for pet projects at work.

pet projects can still be relevant to work.. maybe you've been wanting to make some internal tool, etc

When I introduce this, my criterion is that whatever pet projects people work on during work hours should make the lives of people at the company better, if successful.

Beyond that, I don't care if it's cancer research, self-driving bicycles, an email client someone else at the company uses, or a script to automate some commonly performed actual work task.

Re: My guiding principles after 20 years of programming (2020)

#192
post #56

I think #1 is: Rule #1: Software is a social service. If you're not writing for the user, but rather for the sake of writing code, you're not a good programmer. Write for the user, whether that user is Joe Sixpack or Jane Hotdev, or even if you are the user - assume the role of servicing the end user. Software is a social service.

Is every job a social service?

Pretty much. The money to pay for the work, has to come from somewhere. Usually that is a person/organization/society.

But software specifically is social, because software is useless without a user.

Post reply on HN