Hmm, but weren't you already rating websites by clicking on the search results before? I don't see how that changes the game - and I must admit I don't know much about SEO - but in my view we were always rating results and that was influencing the position. Now they make the linking obsolete or at least less important signal... that's good? It means that relevant content is going to be surfaced to the top. Win-win honestly (and yes, Google will continue to use users-generated signals to drive their revenue like they always have).
This is great! I've been trying to get into local models for a while as I share the sentiment that local models will eventually be so good that there won't be a need to use frontier models for most coding tasks (perhaps that's already true today?).
I have zero experience building computers - where would I even start? I mean, aside from the things already well documented and mentioned in the blog post.
Building computers is very easy. I would suggest watching a YouTube video to get the general gist, and then once you buy the parts, just Google for whatever doesn’t go well.
I built my first Pentium 4 one when I was like six, so I’m sure someone much older that’s into tech can do it without an issue.
There are also tons of Discord communities that are willing to help you live if you encounter any issues.
I agree, but for small tasks - <20 lines that I can understand in a minute or two - perfect. Thinking about it - I have hundreds, if not thousands of tasks that I would like to do, improving pipelines, migrating from one tool to another, but never have time. The only question is - if I don't have time to do it, do I have time to prompt it?
I was thinking for years about doing something like this. Thank you for linking this. Would be nice if it allowed to "reject" or mark a change to fix later, but honestly when it would need to be linked to some tracking tool and it would be overkill.
This is a great idea for some vibe coding tbh and you can customize it to match exactly the resources that you need as everyone has slightly different requirements for their k8s stack.
The simplest way to start probably would just be to create a custom Helm chart and define what you want in `values.yaml`.
The variance is normal, the questions pull from a pool of 138 questions so far. 0.177 is strong. Setting everything to 50% would just get you 0.25, so you did way better on the first attempt. The goal isn't 50/50 on everything, only on the occasions where you are not confident that you are right.
reply