Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Ramiro
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
1.
▲
Show HN: Run AI Agents on your cloud infrastructure
(okteto.com)
12 points
by
Ramiro
1y ago
|
1 comments
2.
▲
Stop Using Docker and Local Kubernetes for Dev Environments (Featuring Okteto) [video]
(youtube.com)
3 points
by
Ramiro
1y ago
|
0 comments
3.
▲
by
Ramiro
2y ago
Very cool! This is a great example of how ephemeral environments can help for a lot more than just fast inner loops or manual verification.
4.
▲
by
Ramiro
2y ago
XMPP was supposed to be this. There was a boom in the early to mid-2010s (I worked at HipChat back then, and it was built on top of XMPP). IMO, it works well; it scales, but none of the commercial solutions picked up for whatever reason. I
5.
▲
by
Ramiro
2y ago
I'd highly discourage you from using SMS; it's very insecure. I'd go as far as to recommend you not to implement your own auth and instead use something like Auth0, WorkOS, SuperToken, or SSOReady ( https://github.c
6.
▲
by
Ramiro
2y ago
I second this, the SF Public Libraries are a great place to work. I used to work out of the Potrero Hill branch a lot. The main library (the one by the Civic Center) closes way later than the rest. Good spot if you're working alone.
7.
▲
by
Ramiro
2y ago
I love reading these "reports from the field"; I always pick up a thing or two. Thanks for sharing @ianvonseggern!
8.
▲
by
Ramiro
2y ago
Every time I read about Nomad, I wonder the same. I swear I'm not trolling here, I honestly don't get how running Nomad is simpler than Kubernetes. Especially considering that there are substantially more resources and help on Ku
9.
▲
by
Ramiro
2y ago
I agree with @metaltyphoon on this. Even for small teams, a managed version of Kubernetes takes away most of the pain. I've used both ECS+Fargate and Kubernetes, but these days, I prefer Kubernetes mainly because the ecosystem is way b
10.
▲
by
Ramiro
2y ago
I really like the "remote"/ "on-site" / "hybrid" filter. Good job!
11.
▲
by
Ramiro
2y ago
The most significant value I get from Costco is that the quality is consistently high and the options are well curated. I like not having to go through 100s of brands of basic staples like yogurt, toilet paper, milk, etc...
12.
▲
Local GenAI development with Ollama [video]
(youtube.com)
1 points
by
Ramiro
2y ago
|
0 comments
13.
▲
Using Prometheus, Loki, and Grafana to Monitor QuestDB in Kubernetes
(questdb.io)
4 points
by
Ramiro
4y ago
|
0 comments
14.
▲
by
Ramiro
4y ago
I agree is early, but the same thought around WASM crossed my mind. Interesting approach though
15.
▲
by
Ramiro
5y ago
@blakesterz what kind of pain are you feeling when developing with containers on a Mac vs using your Linux box? I know perf is worse, but are you hitting other things?
16.
▲
by
Ramiro
5y ago
This is very cool. Running tests on browsers has always being a pain. Is this something that could be run from within a container?
17.
▲
by
Ramiro
5y ago
I think this something that people miss a lot when trying to optimize their Docker builds. Is the whole optimizing for most of your builds vs optimizing for a specific build. Not easy.
18.
▲
by
Ramiro
5y ago
I never really thought about this, it's a good point. What do you suggest it's used instead of ["npm", "run", "start"]?
19.
▲
by
Ramiro
5y ago
Distroless are tiny, but sometimes the fact that don't have anything on them other than the application binary makes them harder to interact with, specially when troubleshooting or profiling. We recently moved a lot of our stuff back t
20.
▲
Development Environments in the Cloud
(engineering.monday.com)
4 points
by
Ramiro
5y ago
|
0 comments
21.
▲
by
Ramiro
5y ago
Fig's integration for Makefiles makes my life so much easier! I've played with shell autocompletion before, but this way easier to use. Good luck!
22.
▲
by
Ramiro
5y ago
Not yet. We are trying different approaches to curb this since we do want to keep our free tier.
23.
▲
by
Ramiro
5y ago
We have the same problem in Okteto. We've been investing a lot on building tech to prevent this (I gave a talk on this during the last eBPF community days -> https://www.youtube.com/watch?v=tplv3Hjjv2Q ), but it
24.
▲
by
Ramiro
6y ago
There's a couple of approaches we've tried: 1. Register each dev env with the provider. Dev Envs can have predictable URLs (e.g in okteto cloud it's the name + namespace + domain), so you can directly register it. This works
25.
▲
by
Ramiro
6y ago
For debuggers, we wrote a few guides like this one: https://okteto.com/blog/how-to-develop-node-apps-in-kubernet... . > We need to maintain separate profiles for running apps in debug mode, to expose the java debug p
26.
▲
by
Ramiro
6y ago
There's two parts to Okteto. The open source project ( https://github.com/okteto/okteto ), which launches development environments and works with any kubernetes distribution. And Okteto Cloud ( https://okt
27.
▲
by
Ramiro
6y ago
If your kubernetes cluster can support a 16GB pod, it will work with okteto. That said, the pattern we recommend to follow is to split it into smaller dev envs. That makes it easier to manage, and allows you to have dedicated dev envs for d
28.
▲
by
Ramiro
6y ago
There are challenges on this model for sure. A big advantage is that, by routing to the dev environments, you can have the dev interact directly with the webhook when they code, instead of having to wait for a shared environment to test int
29.
▲
by
Ramiro
6y ago
Ramiro here (co-founder of Okteto) I agree that "developers should be sympathetic to the environment there code runs in". But that's about where the code runs in production, not where the developer runs it while coding. That&
30.
▲
by
Ramiro
6y ago
> Even npm watch takes several seconds, let alone docker builds almost always take minutes That's where caching, container layers and build stages can help a lot. Specially for development, where you might be rebuilding the same co
More ›