Bells and metal tubes all can have funky harmonics too (and sub harmonics which is interesting). I don't know if it qualifies as "timbre" but if you remove the initial attack, many instruments sound very similar. There are some tests on youtube that I did a lot worse than I thought I would.
One of my go-to for making a new instrument sound is to tamper with the ADSR envelopes, the attack (as you say, the first part, like a pluck of a string or mallet hitting a bell), decay, how long the note "fades" naturally, sustain which is the total length of a note, and release, which is how long a note plays after you "release" it.
Turning the attack up removes the pluck, setting the other three short makes anything percussive, and you can get weirdness if you mess with decay and release with echo / delay effects.
I should sleep, this was way harder to explain than it should have been.
Example, harp has a sharp attack, and real long decay, sustain, and release. To make that a pizzicato violin, you snap the decay and sustain to nothing, and leave a little release. Now your harp sounds like a violin.
This has been the majority of my professional coding experience since the 90's ::shrug::. Having to take ownership of some Java Spring application felt a lot like stepping through an assembly program or some random ROM. Each line of code just returns values and modifies a bunch of other stuff at the same time and you slowly build up a mental model of what it's doing and what it's trying to do!
Works pretty slick for me. Are you considering adding things like super sampling for anti-aliasing and alternate coloring methods like triangle inequality, etc?
This played out at my last place. My boss would assign my co-worker to build the world's crappiest car in the least amount of time and when it broke down I would be the only one that seemed to be able to fix it (while my co-worker was busy building some other crappy car). I would have built a much better car in the first place! However I would have taken more time and the goal was to build and release as fast a possible. My boss was okay with the risk of said crappy car, my co-worker got promoted and I slowly burned out.
It's a tough balancing to make sure you sell yourself correctly and fight to work on things you want to!
We had a guy like this on our team once, it took a year to convince management he was a net drag on the team. Half the team quit, the other half said they would if they had to work with him any longer.
To prove the point we put him on a strategic rewrite and gave him master/trunk while the entire team moved to a feature branch for 6 months. This was complimentary to his ego as he was sick of us bureaucrats in the rest of the team telling him what to do and being such a burden on his genius creativity.
By the end he was unable to build / run his own branch, while the remaining team lost no velocity and was making regular releases to end users. The choice was easy at that point.
I try to never ever use the word "refactor" or "clean up" in any of my work items or even commit messages. My boss and other teams I am collaborating with are like clients to me. Restaurant bills typically do not include explicit line items for "dish washing, mopping, grease-trap cleaning, oil disposal, etc."
The downside is that other people/teams can appear to work much faster and put you at a disadvantage or even risk of being let go due to this perception. Unfortunately this is where IMO you have to play the game and make sure you toot your own horn to the right people sometimes.
This is a good point! We've gotten some instances of Chesterson's Fence that some devs casually remove during a "test refactor" that later allowed a regression to make it into prod.
I've caught some errors in "test refactoring" from our multiple levels of testing having large overlap with teach other. Our end-to-end tests have a lot of overlap with the integration tests which in turn have a large overlap with unit testing. The unit tests run in a matter of seconds compared to the end-to-end which can take minutes or in some cases hours for our manual testing so the levels of testing also serve as an efficiency for us.
I believe "transparent" is the term used when claiming a lossy audio codec is indistinguishable to a lossless one by a human for some definition of an average human. For example I believe aac was considered transparent for most pop music at 160kbps for stereo, 16-bit @ 44.1khz (CD quality). So iTunes selling 192-256kbps was considered more than enough.
That would be green tea no? You pick the green tea, cook it to denature the enzymes to arrest the oxidization (called the "killgreen" step in Chinese) and voila, green tea! Lots of green teas can be quite smooth and even more so with more careful brewing.
The Brit I mentioned elsewhere seemed to think it was the drying that arrested the chemical processes in the tea.
He was also adamant about storing it in well sealed containers out of direct sunlight. I ended up throwing away a couple of containers because of this (although I've kept a couple that are just too beautiful to part with - I store my daily drinker in there since it doesn't need to keep as long). Also explains why my dealer uses mylar vacuum packs for anything over an ounce. No oxygen, no light.
White tea does not undergo the "killgreen" step that green teas and oolongs teas do IIRC. The drying slows the oxidation but does not arrest it. "Aged" white tea is a thing. If you let it sit around long enough it turns deep red. Green tea just turns into stale tea. They even compress white teas into something similar to those "Pu'er Cakes".
Yes, green tea needs lower temperature and controlled infusion time, but rewards that. The author definitely does not seem to be a fan and is not doing it justice.
Yeah! Green tea gets fried or steamed right away to halt oxidation. That kills off some of the undesirable bitterness that masks some flavors that are even present in fresh leaves. It is not that Green doesn’t have any taste; it is that there are more guardrails over what flavors can appear and how distinct they can be.
If you argue that from the site's side then you can bring up that ads are taking up data, bandwidth(thus time) and battery (insane JS "game" ads) on the client side no?
The throttling is so severe it is effectively blocking. The throttling goes down to 50KiB/s on my PC trying to download a basic youtube video. That around 0.4mbps which puts you barely around the bandwidth needed to stream a very low quality 360p/480p video. For reference, this video is about 2 minutes long and that's how long it took me to download it via the last version of youtube-dl:
