dvlsg

Ironically, this is a pretty good example of why tickets end up the way they do in jira - overly specific and concrete. Even the hypothetical situation is getting misinterpreted.

I would still love it if user stories were implemented as the "why" (or even "what") instead of "how", though.

I bought a Samsung phone (S9) over black Friday. Returned it already. Their apps were incredibly heavy handed and invasive.

The photo app had a hard coded button on top of my camera viewing area which linked a way to buy things via a samsung app. I was appalled. I also couldn't turn off the Bixby assistant without first making a new Samsung account.

Looks like dart even uses an event loop. Their examples for handling futures look very, very similar to Javascript (and typescript, of course).

https://webdev.dartlang.org/articles/performance/event-loop#...

Witnesses for which side? Or was it both sides?

Yeah, we use tsc for node. I typically just use ts-node for development, though, and tsc gets to hang out in CI/CD somewhere. I assume ts-node / webpack / etc all use tsc under the hood, though.

Kind of depends on how "go programmer" is defined, too. I've used go, but I certainly wouldn't call myself a "go programmer" at this point.

Proper code search could be a pretty killer feature on its own. Half the time I need to find something on github I just clone the repo and search from my own computer.

It's always refreshing to see a writer that's honest about trade-offs, instead of spouting their preferred method as the one-true-way which will solve all your problems.

Do they? I'm not 100 percent sure about the npm package lock (because I don't typically use it), but I'm fairly sure that yarn's lockfile will lock the full dependency tree, including the dependencies of your dependencies. I believe npm's package lock will as well, but I'd have to double check that.

If we wanted to be picky, promises technically aren't monads because .then() does too much with auto unwrapping nested promises.

https://stackoverflow.com/a/50173415 has some good examples.

It's close, though. Really close. And don't get me wrong - I still love promises and async / await. They're much better than what we had before.

I wrote a lib that does this too. It's been a while, but using generators tended to be way slower than just using arrays, except in the most obvious cases (array of 1000000 elements, only take 5, no sorting involved, etc). Maybe that's changed. It's been a while since I've checked.

Or if an issue happens in your staging environment but not locally. That happened to me just yesterday, and a simple print statement gave me the information I needed to resolve the issue.

I probably could have attached a remote debugger, and executed the relevant function a few times until my request got routed to the right process in the cluster, but that honestly would have taken me more time than just committing the print statement and letting CI take it away.

Do you have to ping auth on every websocket communication? I feel like you should be able to auth once when you open the connection, and then keep track of the intended session timeout locally (unless you expect external factors to extend that timeout I suppose).

Unless that's in regards to checking whether an auth has been blacklisted, which isn't something jwt solves, as far as I can tell.

Agreed. I saw The Acacia Strain the other night (more deathcore than death metal, I suppose), and in between screaming lyrics like "I am the end of the world", they were talking about making sure to reach out to your friends / family for help if you were having any negative / suicidal thoughts, not to taking yourself too seriously, and tossing glow sticks into the crowd while they played in front of inflatable balloons. I thought it was an interesting juxtaposition.

> Maybe a shopping site that builds carts across various retailers and orders from the least expensive?

Sounds like pcpartpicker. Which is, of course, only relevant if you're trying to buy parts for a pc. Great service though (not affiliated in any way, just a happy user).

> If the code is not formatted to the linter, it should not have been submitted for review and I will probably reject it.

Better yet, make a tool (CI) automatically reject it. That way it doesn't waste your time, and no one has to be the "bad guy".

Not until developers start disabling the linter with inline comments, anyways.

I agree. Something about it just doesn't feel right to me. Like state is stored in a global singleton somewhere.

Any of the examples touch on testing components using hooks? Any chance using the same component across multiple tests would result in state collisions? Especially when testing something asynchronous?

Not blizzard specifically, more Activision-blizzard, but the latest call of duty open beta was reportedly running on vultr for at least some of the game servers.

I think they moved it back to in-house servers when it went live, though, and dropped the server rates from 60hz to 20hz. Kind of a shame, the difference was very noticeable.

I suppose we could blame high fructose corn syrup, then.

In the wise words of the robot devil,

> You can't just have your characters announce how they feel! That makes me feel angry!

Shouldn't part of the journalistic process include making sure one guy isn't going off the rails and making stuff up? I guess that could be part that's broken.

That's a fair point. I remember being especially frustrated by Azmodan, the supposed "most capable battlefield general" _literally_ yelling his secret plans at me in Act 3.

I completely agree, but I would also point out that being manipulative by using an evocative name isn't always great by default. Personally, I think it would be beneficial in those cases (shell shock, battered spouse), since dehumanizing suffering is awful at best.

But then names like the "patriot act" also come to mind. Or for something a little closer to home, "anemic domain models".

I suppose appreciating emotive language would depend on whether or not you agree with the purpose behind it.

I think composition and mixins should be kept separate. In my mind (and maybe I have an incorrect view of it), mixins throw a bunch of new properties on the base object, whereas composition keeps the original object encapsulated in a single property. Would you consider the second type to be a mixin? I've never heard it described that way.

Even for servers? I would've guessed most game servers ran on Linux. Seems like the licensing costs for windows servers would be fairly restrictive for that.

I don't know.. Diablo 2s storyline was quite a bit better than whatever happened in Diablo 3.

Hopefully uncommon, anyways. Imports with side effects sounds like a nightmare to debug.

Taking "machine learning" to the next level, I suppose.

I also hit this limit on Spotify. The super frustrating part to me was that it appeared to save your songs, but didn't. They would be starred until you left the page and came back.

I swapped to Google play music, though. They like to re-upload / move albums around and automatically remove them from my lists without telling me. Not particularly thrilled about that, either.

Yeah, it's pretty bad. Some games try to gamify polite behavior (bonuses for getting tagged as helpful in a dungeon, etc), and that sort of works. Kind of sad that it's necessary, though.

I also think the rude behavior is a combination of both anonymity and "I'm never going to see or hear from this person again".