Yeah, or their parents argued a lot and they don't want to end up in a relationship where this is the case. This can also mean they're quick to exit a relationship as soon as the first conflicts need to be resolved, because it feels like a sour relationship to them.
- 帖子
- 29
- 评论
- 1849
- 加入于
- 6 yr. ago
- 帖子
- 29
- 评论
- 1849
- 加入于
- 6 yr. ago
That "l" is an L. 🙃
Many years ago, I was working together with a girl my age for about 3 months and I had decided pretty early on that I didn't want to impress her, but that I would use the time to work on smalltalk and such. It was a factory job with lots of boring tasks, so there were lots of opportunities to entertain each other.
After 2½ months, I felt like I was doing better than I've ever done in my life. Then she hit me with the sentence: "I don't think any girl would want to go out with you, because you don't talk enough."
So, basically worst case: That's genuinely what she thought.'Best' case: She was trying to hurt me, but well, she still knew which wound to poke into, so I guess, I wasn't doing that great either way.
Oh yeah, I do think
setTimeoutexecutes in parallel, so only the largest element determines the execution time. It was difficult enough to make that sentence make sense, so I didn't want to cram that detail in as well. 🙃I mean, it does scale with the size of the input. Just not with the count of inputs, but rather the size of each input element.
I agree in general, that a crash is much better than silently failing, but well, to give you some of the nuance I've already mostly figured out:
- In a script or CLI, you may never need to move beyond just crashing.
- In a GUI application or app, a crash may be good (so long as unsaved data can be recovered), but you likely need to collect additional information for what the program was doing when the crash happened.
- In a backend service, a crash can be problematic when it isn't actually necessary, since it can be abused for Denial-of-Service attacks. Still infinitely better than failing silently, but yeah, you gotta invest into logging, monitoring and alerting, so you don't need to crash to make it visible.
- In a library, you generally don't want to trigger a crash, unless an irrecoverable error happens, because you don't know where it'll be used.
Currently implementing error handling for a library I'm building and the process is basically to just throw all of the information I can find into there. It makes the error handling code quite verbose, but there's no easy way for me to know whether the underlying errors expose that information already, so this is actually easier to deal with. 🫠
That is a good tip. Unfortunately, I am too
fishto understand it. 🙃I just type
psand in 9 out of 10 cases, my shell suggestsps -ef | grep <process-name>. So, it's actually less for me to type than "pgrep"...Ah, that was a brainfart. I do use
pkillprimarily. I just use the other command, when I'm not sure what the process is called...Yeah, I especially don't understand it here, because it's a graphical tool. You don't have to keep backwards compatibility.
Even if you're worried about people depending on the format that's being piped, you could keep only the piped format stable. We have the technology.
Yeah, I would often just grab
htopbecause I had no idea how to read the CPU usage out oftop.For example, for me it says:%Cpu(s): 0,4 us, 0,4 sy, 0,0 ni, 98,8 id, 0,0 wa, 0,3 hi, 0,0 si, 0,0 stNow that I look at it, I can guess that
usandsyare supposed to beuserandsystemtime. And I guessidis supposed to beidle.I have no guess what the other numbers might be, though. And well, I would often like to see the CPU usage per core.Now I know that I can just press1tand get effectively the same view as inhtop.I might learn
top's filtering workflow, too. But so far, I always killed processes withps -ef | grep <process-name>and thenkill <pid>, which isn't particularly more cumbersome, so will see...What terminal emulator are you using where ctrl-c copies instead of sending SIGINT when text is selected?
I know that the terminal emulator built into the JetBrains IDEs works that way...
Dried lentils don’t need to be pre-soaked, but I prefer to cook them separately and drain the water they boil in.
Pre-soaking lentils (and pouring the water away) makes them easier to digest, in particular it makes them bloat you less.
https://farmhouseguide.com/benefits-of-soaking-lentils/
An exception are dehulled lentils, like red lentils. They don't need pre-soaking and are quicker to cook, too. I often throw red lentils into the cooking water with my noodles or rice, just to add some protein into the meal.
Last year, money was running out in our project and the guy who had trained me decided he'd take the L and move to another project, so we could continue in the project. And yeah, suddenly I was in the role of the lead developer.
Like, don't get me wrong, I would've been the one to be moved to another project, if I wasn't up for the task. It's not like I was a complete dumbass.But it did still feel more like "I guess, we doin' lead development now" rather than something I had intentionally worked towards.
I mean, depends on the country. Labor laws here in Germany mean that it's worth investing into workers and when you have invested, it costs you significantly more when they quit than if you just paid them reasonably.
If we leave realism aside for a moment, though, the difference is that:
- a carry slot limit restricts how many distinct kinds of items you can have, whereas
- a carry weight limit moreso forces you to leave behind duplicates of items or to e.g. make a choice between heavy armor vs. having auxiliary items.
It depends on the game what's more fitting for the overall design, but yeah, ultimately you want to prevent the player from optimizing the fun out of the game.Having very heavy armor or dozens of healing potions can be boring, since there's no risk anymore. But having one of each different kind of item can also kill the fun, because having the perfect solution for every situation is just as boring.
Yeah, and you'd often get a separate junk inventory, along with a one-click button to sell everything from there. I guess, at least it was an attempt to solve the problem...
I doubt the details make for a particularly riveting story, but just to say it: I do think it is more complex than her just not being a good person.