IMHO all these companies are flooded with account managers, sales, customer success, BDR, when they could just let customers choose their own plans, upgrade freely, etc, instead of "schedule a call with our team"
Companies do that because it works. Early in Twilio’s life (pre-ipo) the company was very adamant that outreach and negotiation are not needed for SaaS. Jeff Lawson (the CEO) would regularly mock and lambast companies for having a pricing page that said any variation of “contact us for pricing”. There were some pretty dramatic reorgs and management departures because of that attitude. Lawson eventually relented and adopted a more hands-on growth model and growth went up.
Before the change, the company was really struggling to attract blockbuster customers. The growth strategy was (and still partly is) to have startups get hooked early by the quality and just never leave as they grow. For the longest time their biggest customer by faaaaar was Uber, and that happened because both companies were created and grew together. Once the hands-on outreach started, they started getting meaningful revenue from giant multinational banks and manufacturers that have a ton of money but, frankly, don’t empower their developers to choose the best tools for the job.
I completely agree. Use anything except LastPass, I found it to be really buggy, which makes me wonder how secure it can be if bugs that users notice don't get fixed. Granted I haven't used it for a couple of years, but I'm never going back.
I moved from LastPass to Bitwarden a few years back. Bitwarden does win a few kudos points for being free and open source. Unfortunately, Bitwarden is far from perfect either. It suffers from glaring UI problems which the developers have point-blank refused to address, insisting instead that that is how it is supposed to work --which is incredibly arrogant and 'Jobsian'... "You're using it wrong!"
You don't need to wonder, Google for "lastpass vulnerability" and "lastpass breach" and read from the many results. They do not have a particularly decent security track record.
I don't normally comment on HN but reading all the negative vibes made me want to comment.
Glad to hear you are doing great! I had to make the decision between a high paying job and a high rewarding job and choosing the second one has been a huge improvement in my life.
Indeed the HN community seems to manage the ‚issue‘ in an overall happy tale. I doubt there are many in a long relationship which did not suffer for a time due to external and not so well understood circumstances. Pull through and better self/us understanding and a stronger relationship can be ahead.
+1 to AWS Step Functions, in my last three companies I have built fairly complicated workflows with them and once you get used to them they are very powerful, reliable and cheap.
I just wish a little bit more monitoring on top of them but nothing you can not build by yourself.
This will only benefit recruiting firms in order to automate processes such as the one behind this project, I don't see how this would be beneficial for anyone else.
Let me give you a couple of use cases where a standard CV would be beneficial to workers.
1. You want to apply to one position but you only have your data on LinkedIn. If you wanna export it, you only have PDF as an option. You can't adapt or update it.
2. Even if you can adapt or update it, if the company or service where you want to apply doesn't support a standard format, you will have to re-enter the data, one by one.
Finally, all this friction discourages some candidates to apply to some positions.
1.- If you are really interested in the job you spend a few minutes preparing the CV and applying for it.
2.- If the company doesn't support a standard format is probably the company's problem not yours.
"Finally, all this friction discourages some candidates to apply to some positions."
Doesn't this just validate that the benefit is for recruiting firms rather than applicants?
It locks you down to that ORM. If you are the owner of the ORM such as Google with Looker that is fine, otherwise it doesn't sounds like a good idea to me
I forgot to mention on the posts what are my thoughts so far:
- License products such as Tableau, Qlikview or PowerBI are too big for us at the moment, both in size, pricing, complexity, etc.
- Scheduled exports to Excel/csv don't solve our use-case as it needs our interaction every time there is a new export or change in the queries.
- Accepting requests directly don't scale well either.
- Currently we are considering Metabase, Superset and Redash. Leaning towards Metabase based on better UI, runs well in AWS and connects to SQL databases, Mongo, Redshift and Clickhouse (Not that we use all of them but we may in the future)
LaLiga already does this, they display a "B" on the corner and every few minutes a code that can be checked against the subscription, but this doesn't seem to be enough...
