sthomas1618

Ya I’m curious too. How would you switch to Twilio without doing the coding yourself?

Is that take from the gut or is there data to back that up?

I've worked worked developers that have a hardline against ORMs. I see lot of their points, especially around the performance of raw SQL. But I cannot get past how much boilerplate code that has be written over and over again. And then you have to test that boilerplate code. I find that most people are far more productive using an ORMs. To me this makes sense because it's less things to type. Less is often more.

We have services that don't ORMs and I have to wonder if it's worth the cost.

Note to others: Try not to defend yourself in an apology. Otherwise it ceases to become an apology, and instead becomes a list of reasons why there should be no accountability.

To add on: cancellation === accountability. Which many people seem to forget.

I'll give you that things are hardly ever binary. But toxicity is something that can be determined. They are the people do not care about others. They do not listen, no matter how many times you've talked to them. They see themselves as correct in their attitude, and others wrong. They do not change, or at least not in the short term (and definitely if they never suffer consequences). I've worked with these kind of people. We all have.

This whole "good outweighs the bad" is wrong.

1. Toxic people damage the company in general. Whether that be the reputation or culture. The consequences of their actions and words waste company resources.

2. They damage the productivity of others. Either indirectly or directly.

3. Most importantly: they hurt others. Nothing can outweigh the hurt they cause others.

I could not disagree more. This whole statement is "sorry, not sorry".

If someone is known to be a toxic person (and currently still is), you do not let them on to your team. Ever.

So in case of Oracle, OpenJDK will still be viable?

Let's say Google loses... badly. What will be the practical consequences for us software engineers?

Most expensive "historical" movies are wrong too. Otherwise I totally agree with you. I just don't think how much a movie cost to make matters much with regards to historical accuracy.

I've never understood snapshot tests either. My team tried them early on but abandoned them quickly. Whats the value in them?

In addition to Storybook, their Chromatic product is amazing.

Hot take: Delete your snapshot tests. Use Chromatic instead.

As long as the GDP grows faster then the deficit/interest, we’re good.

Reminds me of https://en.m.wikipedia.org/wiki/Century_Rain

I'm curious about those who use a monorepo with microservices: how do you solve CD/CI? Is Bazel the only solution?

Per the presentation, you would need to weigh the benefits/costs. Since TypeScript is a superset of JavaScript, I would argue the cost of adding is very low. The benefits will be naturally high due to type definitions reducing bugs and cognitive overhead.

Assistants help with this paperwork, which is different for every state and requires hours of reading and making phone calls to decipher.

Regardless of this, this still sounds like a market inefficiency. I have not read the book (but I certainly will now), but I'm going to guess the author's response would be that while the assistant's job is necessary for the engineer to remain productive, it is still a bullshit job. What's needed instead is an automated service that handles this for the engineer at far less of a cost or less bullshit paperwork from government.

Having read (and enjoyed) that trilogy, I'm not making the connection. Which part?

The purpose of prison should be to keep dangerous people out of society

Whatever happened to purpose of prison being rehabilitation? I mean... they are called correctional facilities. Are we so far gone now that we think criminals are beyond redemption and change?

Your secure webdev libraries also break under the same constraints.

No argument there. Different design goals. But I still stand by quality of engineering that open source allows.

This isn't going to work. Latency will make this dead on arrival for multiplayer games.

I'd curious to know what strategies make secrecy a necessity. I come from a WebDev background and open-source libraries are almost always always secure and safer then your own (due to the sheer amount of developers and ingenuity working on one repo). Admittedly, game development is a different beast and has to deal with far more client-code so I'm admitting my ignorance here.

I think he's implying a cheater's injected DDL would be tailored for a specific build, so if they shared it with others, it would be ineffective. And not only that, but based on how the Cheater.DDL is targeting the build, they could identify the account that made the cheat.

That would assume the server is sharing the knowledge of other players through the fog of war.

Agreed. Definitely not trying to say encryption is a poor strategy. But it does seem obfuscation is most of their anti-cheat techniques.

But the larger point I was trying to make is that all these studios are very secret about anti-cheat but they all seem to be fighting the same battle. Makes me wonder if the industry would be better off with cross-studio collaboration and open-sourcing anti-cheat libraries (that won't be defeated by knowing the details).

Aside from strategy/RTS games, I'm not sure if thats even possible? How does is ripping off a popular mod relevant here?

That's good point and their random debuggers are definitely a clever obfuscation technique. And also not trying to say encryption is a poor strategy. The larger point I'm trying to make is that its possible being so secret about anti-cheat is to the industry's disadvantage. Feels like there is an opportunity for many studios to collaborate on anti-cheat tools and techniques (perhaps with open-source). For example, is Riot Game's packer/unpacker a specific solution to their codebase or could it be abstracted and open-sourced? This is a industry-wide problem and studios should be competing for the most creative and fun games, not the best anti-cheat.

I feel like the industry would be better off being transparent about anti-cheat strategies and maybe even embracing open-source. Protecting "secret sauce" is basically admitting their anti-cheat are largely through obfuscation and can be defeated by knowing any details.

Something I've been wondering about: how stable is Kubernetes service discovery? I.e. can it entirely replace something like eureka? Is there any reason not to use Kubernetes provided service discovery?

"Here’s how the hack went down: Two attackers accessed a private GitHub coding site used by Uber software engineers and then used login credentials they obtained there to access data stored on an Amazon Web Services account that handled computing tasks for the company. From there, the hackers discovered an archive of rider and driver information. Later, they emailed Uber asking for money, according to the company."

Seems to suggest they committed AWS credentials into source control?