1,554 karma · joined December 2, 2013
Honestly, it feels like low level fruit ripe for baiting engagement.
Sure it would be cool if it wasn't there, but does it really materially change anything?
Actors will be involved in 99.9% of productions, and people will always be involved. Are they in union with those actors?
"Buying magic from Maria Duval" changes it to fraud assuming that Maria Duval was not involved. Where things become slightly more tricky is that Maria Duval sold the rights to her name to the scam operators before they did the scam.
So now the analogy is maybe "you paid for an autograph from Mickey Mouse, but Joe Schmo signed it instead (you didn't find out until later). Disney sold the rights for Joe Schmo to use the name Mickey Mouse in autographs."
Mickey Mouse as a character does exist btw, as a point that doesn't matter much.
You can't say "Well I thought I was getting REAL magic", because that doesn't exist. You can absolutely say "Well I thought I was getting a REAL car", because it's expected to buy a car, and cars exist.
That's my understanding of why they're striking.
That isn't even the big challenge though. The biggest challenge is getting people to build for your platform. If a sales team uses 10+ integrations (it's honestly probably 20-50), then they will pick a platform that supports 9-10 of their integrations.
You must create an amazing ecosystem to compete. But creating that ecosystem is incredibly difficult.
Honestly, my opinion for how you could maybe make it work in open-source is to recreate the Salesforce API. That's a HUGE effort though, as it has a big surface. (I wonder how much of that is intentional to make it so others can't copy it well.)
My point to that is that it is true, but the lockout would prevent a thief from using it until the new SIM is received. Versus a thief having access until the new SIM is received.
I use telegram instead of Whatsapp, but I would hate for anyone to have any time at all on my account. I'd prefer to immediately lock the whole thing down and figure it out once I have everything sorted.
I traced the problem back to the fact that we had 100+ feature flags that were fully launched, but still loaded into the backend when "all feature flags" were loaded for a team. The way this was implemented returned all team IDs that had the feature flag, and the way this was done had some flags with multiple thousand IDs in them.
So 100+ flags, many with 2000+ int entries.
We ended up quickly shipping some code to mark features GA, so they wouldn't be loaded from Redis. Cut usage by 99% instantly.
No tool you have will solve that, whomever owns the product team time allocation needs to be onboard with the idea of cleaning up old code.
You don't necessarily need to quantify that exactly. If you've worked on a team with people like that, then you know it. Their managers know it too.
To your main point, the size of the markets is drastically different. There is only so much room for headline rockstars and entertainers, but there's way more room for talented technologists. Having "rockstars" in the engineering world doesn't really reduce the size of the pie for others.
edit: it's been out since 2015 it looks like. Not sure why but I didn't know about this before. It would have been useful.
Maybe it's actually a great library, but it feels like I'm giving up control of my queries and letting it run with them.
I prefer to use the batch function and manually resolve the query on my own. It's a little more work but it's pretty easy in the end. And fully controlled.
When I read "I can't stand the way some people write", I get a similar sort of feeling. The intention is not that it is a harsh statement, but to me it's very harsh (although not on the same level as the example I wrote).
To me, this highlights the problem with criticism and why the thread is a bit divisive. It's a gap between intention and perception with different end results based on how feedback is perceived.
The attitude of desiring to learn is what keeps me sane, but I've learned that feedback like "X is bad" often comes from someone's subjective experiences in a particular situation. They then take that and apply it globally. It's hard to have conversation with such strong opinions.
Having a trusted coworker who has a disagreement, followed by a healthy conversation will result in either the change they want, the original staying, or a new solution that's better. Growth can come from all 3, depending on the mindset going in.
I don't understand not feeling bummed out by that type of critique. Sure it's not about you as a person or your values, but dang that sucks.
It's absolutely possible to build maintainable, accessible, linkable, fast modals.
I have no clue why someone would say those things are impossible or impossibly difficult to achieve.
Looked it up and there's a great video from him about wells & aquifers https://www.youtube.com/watch?v=bG19b06NG_w