HN user

dr01d

125 karma
Posts0
Comments33
View on HN
No posts found.

1. No sorry. Slack is already too chatty with bots and I end up leaving channels with git related output. I like to do git things in GitHub,gitlab, or terminal where I have full access to the toolsets. Email serves fine for notifications on PRs or things I have marked as watch.

2. No.

3. I don't think so. People seem to be quick to add these types of integrations but after 500 messages from git activity everyone ignores them or turns them off.

All my opinions of course. Maybe other people will love this.

I'm using opencv with facial detection running in the browser as JavaScript. The technology is here and isn't going away.

Realistically, smartphones are tracking everyone all the time and provide rich datasets. Camera, microphone, and GPS. If you turn off location services your phone still connects to cell towers, WiFi access points, and Bluetooth beacons, as you drive or walk around throughout your day.

If I liked Alexa... I could see myself being into this product.

Whether you like it or not you will be in their product if people are walking around in public or at work while wearing these. Isn't the future great?

The value prop isn't for the consumer, it's for Amazon. Stuffing Alexa into anything and everything means more usage overall and a more attractive platform for companies looking to sell their wares.

Zero maintenance? What about standing up multiple environments for staging, prod? Sharing secrets ,keys, and env vars? Deployments? Logging? No migration time down the line? I'm pretty sure GCP, Azure don't have Lambda, SQS, or EC2 load balancers so you absolutely will have migration time if you have to retool your implementation to switch cloud providers or products.

In most cases, very few companies have products that need to scale to extreme load day 1 or even year 1. IMO, instead of reaching for the latest shiny cloud product, try building initially with traditional databases, load balancing, and caching first. You can actually go very far on unsexy old stuff. Overall, this approach will make migration easier in the cloud and you can always evolve parts of your stack based on your actual needs later. Justify switching out to proprietary products like lambdas, etc once your system actually requires it and then weigh your options carefully. Everyone jumping on the bandwagon these days needs to realize: a LOT of huge systems are still rocking PHP and MySQL and chasing new cloud products is a never ending process.