I've always viewed programming as more art than science, and derive most pleasure from twisting it in unusual ways, or throwing together useless "toys" mainly for my own enjoyment. Sometimes these exercises yield something useful (new libraries, tools, frameworks etc.), but that's just an added bonus.
Unfortunately, this kind of intellectual play doesn't pay the bills... developmental API "plumbing" does. To me, it's mostly boring, but occasionally throws up interesting challenges. The main reason I stick with full stack is to keep it as interesting and varied as possible.
What parts of your “toys” do you find fulfilling, and why do you think this kind of software is not useful in a professional setting?
I must admit that I do enjoy software architecture a lot, and so choosing which API, when, for what reason, and how to introduce it is what really gets my creative mind going. Do you chose an event driven architecture or stick with plain old REST calls and a DB transaction? What if you had a big old codebase using node.js and mongodb? What if this thing needs to ship tomorrow?
The creativity is moved from the actual code to the design of the system, the compromises, the realities of running a system production (very worth it using a shitty API if the tooling is better, etc…)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've always viewed programming as more art than science, and derive most pleasure from twisting it in unusual ways, or throwing together useless "toys" mainly for my own enjoyment. Sometimes these exercises yield something useful (new libraries, tools, frameworks etc.), but that's just an added bonus.
Unfortunately, this kind of intellectual play doesn't pay the bills... developmental API "plumbing" does. To me, it's mostly boring, but occasionally throws up interesting challenges. The main reason I stick with full stack is to keep it as interesting and varied as possible.
What parts of your “toys” do you find fulfilling, and why do you think this kind of software is not useful in a professional setting?
I must admit that I do enjoy software architecture a lot, and so choosing which API, when, for what reason, and how to introduce it is what really gets my creative mind going. Do you chose an event driven architecture or stick with plain old REST calls and a DB transaction? What if you had a big old codebase using node.js and mongodb? What if this thing needs to ship tomorrow?
The creativity is moved from the actual code to the design of the system, the compromises, the realities of running a system production (very worth it using a shitty API if the tooling is better, etc…)