You’re not writing code, you’re solving problems
lanraccoon.com
You’re not writing code, you’re solving problems
1–10 of 143 posts
Re: You’re not writing code, you’re solving problems
#2Re: You’re not writing code, you’re solving problems
#3Yet 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.
Re: You’re not writing code, you’re solving problems
#4Yet 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.
Re: You’re not writing code, you’re solving problems
#5Re: You’re not writing code, you’re solving problems
#6Re: You’re not writing code, you’re solving problems
#7Yet 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 would not write a post about it.
Re: You’re not writing code, you’re solving problems
#8Yet 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.
Game dev can be just hardcore programming juggling everything from euler equations to hardware performance budgeting.
Sure you can take the view this are just constraints in a problem solving exercise.
Or it’s highly skilled programming. I fall on the latter view for sure.
Re: You’re not writing code, you’re solving problems
#9Re: You’re not writing code, you’re solving problems
#10Yet 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.
Like, you could also say that I'm solving the real world problem of, 'this exact game not existing, cus these specific people would love to play it but it doesnt exist' .. But that is a super-stretch.