1,492 karma · joined September 22, 2008
There is so much randomness that I, as interviewer, decided on the following strategy - put candidate into best possible position and judge from that. I settle on one set of questions - "tell me about your most favorite project, why, and let's discuss in detail". If candidate knows his/her stuff - this is fun/informative discussion. Also easy filter if a candidate cannot say much or doesn't understand details of project they consider their favorite.
The value is very large for me - instead of reading page of Claude produced prose, I mostly just look at focused choices and continue with single button press - significantly less Claude deciphering and typing now. In addition, I do my sessions with /rc so I get nice form on mobile app where I can just select a button instead of typing to continue work.
PS: I think there is confusion in term - "every turn" - I don't mean every tool call, I mean after minutes or hours of agent work when agent decides that its done it gives a report. The report I see now has structure to it with options set to continue (or stop).
I'm now running NVFP4 quantized both weight and cache on my RTX5090 and getting excellent results: 264k cache allocated for pool, 10k tok/s prompt processing, 200 tok/s generation for single stream, or 801 tok/s generation for 8 concurrent streams. Also have about 2Gb vram left for use of OS.
my coding agents regularly reach 200k context used without noticeable degradation.
P.S. I used setup from: https://github.com/seanyourhighness/vllm-sm12x-nvfp4-dflash2
P.S. Although my wife insists that I should stay polite in case AI overlords remember how I treat them ...
- they would not change much on battlefield - there is no large concentrations that you can nuke - everything is dispersed
- nuking urban centers again won't change much on battlefield but would alienate China
- Russia's equipment is known to be not most reliable/maintained and worst that can happen to Russia is them trying to nuke and nukes not working
``` c = Sector(radius, start = 180°, end = 270°).translate(y = radius); ```
Programming language that requires (maybe it does not require, but then example is not good) to type degrees. Or maybe it is not designed to be typed and rather ai generated?
Edit: mostly speaking about Model Y, as Model 3 had actual refresh recently.
That's old news. If build quality is your only concern, I suggest you to check them again. They supposedly improved build quality significantly after initial rollout of M3. As a data point: my family owned and drove 6 different Teslas over last 3 years - we did not have build quality (or any other) issues with any of them. All recent horror stories you heard are because of current Tesla scale and media negative bias against the company - you don't hear similar stories from other manufacturers.
How do you know this? Did you see their internal data? There are lots of anecdotes going around about Tesla's quality. However, with all the TeslaQ it is hard to believe that there is real correlation between anecdotes and data. Here are my anecdotes - I owned 6 Teslas over last several years. Not one of them had any QC issues. I had one service done because I hit tire debris and front break dust shield started making noises. Tesla fixed that for me quickly with no charge. As for the data - during earnings calls they mentioned that they do pay close attention to their customer experience data and they had period of time where service was lagging. But they started addressing this issue and saw improvements. The way they are growing I do believe they need to keep close eye on customer experience, but looks like they understand that themselves and use data to make sure they are on top of this. Unfortunately there's not much reliable independent data to have better understanding of this issue.
Add: The intent of my comment was to ask if parent info is based on specific data or just anecdotes. As an example, I gave my own anecdotes and mentioned that they are not reliable correlation to the data. Somehow the responses I've got are all about anecdotes, mine or others, also some personal judgement of my ability to appreciate cars or judgment of my life circumstances that required me to have these many Teslas. Can we get back to discussing the main point I'm making - do we have data to make any of these judgements?
I, myself, don't see how this can be more competitive than superchargers. But I do see that some customers would like to have this option.