woud420

There's nothing stopping you from applying for Daybreak for OpenAI / Unsure which program Anthropic has. But yes, you do have to share your identity and I can see how that is a blocker for some.

+1 on all of this, it is similar to the pattern I see emerging as well. For example I have open-sourced (let's be honest, it's just my personal tooling of taste) a repo on gh to try and formalize these things. I'd rather not share out of mostly imposter syndrome but essentially it's a scaffolding tool ala "create-react-app" for the stack I generally use.

Part of that is to create standardized "docs/{architecture, decisions, contracts, operations}" folders that my harness recognizes in my repos to have a better sense of where was it.

Glad others are converging towards similar ideas!

Yes, that's my point :)

It's not just a stored prompt, you can attach re-useable scripts to them to offer more determinism. ex: a script that validates that a PR follows exactly the template you want, with a max of N lines per entry.

The more determinism you have, the more consistent you can be and the more leverage you can build. (yes I understand that skill calls are non deterministic).

That's your experience and it's valid. For me documentation AND comments have been useful on occasion.

The core thing that I agree with is that comments (or docs) can get stale and not follow what is actually being executed. The way I work with it is by being structured, consistent and follow standards. Unfortunately for me, not all developers follow the same guidelines.

Code can "lie" too.

```auto a = 65535 + 1``` will give you a different answer depending on the architecture. You can then decide.. oh don't use auto or don't use c++ or whatever and have standards... like the standard you set for yourself "disallow comments from my LLM".

A comment is just a summary of the code in an abstraction that's easier to follow. Let's say you have a simple function which would produce an almost as large comment, yes obviously useless. If the function is large enough, yeah summarizing it as a comment is a good idea.

Now you might say, don't write huge functions. Sure I agree, but most codebase or teams are not super disciplined enough. So comments are a compromise.

Just to be clear, that salary is prevailing wage which is usually lower than the actual salary you're getting (does not include RSUs or stock on top of that). In my case the difference was about 30 to 40% lower.

>To be able to even consider to move there I would need a salary bump of 3x-5x. No way this will ever happen.

You'd be surprised. Granted it was over a period of 4 years, but I did hit that 5x.

You mean this C++ code?

  std::vector<std::pair<std::string, int>> s;
  s.push_back({"a", 1});
  s.push_back({"b", 2});
  s.push_back({"c", 3});

I mean let's compare apples to apples here.

I'm unsure as how you would identify people across apps using cookies but.. okay.

Considering that Mobile is about 50% of web traffic and that cookies are not very useful on mobile as well as ITP, I would say fingerprinting has been a very practical in building user profiles.

Yes RVO is one case where the compiler will do it automatically.

I think copy initialization of an object will have the same will apply copy elision as well to result in the same performance, but I'm not entirely sure.