In my experience, you can’t expect it to deliver great working code, but it can always point you in the right direction.
There were some situations in which I just had no idea on how to do something, and it pointed me to the right library. The code itself was flawed, but with this information, I could use the library documentation and get it to work.
ChatGPT has been spot on for my DDLs. I was working on a personal project and was feeling really lazy about setting up a postgres schema. I said I wanted a postgres DDL and just described the application in detail and it responded with pretty much what I would have done (maybe better) with perfect relationships between tables and solid naming conventions with very little work for me to do on it. I love it for more boilerplate stuff or sorta like you said just getting me going. Super complicated code usually doesn’t work perfectly but I always use it for my DDLs now and similar now.
The real problem is when people don’t realize something is wrong and then get frustrated by the bugs. Though I guess that’s a great learning opportunity on its own.
Gen AI is best used with languages that you don't use that much. I might need a python script once a year or once every 6 months. Yeah I learned it ages ago, but don't have much need to keep up on it. Still remember all the concepts so I can take the time to describe to the AI what I need step by step and verify each iteration. This way if it does make a mistake at some point that it can't get itself out of, you've at least got a script complete to that point.
Exactly. I can’t remember syntax for all the languages that I have used over the last 40 years, but AI can get me started with a pretty good start and it takes hours off of the review of code books.
I actually disagree. I feel it’s best to use for languages you’re good with, because it tends to introduce very subtle bugs which can be very difficult to debug, and code which looks accurate about isn’t. If you’re not totally familiar with the language, it can be even harder
I test all scripts as I generate them. I also generate them function by function and test. If I'm not getting the expected output it's easy to catch that. I'm not doing super complicated stuff, but for the few I've had to do, it's worked very well. Just because I don't remember perfect syntax because I use it a couple of times a year doesn't mean I won't catch bugs.
Nah. It doesn’t say not to plan. It says to prefer responding to change over planning. Which means both happen but responding to change is more crucial. Or put another way don’t let your plan get in the way of responding to change.
I’m sure you were being sarcastic, but I get kind of tired of the Agile strawman and people shitting on it. It’s not a complex philosophy yet people extrapolate so much (too much) and then get annoyed when their assumptions don’t pan out well. even performing sprints is an extrapolation, so this meme gets it wrong too.
For the benefit of any of Today’s 10,000 I just want to point out that this is a reference to a quote from a movie.
The same movie stars Danny Trejo as Machete.
This movie is Spy Kids 2.
How? You’d need to compile it down to machine code somehow, for the processor to have any clue how to run it. And you’d need some custom library with custom compile instructions, to be able to control memory allocations, memory addresses etc…
I did a quick search and found two operating systems written in JS, both of which cop out when it comes to the kernel. Did you maybe mix it up with those?
I mean, I’m a bit out of my water there, both in terms of the featureset of PHP and what’s actually needed for a kernel, but I’m still gonna go with no.
For one, PHP uses reference counting + garbage collection for memory management. That’s normally done by the language runtime, which you won’t have when running baremetal.
Maybe you could implement a kernel, which does as few allocations as possible (generally a good idea for a kernel, but no idea, if it’s possible with PHP), and then basically just let it memory leak until everything crashes.
Then again, the kernel is responsible for making processes crash when they have a memory leak. Presumably, our PHP kernel would just start overwriting data from running processes and eventually overwrite itself in memory(?). Either way, it would be horrendous.
Maybe you could also try to implement some basic reference counting into your own PHP code, so that your own code keeps track of how often you’ve used an object in your own code. Certainly doesn’t sound like fun, though.
Well, and secondly, I imagine, you’d also still need an extension of the language, to be able to address actual memory locations and do various operations with them.
I know from Rust, that they’ve got specific functions in the stdlib for that, see for example: doc.rust-lang.org/stable/std/ptr/index.html#funct…
Presumably, PHP does not have such functions, because its users aren’t normally concerned with that.
Right – I’m not saying you could build a compiler then just go to town. You would still have to build all the tools, using PHP, to interact with hardware, the way other languages do. A horrible idea, lol, but interesting, sort of. Since at its core as long as you can execute logic and read/write to memory, you could do it, I think
But that is what I mean with it needing an extension of the language.
So, I’m not saying you could just build a library that calls existing PHP functions to make it all work. Rather I’m saying there’s certain machine code instructions, which just cannot be expressed in PHP. And we need those machine code instructions for actually managing memory. So, I am talking about reading/writing to memory not being possible, unless we resort to horrible hacks.
Since we are building our own compiler anyways, we could add our own function-stubs and tell our compiler to translate them to those missing machine code instructions. But then that is a superset of PHP. It wouldn’t be possible in PHP itself.
Again, I’m not entirely sure about the above, but my web search skills couldn’t uncover any way to actually just read from a memory address in PHP.
AI coding in a nutshell. It makes the easy stuff easier and the hard stuff harder by leading you down thirty incorrect paths before you toss it and figure it out yourself.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.