This article sums it up perfectly. I was interested in building a compiler long before going to college and this was the most accessible body of work.
Building a recursive descent parser from scratch was an eye opener to 17yo me on how a seemingly very complex problem that I had no idea how to approach can be made simple by breaking it down into the right primitives.
You can do this with SES on AWS or Mailgun.
We use SES for this exact use case. Giving agents programmatic access to an email inbox and programmatically creating inboxes.
The problem is, it's not necessarily the job of the person who is tasked with doing it.
These are the kind of things that fall between the gaps in smaller companies and there's no expert to build this disaster recovery plan because there is no risk or compliance department.
It falls into the lap of whomever is dealing with the audits or whoever has a reputation for getting things done and unblocking people.
Shoe Dog - Phil Knight.
A great read about the struggles of how Nike started. But was left unsatisfied as the book ends with the company going public but doesnt cover its ascension in the late 80s/90s and how that went down.
>I perfectly understand the rationale behind the pricing model. The point is that "only large enterprises need or care about SSO" is completely wrong-headed and detrimental to the overall security posture of any business customer. That is and should be unacceptable.
I made this comment the last time the SSO Tax question came up: We routinely deploy our platform to large customers for 6 or 7 figure contracts.
The number of them who actually deployed SSO (without just asking if we comply with it) is less than 20%.
We routinely sell mostly to large enterprises. Yes, its not proportionally more difficult than selling to SMEs.
However the problem with enterprise accounts are:
1. They hijack your roadmap. You go into danger of building one-off features and bespoke software
2. Your risk is concentrated into fewer accounts. When you lose an enterprise customer you risk disrupting your cashflow and quarterly targets
3. If you dont yet have product market fit it becomes more difficult to achieve it (related to point 1)
Or equally likely he's on his way out? If there is doubt about whether a person of his stature belongs on the leadership team or not, it seems to signal that he won't be on the leadership team.
How much of OpenAI’s success can you attribute to sama’s leadership and how much to the technical achievements of those who work under him.
My understanding is that OpenAI’s biggest advantage is that they recruited and attracted the best in the field, presumably under the charter of providing AI for everyone.
Not sure that sama and gdb starting their own company in the same space will produce similar results.
Dropbox for everything except photos, videos and security-related info.
I used to keep photos and videos on an external hard disk with a jwz-style backup mechanism and Lightroom 3 for organizing it (kept the light room database file on the hard disk itself)
Now just gave up and use iCloud Photos. Not as good as Lightroom but can't find anything better that's also easy.
Secure details go into 1Password with a printout of emergency keys in a wardrobe under lock.
I used to use Evernote but moved away from it soon after they started introducing chat and a bunch of crap no one cared about.
I keep copies of often-referenced items from Dropbox in Apple Notes but the master copy is a file in Dropbox.
I'm using the Shortcuts app on the phone to take a receipt from an online payment and file it away in the /receipts folder in Dropbox.
I used to have an IFTTT integration to take all the photos I posted on Facebook and keep a copy of them in a Dropbox folder as well. It probably still works but I don't really post stuff anywhere any more.
Building a recursive descent parser from scratch was an eye opener to 17yo me on how a seemingly very complex problem that I had no idea how to approach can be made simple by breaking it down into the right primitives.