Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

You’re not writing code, you’re solving problems

lanraccoon.com

Post reply on HN
Print view View original

11–20 of 143 posts

Re: You’re not writing code, you’re solving problems

#11

Post by amelius »

webn3rd wrote: post #4
everyone wrote: post #2

Yet another article on HN that reads as if the entirety of programming = making CRUD web apps. I make games, it has nothing to do with the real world, I'm not solving any real world problems. I'm making a new fantasy world.

Still, in my point of view, your viewpoint and the article's one can be aligned. Strictly speaking, converting your ideas about the fantasy world into code to run the game is "solving a problem". I'd argue that any creative process can be coined as a problem-solving exercise, except for the fact that in many such cases the problem isn't tangible and the outcome isn't measurable.

> I'd argue that any creative process can be coined as a problem-solving exercise

Problem solving with real-world constraints = engineering

Problem solving without any constraints = art

Re: You’re not writing code, you’re solving problems

#12

Post by acdha »

amelius wrote: post #11
webn3rd wrote: post #4

Earlier quoted context omitted.

Still, in my point of view, your viewpoint and the article's one can be aligned. Strictly speaking, converting your ideas about the fantasy world into code to run the game is "solving a problem". I'd argue that any creative process can be coined as a problem-solving exercise, except for the fact that in many such cases the problem isn't tangible and the outcome isn't measurable.

> I'd argue that any creative process can be coined as a problem-solving exercise Problem solving with real-world constraints = engineering Problem solving without any constraints = art

Art has always had constraints: funding, the physical media’s capabilities, and the ability to reach an audience. This is why any time a new technology shift happens there’s a spike of artists trying things which were not previously feasible.

Re: You’re not writing code, you’re solving problems

#13

Post by amelius »

acdha wrote: post #12
amelius wrote: post #11

Earlier quoted context omitted.

> I'd argue that any creative process can be coined as a problem-solving exercise Problem solving with real-world constraints = engineering Problem solving without any constraints = art

Art has always had constraints: funding, the physical media’s capabilities, and the ability to reach an audience. This is why any time a new technology shift happens there’s a spike of artists trying things which were not previously feasible.

It's a spectrum. I just wrote down the two ends.

Also, an artist's constraints are often self-prescribed, and they can easily change them if they like.

Re: You’re not writing code, you’re solving problems

#14

Post by thaumasiotes »

amelius wrote: post #11
webn3rd wrote: post #4

Earlier quoted context omitted.

Still, in my point of view, your viewpoint and the article's one can be aligned. Strictly speaking, converting your ideas about the fantasy world into code to run the game is "solving a problem". I'd argue that any creative process can be coined as a problem-solving exercise, except for the fact that in many such cases the problem isn't tangible and the outcome isn't measurable.

> I'd argue that any creative process can be coined as a problem-solving exercise Problem solving with real-world constraints = engineering Problem solving without any constraints = art

This is reminiscent of the old divide between mathematics and philosophy:

true and useful = math

true and useless = philosophy

Re: You’re not writing code, you’re solving problems

#15

Post by acdha »

heavenlyblue wrote: post #5

Astrologers announced the week of the epidemic: the number of useless posts to increase traffic to your website had quadrupled.

If you don’t like it, don’t vote for it and move on. A content-free comment complaining that someone on the internet made something and gave it to you for free doesn’t add to the conversation.

Re: You’re not writing code, you’re solving problems

#16

Post by wwweston »

thaumasiotes wrote: post #14
amelius wrote: post #11

Earlier quoted context omitted.

> I'd argue that any creative process can be coined as a problem-solving exercise Problem solving with real-world constraints = engineering Problem solving without any constraints = art

This is reminiscent of the old divide between mathematics and philosophy: true and useful = math true and useless = philosophy

Which side does the practice of distinguishing between the useful and the useless fall on?

Re: You’re not writing code, you’re solving problems

#17

Post by muglug »

I think this article constructs a strawman argument – pretty much all developers are solving some sort of problem.

The big question is who you're solving problems for – when I was a single person doing freelance web work (like this article seems to assume), I was always solving problems for customers and their clients.

Once I started working with other developers, I became interested in solving their problems too – sometimes in the form of a big refactor to improve the code, but also making tools to improve the codebase at scale.

Re: You’re not writing code, you’re solving problems

#18

Post by datalist »

acdha wrote: post #15
heavenlyblue wrote: post #5

Astrologers announced the week of the epidemic: the number of useless posts to increase traffic to your website had quadrupled.

If you don’t like it, don’t vote for it and move on. A content-free comment complaining that someone on the internet made something and gave it to you for free doesn’t add to the conversation.

I believe calling out something for what it is, is just fair.

Just like calling out Milli Vanilli was in order.

Re: You’re not writing code, you’re solving problems

#20

Post by datalist »

webn3rd wrote: post #4
everyone wrote: post #2

Yet another article on HN that reads as if the entirety of programming = making CRUD web apps. I make games, it has nothing to do with the real world, I'm not solving any real world problems. I'm making a new fantasy world.

Still, in my point of view, your viewpoint and the article's one can be aligned. Strictly speaking, converting your ideas about the fantasy world into code to run the game is "solving a problem". I'd argue that any creative process can be coined as a problem-solving exercise, except for the fact that in many such cases the problem isn't tangible and the outcome isn't measurable.

You could argue that, but that would apply to painters, chefs, mechanics, hair dressers, everyone.
Post reply on HN