warmwaffles

> Don't ask LLMs for big changes

> Review everything and point them in the right direction

Sorry upper management doesn't care. That's an engineering problem that you need to solve.

And even if it _was_ related to AI, they would not admit it. First course of action is to blame user/programmer error and then QA process error. You shall not blame the golden calf. I am half serious and half not. But I do recommend reading the book "The Field Guide to Understanding 'Human Error'" in conjunction with my hyperbole.

Schools have always lagged and can barely keep up. Books once printed on any tech topic is almost always outdated by the time it reaches students. Anecdotally, I went through high school being told over and over that I wouldn't always have a calculator in my pocket. I think the messaging they conveyed was done poorly, and should have said "you need to understand the fundamentals and why the calculator gave you the answer".

> Moore's Law approaching its end.

No it isn't. We are going more parallel and the transistor counts will continue to rise.

Perfect, now we'll start seeing people automate auto publishing because they don't want to explicitly push a button to publish it.

Well if you also have your 2024 input docs as well, you may want to check that too in separate sessions. Post your findings. I'm interested.

The sweet spot for being just fast enough to not irritate you is 10tok/s. Still slow but faster than you can sustain at typing and thinking. Just interesting to observe.

> quickly text a colleague.

This is still common and useful to gut check and make sure you aren't missing something. Source: wife is a doctor.

Because he wants to move it and then has to provide rationale behind why Ghostty is moving away from Github.

I am curious to watch this unfold. How long until a clever supply chain attack effects this? What will the response be? Will be interesting to see it.

> Couldn't you also just have an LLM review the PR and quickly fix any issues? Or even have it convert the PR into a list of specs, and then reimplement from there as you see fit?

Sometimes I'm not a fan of the change in its entirety and want to do something different but along the same lines. It would be faster for me to point the agent at the PR and tell it "Implement these changes but with these alterations..." and iterate with it myself. I find the back and forth in pull requests to be overly tiresome.

Yea this is operating on the pointer to the values, but if you use just an `unsigned a` it uses xor

clang: https://godbolt.org/z/5PEMTrxba

gcc: https://godbolt.org/z/7j8h4zo4v

`-Wall` is your friend and boy it is a major irritant using third party sloppy libraries when statically compiling it all.

Yes, especially if you are using a WAL.

10-Ks are going to be written by LLMs increasingly soon. I wonder how this will impact LLMs reading them.

I've trained myself to avoid this entirely by avoiding changing lines unnecessarily. With LLMs, I also force them to stay concise and ONLY change what is absolutely necessary.

The crazier fact is that a hand full of cities alone in the US has a higher population than all of Norway.

Ever try to get Congress to agree on something without packaging in another thing?

The modding community was gigantic for 3 and was simply amazing being a part of it.

I actually preferred Civ 3 to 2 and 4. It scratched a certain itch.

Awesome. Good luck and I hope to see it.

I played A-10 Cuba a ton on an old Pentium 3. Are you doing this in a repo somewhere?

It's fast. I don't know if they are conflating the actual compiler being slow with xmake executing it.

I did not spot those in the docs. Thanks a ton. This will help my autoformatter not completely wreck my files.

I use it for personal projects and I find it substantially easier to mess around with compiling shaders to SPIRV, processing assets, etc... But some of my gripes are, although it _is_ lua, there is some magic fuckery going on. When you specify targets, things for that target need to be close to the definition, and it feels very odd in a lua language to not have `target("name", function (ctx) ... end)`.

Anyways, not going to die on that hill and I'll keep using it because it's simple and works well for my needs. One thing I do like is that I am not having to constantly keep a skeleton CMake project around to copy paste and setup.

People getting hung up on `_t` usage being reserved for posix need to lighten up. I doubt they'll clash with my definitions and if does happen in the future, I'll change the typedef name.

Put it in drive, neutral, park, or reverse. Same as an automatic.

If you were able to wave a magic wand today and remove piracy, Microsoft would not remove ads.

Absolutely love my dumb Sceptre TV. Colors aren't super fantastic, but for the casual observer, it is just fine and gets the job done.

One could only hope.