.net's System.Web and System.IO. Most of the code I write seems to use them somewhere. They're quite old, and not particularly well factored by modern standards, but I like their straightforwardness.
Yes. In the end I hope that it's only the minority of people exploiting it and that it does more good for the people who cannot afford to pay for something.
19 comments
[ 2.9 ms ] story [ 52.8 ms ] threadWrote an article about how to write Alfred workflows in Go too here: https://medium.com/@NikitaVoloboev/writing-alfred-workflows-...
- Segment (backend event tracking and frontend management of things such as Google analytics)
- Intercom (frontend customer chat)
- Stripe (payments)
- Slack (we use the Api to correspond chat users with user accounts, and to create private channels for ongoing jobs)
- Sentry (error tracking with lots of additional information)
- Kubernetes (local and production application hosting setup)
- Contentful (CMS for our blog)
- Imgix (CDN that resizes photos on the fly - which we use for profile photos and logos)
- [0] https://github.com/rwieruch/purchasing-power-parity
- Stripe (payments)
- PipeDrive & Intercom (CRM integration)
- Zapier (some automation between systems)
- Rollbar & Sentry (error tracking)
- AWS S3 (file storage)
- AWS Route53 & CloudFlare (DNS)
- AWS EC2 APIs (Infrastructure provisioning)
- AddSearch (search)
- Freshdesk (tickets)
- Sendgrid (email)
- Google Recaptha (captcha)
- APILayer (tax)
- Monitis & Uptrends (monitoring)
- Browserstack (browser automation)
We use 100s of services (https://blog.ably.io/94-tools-you-need-to-grow-your-startup-...), but I've only listed the key services where we integrate with their APIs.