0xFEE1DEAD

I don't exactly understand what this has to do with continuous delivery, but maybe I just don't know enough about this topic.

Wouldn't it have been best to set up a 'shadow infrastructure' and route every trade into it for several weeks/months to verify the correctness of the system?

Germany chiming in to agree.

WhatsApp is the default

In Germany we've got 'Unze' (ounce) which is defined as ~30g which we only use when talking about precious metals.

What we do use is 'Pfund' (pounds lbs) which is defined as 500g.

I am amazed the nations of the world actually came to an agreement about what to use as base units and I can't even fathom what shit show it must've been before that.

I live a 30min drive away from the Netherlands and your ounce is already 230% more then my ounce.

Look for clear and distinct frequency bands corresponding to the vocal range of human speech (generally around 100 Hz to 8 kHz). If the frequency bands are well defined and distinct then the speech is likely clear and intelligible. If the frequency bands are blurred or fuzzy then the speech may be muffled or distorted.

Note that speech like any audio source consists of multiple frequencies, a fundamental frequency and its harmonics.

Background noise can be identified as distinct frequency bands that are not part of the vocal range of human speech. E.g. if you see lots of bright lines below or above the human vocal range then there's lots of background noise. Especially lower frequencies can have a big impact on the perceived clarity of a recording whereas high frequencies come of as being more annoying.

Noise within the frequency range of human speech is harder to spot and you should always use your ears to decide whether it's noise or not.

You can also use a spectrogram to check for plosives (e.g. "s" "k" "t" sounds) as they also can make a recording sound bad/harsh.

> I fail to see how this is a bug if you feed it garbage

What an awful response to someone reporting a pretty serious security vulnerability.

On my iPad I’m able to access it via Control Center [1] so you can probably also get it working for the iPhone I just haven’t bothered

[1] https://imgur.com/a/FhzjJmH

I use this too. You should know the iPhone has this as a accessibility feature.

Go to Accessibility -> Audio/Visual -> Background Sounds -> Sound -> Dark Noise

After that go to Accessibility -> Accessibility Shortcut -> Background Sound and you'll be able to activate the noise with a tripple side button click

Just 4h ago I went to affinitys website because I wanted to download photos for my work laptop and I got a page "we're working on something big. stay tuned". And now I'm seing this. I'm hyped.

Edit: Looks like there's no discount if you already own a license which is a bummer considering they advertised with selling you a lifetime license.

> Use set -o errexit at the start of your script. [...]

A couple of days ago this link was posted to hn http://mywiki.wooledge.org/BashFAQ/105

It showed me once again how little bash I know even after all those years. I checked the examples to see if only set -e is dangerous or also set -o like the author suggested and sure enough it's just as bad es set -e. You just got to thoroughly check your bash scripts and do proper error handling.

Seems a bit like a witch hunt to me. It's your PC executing the request. Nowhere does it say this data gets send to apple servers.

Just yesterday I watched a talk from NDC Copenhagen by Dylan Beattie about this exact topic. The story which stood out the most was this https://www.youtube.com/watch?v=gd5uJ7Nlvvo&t=22m09s

The whole talk was an interesting watch tho.

please tell him to sell merch. I'm a Michael R. Clarkson super fan and desperately want to show my support in real life. Because of him I learned ocaml and for this I'm forever grateful.

no need for active radar. just have your guys at base watch your flight path and route you safely. this way you can deactivate your transponder and still be not of danger to anyone around you. I’d imagine this is how they to it

I've been closely following him eversince he first got into the spotlight. He got famous in the tech community because he's been preaching about tdd and later on clean code before it got widely accepted to be good practice. Because of this the tech community treated him like a divine preacher and it seems like this got to him and went into his head. His persona "Uncle Bob" is this wise and all knowing guy who has ideas way ahead of everybody else but like most people he had more misses then hits. It seems like he's chasing "controversially big ideas" which he presents like they're truths and this can be pretty tiring to read.

Well then it might me a reddit thing because I've had both interactions on r/rust and in the comments of r/golang where rust fanboys derailed the the conversation

Every interaction I’ve had with the rust community was toxic in nature. Also for whatever reason all those „rust vs go“ articles are always coming from the rust corner. It’s like the rust community is frustrated about go success and they individually feel the need to attack their perceived competitor meanwhile the go community has no issue with any other language.

People like the author tend to think that the differences in humans vs other primates can be seen as a linear function. I'm like the author no expert on this topic but I imagine this as a exponential function. You see plenty of similar behavior in primates and humans, similar social structures, clear evidence of being capable of complex thought processes etc.

It's like the difference between transistors and a logic gate isn't big but results in much more complexity.

It's a trade I'm willing to take for simplifying reasoning about non-happy-paths. Try catch is great in theory but it's super easy to shoot yourself in the foot with in bigger projects, either because it's non exhaustive or someone took the easy way out and made a catch which isn't fine grained anough.

I wish people would realize using pointers in go doesn't automatically mean better performance. You should really stick to using values and only use pointers if it's necessary/makes for better code/increases performance. Using pointers makes escape analysis harder and results in more pressure on the gc which can effects performance more than usage of pointers saves.