Randall Degges, a developer and former Heroku and Okta employee, writes about APIs, authentication, services, and developer productivity.
HN links it for his contrarian 'Why I Love Basic Auth' post and his Heroku writing, and commenters mention him in Heroku discussions.
Great writeup. I really appreciate when people take the time to do this. And also to risk dealing with the jackass criticism that usually comes from putting yourself out there on the internet.
One thing that was underemphasized: They built in response to actual need, which was great. If you click through to the announcement post [1], he explains that he had spent 4 years doing telephony stuff, and was always bothered by the lack of an API.
Good for them for taking their small proof of need and building small. And then using that to get more proof of need as a way to justify further investment. That's in contrast to a classic startup mistake, which is to jump in and build something you just think other people need.
[1] http://www.rdegges.com/im-working-on-a-startup/
Sad day, indeed.
I remember meeting @craigkerstiens through Heroku -- I started using it back when they first released a beta Python buildpack. I also made friends with a ton of amazing people over the years through Heroku. It was a magical company with amazing engineers.
Over the years I've written a lot about Heroku on my blog (https://www.rdegges.com/), and even wrote a book on Heroku many years ago (https://www.theherokuhackersguide.com/), which really helped improve my technical writing chops, and got me into the public eye.
RIP Heroku
Upvoted. This is how Postgres supports "fuzzy searching" which helps with misspellings. https://www.rdegges.com/2013/easy-fuzzy-text-searching-with-postgresql/
Completion response-time will be slower than Solr, Elasticsearch, Algolia, etc... but if you're already running Postgres, this may be the fastest to deliver for you.
Environment variables work extremely well when deploying on Heroku [1]. You can't exactly commit a local_settings.py file to your repo, so setting env variables is the only way to exclude sensitive keys and passwords from your source control.
[1] http://rdegges.com/devops-django-part-3-the-heroku-way
dont know whether the facebook bots execute javascript - https://www.rdegges.com/2017/how-to-monetize-your-website-with-cryptocurrency-mining/
Postgres can definitely do fuzzy matches!
[0] https://www.rdegges.com/2013/easy-fuzzy-text-searching-with-postgresql/