>What's the alternative? A customer service job where you can be rude? There are cultural norms which we all have to obey in a workplace.
Yes, it is a cultural norm. It varies from culture to culture.
There are lots of countries / cultures where "neutral" customer service - say, at a restaurant - is perfectly fine. Others have a baseline expectation for "friendly" service. To the latter, the former might come across as rude...
When visiting the US, I time and time again started telling service staff about how my day was, because they seemed so sincerely happy to meet me and interested in how I was doing.
That’s the number of cases being directly linked to a specific cause, it doesn’t mean that the actual number was 400/year. It’s like someone trying to estimate how much violence exists from watching the news. You’re likely to see major incidents, but you can only estimate the actual total.
I wouldn’t be surprised if it was well over 10k/year, but the CDC is conservative with their numbers for good reasons.
Also worth noting that there can be incidents where a massive number of people are infected in a short span.
> with the largest sickening over 2,000 water frolickers in one go.
Lots of people experience isolated events of food-borne illnesses for a variety of reasons. But when a restaurant gets 2000 people sick in a short time frame, we shut it down...and correctly so!
The average annual rate is not terribly informative for making effective public health decisions because it smooths out most of the interesting bits.
For public health decisions I agree, but I'm not making those decisions.
For private health decisions (should my family go to a splash pad or not) the average rate, or chance of infection from one visit relative to other activities, would be more relevant.
The functionality looks very very cool. But the privacy policy raises an eyebrow - am I overreacting?
Usage Information. To help us understand how you use our Services and to help us improve them, we automatically receive information about your interactions with our Services, like the pages or other content you view, the searches you conduct, and the dates and times of your visits.
Desktop Activity on our Services. In order to provide the Services, we need to collect recordings of your desktop activity while using our Services, which may include audio and video screen recordings, your cookies, photos, local storage, search history, advertising interactions, and keystrokes.
Information from Cookies and Other Tracking Technologies. We and our third-party partners collect information using cookies, pixel tags, SDKs, or other tracking technologies. Our third-party partners, such as analytics partners, may use these technologies to collect information about your online activities over time and across different services.
[...]
How We Disclose the Information We Collect
Affiliates.We may disclose any information we receive to any current or future affiliates for any of the purposes described in this Privacy Policy.
Vendors and Service Providers. We may disclose any information we receive to vendors and service providers retained in connection with the provision of our Services.
We work with fortune 500 companies and have HIPAA compliant offerings, so we are very sensitive to privacy and security concerns. Fundamentally the models need to operate on whatever browser tasks users ask Autotab to perform, and we need to use frontier vision models like 4o and Claude to reliably perform them (model providers are the affiliates in question). If you have specific concerns happy to answer them.
Your response doesn't seem to address the Privacy concerns raised. Why is the policy so broad and invasive? There's no mention of how you handle PII data collected as telemetry.
This comment lists most of the questions I would ask. Couldn't agree more. Only advice I would add for the OP:
Check if your contract with the vendor includes any business continuity clauses. What happens to their solution, their code, and your data if they go out of business or get acquired (by someone else)?
One relatively common option is to have them put their code in escrow, and get access to it if certain events happen. You can probably negotiate this into your contract if you have enough leverage.
If their software is critical to your business, and you feel they are stagnant and underfunded, there may be some risk here you can address today - check with your lawyers.
(also, just noticed the username I'm replying to... hi Teren!)
Indeed - good point to ensure business continuity. There should also be a transition period to ensure OP, you’re getting support (like 6 months of service) in addition to code that allows you to address the issue if the vendor does disappear.
As CEO / owner of a small business... god I hope so, where do I sign up!
The article lists a couple examples of “virtual” CEOs. Disappointing not to see any kind of critical thought or analysis on what that actually means in practice, beyond a pretty transparent PR gimmick to get headlines for those companies.
I am fascinated by this - how wildly different experiences can be in different pockets of the industry.
The only way I can see 400k+ salaries is if your requirements are a very restrictive Venn diagram of:
* Geographical location (assuming in person, Bay Area / SV?)
* FAANG experience (is it an actual requirement?)
* Seniority (does not necessarily translate to ability... but it does translate to higher asking salary!)
* Niche technical or industry skills
* Golang experience (which wouldn't explain 400k+ by itself, but may restrict the candidate pool further)
If you're seeing $200/hr, that is high but not unreasonable for a good freelancer and smaller engagements. $400k for a 1 year full time freelance contract is pushing it. $400k/year for a salary position seems borderline crazy to me!
To make it more explicit, the term comes from “castle moat” - a form of defense that makes it more difficult for others to attack your castle (or in this context, more difficult to compete with your product/company).
Yes, it is a cultural norm. It varies from culture to culture.
There are lots of countries / cultures where "neutral" customer service - say, at a restaurant - is perfectly fine. Others have a baseline expectation for "friendly" service. To the latter, the former might come across as rude...