HN user

UlisesAC4

54 karma

[ my public key: https://keybase.io/ulisesac4; my proof: https://keybase.io/ulisesac4/sigs/yvsU0wZPsXk6T6bG8KPX75y8vkGJJWiYJ_xfDeS6FjY ]

Posts1
Comments75
View on HN

This must be easily benchmaxed because I have never gotten an "idk like" answer for the western frontier models. All my personal "real world" use cases will always resort to hallucinations.

Liability. I work in a tightly regulated market and I cannot use any service due to be in touch with PII data. If it was my option I would just use OpenCode with deepseek, it is more than enough for the majority of my tasks.

DeepSeek v4 3 months ago

This, I have been doing my side hustle code with open code an 3.2 reasoner and it is way better than what I have at day job with copilot and whatever models are there.

To be fair I cannot trust your shape in your jsonrpc, I am not sure if id is truly an integer or if you sent me an integer by mistake, same as params or even the payload of the params' param, this is why we ended adopting openapi for describing http interactions and iirc jsonrpc specifically can also be described with it. At least in the schema part no one would say it is ambiguous, also one does not need do heavier parses, the obj is a tree, no more checking on scaping strings, no more issues with handcoded multiline strings, it is dropped the need to separate attributes with commas as we know the end tag delimits a space and so on.

It is a shame that the people you are answering is being downvoted, I also understand the importance of coloring functions, but look at the examples that person put, python and rust. In those, executing a colored function (at least the async related ones) propagates up to the top of the program, that is a cost that we have to interiorize, but I would be lying if I told you I wouldn't he happy with such behavior. I do a lot of js/ts and I would love to just be able to "inline" await without making my current scope recursively to the top of the program like it can be done with F# with the Async.StartAsTask operation.

Why F#? 1 year ago

You can use adapters via Foreign Function Interface and interact with C++ code. The deal breaker is that memory is separated, C++ code has its own heap and Ocaml too. Quiet different to F# in which operating with C# is seamless and the runtime is the same.

Basically the experience of asian MMORPG since 2006.

Source, played MapleStory alot in the past.

Why the hell

Simple, if you are not there you do not exist. Go and check how many of your contacts follow the oficial accounts of your local government.

Also, the common layman isn't anyone that suddenly gets the urge to check your official webpage, if you are lucky you are in their social media results.

Well, on the other hand, her friend should be able to produce the same content in a 1/15 or even 1/20 of her original time.

The more you know about a domain the better questions you can ask to chatgpt. What people do not get is that due to lack human's creativity it cannot innovate like a human does, it cannot create new knowledge, but it can let you know any existing field as long as you know what to ask.

It does amuse me that we're still at more people hiring than looking for jobs. It's a stark contrast to other industries, where the power is normally in the hands of employers.

I am sure that there is a huge margin of error. I have been looking a job for 5 months. Granted, I have not used Who's hiring threads religiously and I am sure that there are positions that I applied where something with better qualifications was chosen.

If you need temporal variables to give context you have other problems with the naming of the function that you are calling in the first place.

We have used temporal names between function calls not because it was more readable but because chain of methods was not an option as you have said.

I do. I find it better to have the information that I want as static generated in a graphql environment so I can query it wherever I want in the application. Next.js has some "inflexible" rules for the static generated content gathering. For dynamic content both are good.