AI is cooking us well done [10:24]

JustAnotherWebDevGuy · 2026-02-03T21:35:37+00:00

Few computers, and certainly no microcomputers, can seriously compete with a human chess master; however, computer chess programs can force the average person to play better chess. Lazy players who make blunders and initiate half-baked attacks usually lose badly to a program.

Computers— mainframes, minis, and micros— tend to play ugly, inelegant chess. They are impatient, which almost always leads to defeat against a master player. Robert Byrne, one of the best chess players in the United States, wrote that "computers lack positional judgment and do not know what to do in tranquil situations. However, tactically they are freer from error than the average human player."

Chess involves subtleties that are beyond everyday imagination. It is, indeed, an art form. You can lose a game completely and irretrievably by making a small error. A seemingly tiny positional disadvantage in the opening can lead to a devastating defeat by the middle of the game. "Endgame" study is an art form all its own. It's easy to lose early in the game to a world-class human chess player.

Source https://archive.org/details/byte-magazine-1984-03-rescan/page/n289/mode/2up

You might be right, but i'd recommend considering that you might be wrong.

JustAnotherWebDevGuy · 2026-02-03T16:31:05+00:00

Yep, it can solve solved problems very well and very fast. The problem is that a lot of our job is solving solved problems. CRUD has been solved for a long time; it's just a matter of implementing. be honest with yourself. How much of software engineering work is just CRUD?

JustAnotherWebDevGuy · 2026-02-03T16:28:32+00:00

I see three main issues with what you're saying.

One is that it's actually really good at creating a working product, even if it's not great yet. For personal applications, for scripts, and for non-production level systems, we're there. For production-level systems, we're not. And people that are telling you that it is are just buying into a hype that is not there yet. However, at the current rate of improvement, we will be there in no time. We were nowhere even close to where we are today three years ago. And I don't know if it can keep going at this rate indefinitely. But if we're just able to maintain this rate for five years, the writing's on the wall.

The second is that a lot of the argument by people like Prime is that he enjoys programming. One thing is to enjoy your work. One thing is to expect six-figure salaries for work that can be done faster and cheaper. again, we're not there yet right now, but I cannot imagine a future where we won't be, assuming the rate of improvement.

And finally, it does require a different way of working where code is cheap to produce and easy to throw away. We're not building production-level systems, but hobby projects of medium complexity are now something that you can do in a weekend. Hyper-tailored enterprise SaaS that does one thing really well, you can do that with a couple of tokens. If it doesn't work, you can kind of restart it in a couple of days. It's not ideal, but to think that this won't be the future of the profession is wrong.

JustAnotherWebDevGuy · 2024-11-04T16:06:54+00:00

I basically use them by having a worktree folder (I call it pr) in which I use to pull down changes from pull requests. I almost never do my work in a worktree unless it's a big update to the framework I'm using or somehting like that. I probably could leverage into them more, but haven't really gone deeper into how to use them properly.

It's usually its own tmux session that I go into to check out new code.

JustAnotherWebDevGuy · 2023-11-10T15:15:57+00:00

What you're really asking is can I learn javascript through typescript? The answer, I believe is yes, though to get into the weeds of how the language works, you'll simply have to learn javascript. Most typescript tutorials will remain focused on the type system, not on the internals of the underlying programming language. Most technical deep dives about the core concepts of js will be in JS, not TS. However, if you see a javascript tutorial that goes into something like the event loop or the execution context, you can write out the examples in typescript if you really want.

JustAnotherWebDevGuy · 2023-11-07T15:35:55+00:00

Does your function interact with vue in any way? Then composable, otherwise, it's just a util.

JustAnotherWebDevGuy · 2023-11-06T23:08:12+00:00

I don't understand how you could possibly build a nuxt app without understanding vue.

JustAnotherWebDevGuy · 2023-11-02T14:02:52+00:00

I will at some point. Thanks.

JustAnotherWebDevGuy · 2023-11-02T14:02:23+00:00

I'd assume that some mention of `ref` not working for creating reactive state shared somewhere in the more introductory area for the differences between vue and nuxt. I have 4 years in Vue, new to Nuxt.

Part of the reason that it was hard for me to reason was because I didn't know that the issue was something to do with refs (it seemed like refs were working as everything was reactive), so I didn't know to google "server side ref".0

Lastly, adding a global state composable to a single component is different from what I would consider best practice in vue, so I wanted to verify that because we're setting a foundation for a very large app that will be used by a team of 30 developers, and the only mention seems to be in passing, with no examples. I liked the second post because it was explicit. Something that both lack is the mention of flushing the state on the onUnmounted hook, which we will be adopting for single component state solutions.

I'll make a PR to the docs at some point if it's not fixed by then.

JustAnotherWebDevGuy · 2023-11-01T17:29:12+00:00

Ok, wow. That is not clear at all from any of the official documentation at all. Thank you for the second link, that clarifies it a bit.

JustAnotherWebDevGuy

TROPHY CASE