I was listening to Aphex Twin at the office one day with my Grado headphones which are open-air. They don't block sound coming in. or going out, for that matter.
this came on, and people started looking around wondering what that hideous noise was.
I can't find it, but my favorite YouTube comment is on one of the posts of this track: "I love the part where it goes 'EEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEE'"
That's actually because Ventolin is for asthma, that artist has asthma, and one of the side effects is extreme tinnitus.
@AlexandreVaillancourt Sunblock 5000 for hours of sun protection :)
@Almo Yeah, the first time I noticed it, I also had fever, so I wasn't totally sure - I figured it was just because I was sick. Turns out it was the IBs which I was given for said fever.
Well, with this ECS, I can't give a recipe to my fellow devs about "how do you add a new feature"... looks like every new component/system has its own specs...
For instance, maybe try to come up with several (a dozen? not sure, making numbers up that sound good) possible examples. Rough them out. And then distill them down two maybe 3 actual examples that overlap as much of the original 12 as possible.
I sometimes find the example features I think up don't always cover what others are imaging. Including some of their "gee it would be cool if I knew how to add an X" feedback shows the work is their to support the visions of the team.
The other way to go: collect a dozen or so examples & pick a subset that shows the greatest diversity (i.e. avoid overlap). This would show more range, but increases the work load on you (since there's little recycled work).
For what's it's worth, I had a similar problem with my home brewed ECS. Frequently new functionality required adding new classes. Sometimes I could get what I wanted from existing code, but it was a toss up on whether or not repurposing existing components lead to clean or ugly design.
Yeah. Thing is, we're having this new architecture and I'm kind of trying to push as much as possible stuff into the components. A lot of 'features' were related to external data with 'hard links' (like the cameras positioned around the machine were indexed from an enum, but all their data came from external text files, loaded at startup). I have to interface the "old infrastructure" with the new "data driven" one.