If you run a build command on the CLI, it should tell you the full type names...
Ephera
joined 5 years ago
The conventional ternary is structured like a normal if-else. In fact, in many languages with functional influence, they're the same thing.
For example, you can write this in Rust:
let vegetable = if 3 > 4 { "Potato" } else { "Tomato" };
Those also happen to be errors you'd typically run into, if you don't yet really know Rust...
Well, I happen to separately ~~only eat foods that don't cast a shadow~~ do the vegan thing and my genes don't like the taste of onion either, so uhh... 😅
But still good info. I haven't yet tried cooking whole-grain buckwheat myself, so knowing a combination that works, I can figure out substitutes or other combinations which are likely to work.
According to the screenshot I took, it was a gargoyle berserker with an axe. I had some ridiculous luck with armor drops, so basically every resistance was either maxxed or close to it. I only really got into trouble down in Zot:5...
And hmm, I should do more with Lugonu. I never really have a reason to pick him, but that means I also don't experiment with him, so I won't really learn what reasons there are to pick the guy...
I actually do, yes. Hundreds, if not thousands, of hours played and I made it down there and back out exactly once. 🙃
I just searched that name to see if it's the guy I had in mind, too, and typoed it as "Chris Ecans". So, I guess, he's a pokemon now.
I recently figured out that wheat/gluten FUBARs my health, so even just the concept of cereal grains has recently exploded in complexity in my head.
Before, I was eating:
- wheat (incl. durum, spelt, rye, and rarely barley, emmer)
- oats
- rice
Now I newly eat:
- buckwheat
- millet
- quinoa (in like three different colors)
- amaranth
- whole-grain rice is apparently pretty cool
- maize/corn (in the form of polenta and tortilla)
I like the cello a lot.
Only in 3D. In 2D, you slap some pixels on top and there's your scarf:
El Camino Real by Alfred Reed has a nice oboe solo.
The problem is that corporations are not holistic organizations. In theory¹, a company could not have any juniors and always just hire seniors from the outside. And if your boss has reason to believe that this is more cost-effective, then they have to strive for that, even if they're well aware that it cannot work when all companies strive for that.
¹) In practice, I've actually found that juniors are important, too. If you staff a project team with only seniors, you quickly end up in a situation, where they don't talk enough to each other. They know how to solve things technologically, so they don't need to tell each other about their challenges and what solution they chose.
Similarly, you likely end up in a situation, where only big problems are being tackled, because everyone can tackle big problems and they're just very visible, highly prioritized problems. But when you add up enough small problems, they become just as problematic.