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.