Vorstellungsgespräch bei Audi
"OK, wissen Sie, was 'integeres Vehalten' bedeutet?"
"Ich verhalte mich stets wie meine Führungskräfte, oder so ähnlich?"
"Nein. Äh. Ja. Nein. Fuck. Fuck. Fuck. Fuck."
Luccus
joined 2 years ago
Couple of years ago I saw a video about Chris Chan, and when describing "Sonichu" they labeled it as "creative unoriginality".
I often think of this term these days.
I have mostly given up on stopping them. I my testing with local bullshit, they will eventually work out most red herings. And I imagine the bazillion parameter models will do so even faster.
However, you can eat into the token budget, sometimes a lot, by adding sarcasm, aggressive/unusual in-lining or having some "fun" in your naming schema and descriptions (if the language allows them). Same with solutions requiring lateral thinking.
But the best way is to not give the full story easily. Some IDEs may have toggles for stuff, the LLM would have to find in the some config file. Game engines will let you set things up in the GUI a LLM will not easily pick up while injecting the code. Anything outside the code is usually a win.
Damn. If the glass was properly marked, I'd ask if she worked as a manager.
The slightly skewed and rotated text,
the noticable texture of JPG compression,
a perfectly unaligned down scale and pixel mismatch,
a bad crop.
their software has commited multiple crimes
Their management allowed for, and their technicians excecuted the careless set up of a Rube Goldberg crime machine. This occured after a series of other crimes and while taunting the ability of their machine to commit crimes.
The creation of the machine also included crimes, meanwhile augmenting the ability of criminals to commit even more crimes.
Surely they will be brought to justice! (insert Padme meme)
Which is why online games sometimes feel like someone is able to see or shoot through a wall.
Perception is kinda weird. A sound that's 50ms late will almost always be accepted as "in sync". A input that's 50ms late feels floaty and weird (especially on high fps monitors). 50ms of jitter on a frame can be a head ache inducing mess and low key unplayable, unless we are talking about a particularly slow game.
Spiral power, you say?
Edit: it is Junji Ito's Uzumaki.
I wonder how they would react to House of Leaves.
"You where right, Chatty said the same thing!"
Why even bother asking me then?
I just don't understand how this is a metric now. With programmers, I can at least see how someone who doesn't know any better might think lines of code is a good metric. But this?
And it gets worse: The company now has to pay both for its employees(' brain) and the damn text-completion machine.
Steinernema feltiae can be used as biopesticide against weevils, cutworms, mole crickets and - importantly for house plants - gnats.
I am currently creating some meshes that are then exported as OBJs. I am really only interested in the vertex positions and normals, as everything else will be done with shaders. But I keep coming across… well, not really a issue.
Some exported vertex positions deviate from their in-editor position by literally a micrometer. Again, I know that this is basically irrelevant. Perhaps, if I were to compress the files, I might have a few kilobytes more data than actually necessary.
…but I keep seeing this and it annoys me for no practical reason. Does anyone know if there is a "fix" for this behavior?
TLDR: The Corsair Virtuoso Pro is good and becomes pretty impressive with a bit of EQ. If you need a microphone, I think this is pretty ideal, especially for the price. And even without the need for a (btw. detachable) mic it's still pretty good. Somehow.
About two months ago, I stumbled across a post on a German blog about Corsair Gaming, Inc's Virtuoso Pro. A gamer headset from a gamer company for gamers. Please excuse my snark, but that raises just about every red flag I can think of.
But somehow, it did pretty good in Igors measurements. Rtings also measured it and it still did well, but other than those two, there's just not a lot of good information on the thing.
About three weeks later it got a bit cheaper (130,-€, instead of the usual ~160,-€. It was 110,-€ last year too). Not exactly cheap, but fine for the assumed performance, and the included microphone solved a problem with my current setup.
By now, I've been running it for a month… and it's good. Not only is it good out of the box, it takes well to EQing. Which, for me, is the absolute kicker and opened the doors to combining it with pretty a cheap Fiio JA11 / JCally JM12 with flashed firmware as they come with built-in PEQ via Web-USB interface (the app is a burning pile of trash btw.) and microphone pass-through, just a lack in power. But the Virtuoso Pros are pretty sensitive anyway making it a pretty perfect match.
I'm currently running them with this EQ:
Preamp: -5.7 dB
Filter 1: ON LSC Fc 28 Hz Gain 2.8 dB Q 0.800
Filter 2: ON PK Fc 150 Hz Gain -2.0 dB Q 0.800
Filter 3: ON PK Fc 1500 Hz Gain 2.9 dB Q 2.300
Filter 4: ON PK Fc 2700 Hz Gain -2.5 dB Q 2.800
Filter 5: ON PK Fc 3900 Hz Gain 6.0 dB Q 1.800
Here's my reasoning for this, if you are interested.
Tap for spoiler
First of: My preference is a good amout of rumble falling towards some warmth and then basically just Harman 2013.
If you check squig, you'll notice a big boost towards the bass. This is a decent call by Corsair, as open-back headphones tend to underdeliver in sub bass and a boost here can hide this effect to some degree. I just dislike the bump and would much rather push the sub bass via EQ.
Then there's a dip, a sharp rise, followed by another dip, I wanted to smooth out. This is mostly for clacky, metallicy, poppy sounds and some over-tones. I guess it "adds presence" to some instruments.
After 6-8k the measurements get wonky anyway and depend on the exact geometry of ones ear and head. As such I never really touch these anyway and the Virtuoso Pros do good here anyway.
But that's my ears. You better tune to your set. ;D
Imo, there are just two problems, both having to do with microphonics:
Corsair somehow thought a nylon sleeved cable was a good idea. Visually, I agree. Microphonically, it's terrible. I don't have a huge problem with it, but both the mic and the ear cups easily pick up any noise that comes with any movement of the cable on pretty much any surface. This is stupid. Secondly, unless you're a horse, the microphone has to be bent into an L shape. The arm is just too long and the microphone is prone to plosives. Not a good combination - even if the L-bend makes it easy to fix.
Other than that; I'd say they are pretty good headphones… with a microphone! Which is rather perfect for my use-case, where I switch from PC-gaming plus voice chat to my phone plus music and mix and match tasks as they come.
Edit: words & phrasing Edit: updated EQ settings
Last year I managed to fertilize a single flower on my cherimoya tree, which is a bit difficult as the flowers are female in the morning and turn male in the evening. This year I will hopefully be able to have the tree in a south-facing window. So I'm hoping for proper fruiting next year.
Also, strangely enough, cherimoyas seem to do well in an indoor environment and don't seem to have any pest issues at all.
About two years ago I read up on chitin as a possible pest control/deterrent as I was always struggling with mealybugs and thrips, especially in spring, and buying IPMs was getting quite expensive.
I had the most problems with my banana tree (thrips) and my kumquats (mealy bugs). But since I added insect frass (in my case sheddings and droppings from zophobas) in the fall two years ago, this problem disappeared almost miraculously. Since then I have added a small handful every spring and haven't seen a single thrip or mite on any of my plants.
Sooo… idk, it definitely gets a "worked for me".
The plants are: a cherimoya, kumquats, figs, a banana, two monsteras, and a bunch of pitahayas (although the cuttings are only 1 year old and haven't found a permanent home yet), hoyas and a small pineapple.
Looking forward to hear everyones experiences with this!
view more: next ›
I hate LED manufacturers so much.
Assuming state of the art efficiency of 200 lumens per watt, this LED bar would consume about 50 watts. Since bars, spots and stripes never reach this efficiency they are most likeley producing ~100 lumens per watt, so 100w for 9600 lumens.
Point is: they probably lied in the marketing material.
Btw., not shitting on you. The reason LED manufacturers lie so commonly is that people generally don't know how much light a lumen is. 9600 lumens are double most car headlights.