It’s not as strict as you are trying to make it out to be. My favorite job ever was a small company. The owner was fine with us programmers just working on pet projects on company time. I was goofing around at some point and ended up writing us some code that ended up being kind of a workshop for some code that us programmers would have to sit and work on. It allowed non-programmers to set up the same conditions and handled the ‘code’ part internally. It was all because I was just goofing around with program ideas and eventually got to that point where I had my eureka moment. I didn’t set out to waste company time and money, but the end result paid off in droves, which is exactly how it sounds like the deck came to be. Another programmers goofy side project turned into an accounting package that we ended up tying into our actual product. If our boss/owner had been looking at it the way you are describing, none of that would have come to fruition, but look at all the money he would have saved not letting us programmers do what we did. /s
thats called R&D. I don’t personally spend millions of dollars, but I do spend money on things that never pan out but teach me a lot of lessons I can apply to my next project
this is how I know you’ve never created anything, lol. lots of times, you fail at making something, but you learn from those failures.
who knows what other projects they threw money at and failed, the only one I can think of rn were the steam machines.
I’m sure they learned from those mistakes, tried again, and here we are with the steam deck
So I suppose you spend millions funding engineers to create products as personal toys with no intention of selling any of them?
It’s not as strict as you are trying to make it out to be. My favorite job ever was a small company. The owner was fine with us programmers just working on pet projects on company time. I was goofing around at some point and ended up writing us some code that ended up being kind of a workshop for some code that us programmers would have to sit and work on. It allowed non-programmers to set up the same conditions and handled the ‘code’ part internally. It was all because I was just goofing around with program ideas and eventually got to that point where I had my eureka moment. I didn’t set out to waste company time and money, but the end result paid off in droves, which is exactly how it sounds like the deck came to be. Another programmers goofy side project turned into an accounting package that we ended up tying into our actual product. If our boss/owner had been looking at it the way you are describing, none of that would have come to fruition, but look at all the money he would have saved not letting us programmers do what we did. /s
thats called R&D. I don’t personally spend millions of dollars, but I do spend money on things that never pan out but teach me a lot of lessons I can apply to my next project