Like a QA engineer probably isn't directly tied to overall revenue, but it is a topline number that can be applied to everyone generally, so it can get used (in a general sense, I'm sure there are lots of specifics and nuances here).
5,096 karma · joined July 12, 2020
Like a QA engineer probably isn't directly tied to overall revenue, but it is a topline number that can be applied to everyone generally, so it can get used (in a general sense, I'm sure there are lots of specifics and nuances here).
It sounds arrogant, to me, to be so sure you know what the outcome will be of a given situation, considering all of the necessary ingredients for that outcome have existed for some time and what you claim is "inevitable" has still not happened.
Part of being a free person is the ability to choose how you spend your own time. Just because you consider other people's choices to be a "waste", doesn't mean a) the time is indeed "Wasted" or b) that the people making those choices want to change their decision and can't.
I will not hire someone who holds this view, straight up. It's the only technical belief (aside from crazy things like don't care about quality) I can think of that would instantly disqualify a candidate in my mind. Everything else feels negotiable and perspective-relevant, but not this.
It's such a massive waste of time to try and rewrite functionality that already exists elsewhere, and an inability to trust other people is a huge, bright red flag when it comes to working with others on the team.
Being very selective of which libraries you use? Sure, fair. We can talk about various lines and where to draw them, but categorically denying library use? That's unacceptable.
How else would you prefer this to be? Of course a majority of Senators get to control the agenda…
My argument is not that it's fine as long as the likelihood for abuse is low, my argument is that it's fine as long as there hasn't been any actual abuse. When something does happen, we can respond to it.
Until then, it's not reasonable to go through a bunch of worst-case scenarios.
We all deal with "sky is falling" person on our development teams, and it's pointless doomsaying then as it's pointless doomsaying now.
When the bad things happens, we can react. Until then, let's try to stay reasonable.
A numerate person would know how rare these things you're afraid of are, and not let those fears drive how they live. I (hopefully) follow that path, and I recommend you check it out!
I read what you wrote in the same way I suspect you would read someone who is afraid of space because meteors have killed people (as a rough example).
It just doesn't seem like the rates at which the things you're worried about are happening in a volume that would actually matter to a society.
Google is smart enough to know that "snitching" on its users is bad for business.
Think "track a burglar as he moves through a neighborhood" not "snoop (illegally) on the contents of people's mail".
I'm not denying the right exists, I'm saying we give up our other rights all the time for the benefit of society, why is privacy any different?
Further, it's a spectrum. You're not putting a camera up for police to peruse at their leisure, it's only in specific situations.
Sometimes I think people covet privacy for its own sake, and don't think about the practicalities. The whole point of living in a collective society is that we give up some freedoms for the sake of overall increased prosperity, that's always been the tradeoff, and this is just one of those tradeoffs.
Up to you.
Very, very few people are paid to find the "optimal" anything. The trust you're looking for can be found once you recognize what it is you're actually being asked for (again, rarely 'optimal', just 'functional').
The real, fundamental mistake being danced around here is the failure to recognize the inherent tension between product and engineering.
Stop fighting, start harmonizing. Understand how you fit into the bigger picture, and “deadlines” vs. “complexity” will start to make more sense.
It’s obvious that you aren’t going to make money off of nothing, so you have to build something, and it’s obvious you can’t build something out of thin air, so figure out how to build small, specific things that people will pay for.
The biggest benefit from this redesign is the very clear insight into billing you now get. Right on the main page, you see your billing breakdown, both from a "here's what you've spent this much" and "here's your projected spend" perspective.
That, alone, was huge, and required a new UI to display that information cleanly and clearly.
Cognito's UI is now substantially better, as well. Before it was very different from the rest of the site and therefore unintuitive, and it's now matching.
There are other examples, but suffice it to say the folks claiming the "old UI was better!" are not doing so from any place of reasonability.
So yes, can all of the folks who fear change please hop on whatever mode of transportation you prefer, and leave those of us who understand that progress is, generally, good alone?
Okay, you and I care about very different things.
[0] https://www.health.harvard.edu/mental-health/the-power-of-th...
I wish it were easier to see the moments when demand and capacity were at their closest, as those are the "interesting" moments.
You can very successfully write code that runs on Linux on either MacOS or Windows, depending on what you're developing.
Probably not a big deal, but just seems pointlessly narrow to think all developers would or should prefer actually developing on Linux exclusively.