In my day job, I arrived at using some tools and patterns which are not very common practice in our industry. But they have made an immense difference in the maintainability (including speed of fixing bugs and adding new features) of our products. When I research (watch tutorials, read docs, etc) products like Unity from that backdrop, I feel like there is room for another take on the dev experience that could incorporate some of the same things. And likewise there are things I take from game dev patterns as useful models for some of my day-job problems. Such as ECS and Data-Oriented Design.
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.
Thanks for the response.
In my day job, I arrived at using some tools and patterns which are not very common practice in our industry. But they have made an immense difference in the maintainability (including speed of fixing bugs and adding new features) of our products. When I research (watch tutorials, read docs, etc) products like Unity from that backdrop, I feel like there is room for another take on the dev experience that could incorporate some of the same things. And likewise there are things I take from game dev patterns as useful models for some of my day-job problems. Such as ECS and Data-Oriented Design.