21–30 of 196 posts
Definitely only do one of these at a time, tho :)
Seems to be this article is about when your product is bleeding-edge tech, but people are commenting as if it were about building your product using bleeding-edge tech (in-house or otherwise). Definitely only do one of these at a time, tho :)
All of the comments for some reason are about not using latest-nosql-db-from-producthunt in prod.
Lol. I'm an embedded engineer, and this week I'm getting my coworkers excited to upgrade part of our system to use bleeding edge technology from the mid 90's!
Just getting hardware upgraded from very early 2000s PICs to ARM chips has been a pretty big win for me
Earlier quoted context omitted.
Kube is great. Abstracts away lots of problems. If you make a single kube cluster (which is trivial with eksctl) you can iterate on a number of startup ideas pretty quickly on it. The kube API (the pod/deployment/service/ingress structure) is where the magic is, imho. Sure you could just make an EC2 instance, and swap in your Rails, and redirect the ALB and fix your domain CNAME, but whatever man, you can do like 4 o…
You know what abstracts away all those problems but doesn't require hours a day of mucking with scripts? Google App Engine. Heroku. Elastic Beanstalk.
You have to toe the line a bit in startups, you want to use proven technology but leave room for the employees to feel like they are contributing to something new and unique.
Why? I would advise finding better employees who respond to contributing to a solid business, and in return their own paychecks and bonuses.
Earlier quoted context omitted.
Kube is great. Abstracts away lots of problems. If you make a single kube cluster (which is trivial with eksctl) you can iterate on a number of startup ideas pretty quickly on it. The kube API (the pod/deployment/service/ingress structure) is where the magic is, imho. Sure you could just make an EC2 instance, and swap in your Rails, and redirect the ALB and fix your domain CNAME, but whatever man, you can do like 4 o…
You know what abstracts away all those problems but doesn't require hours a day of mucking with scripts? Google App Engine. Heroku. Elastic Beanstalk.
Yeah, definitely Heroku over k8s for idea validation.
I think there's definitely room in the k8s-based space for slightly past that, though.
You have to toe the line a bit in startups, you want to use proven technology but leave room for the employees to feel like they are contributing to something new and unique.
We are still on RethinkDB but know we have to get off it eventually :(
There's a distinction to be made: - If your business doesn't rely on new technology, then avoid bleeding edge tech (examples: you retail co-working space, rent apartments, do food/grocery delivery, etc.) - If your business model does rely on new technology (examples: airlines in the early 20th century, railroads in the early days of the steam engine, e-commerce in the early 2000s) then you have to work out a way to d…
>Though even in the latter scenario, it's still prudent to narrow the scope of your bleeding-edge tech as much as possible (e.g. if you're doing a cryptocurrency app, you probably shouldn't be trying to make your own NoSQL database at the same time). Nonsense, the database is the back up plan so you can pivot to a DB company if your main thing doesn't work out.
It feels like I'm moving a brick around. Was going to return it, but now I'm saving it for a protest.