<div dir="ltr">Do you think AI is going to cause a skills gap where you can do jr level tasks with it, but moving from jr to sr is a giant leap because the smooth learning curve is distorted by how easy it is to do basic things?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Nov 4, 2024 at 3:06 PM Keith Smith via PLUG-discuss <<a href="mailto:plug-discuss@lists.phxlinux.org">plug-discuss@lists.phxlinux.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 2024-11-04 11:30, David Schwartz via PLUG-discuss wrote:<br>
> Not what anybody wants to hear but …<br>
> <br>
> AI is going to transform this thing we call “programming”.<br>
> <br>
<br>
It has already. I use it regularly. It helped me configure my LAMP <br>
server to use php-fpm. I've played with enough to know it can program <br>
faster than me and better than me.<br>
<br>
<br>
<br>
> The “programming” process is going to become more high-level and <br>
> abstract. The “coding" stuff will become hidden in the background and <br>
> nobody will care about the language being used.<br>
<br>
For now I think one needs senior experience to use AI for programming. <br>
Maybe 3 50 5 years it might be getting there. I think we are safe for <br>
possibly 10 more years.<br>
<br>
> <br>
> Descriptions of what’s wanted will be used instead of entering lines <br>
> and lines of code.<br>
> <br>
> I see a process that looks more like an interview, like what analysts <br>
> do now, where the user is describing what they want to see first at the <br>
> UI level, then drilling down to specific formulas and actions that <br>
> apply to each field, as well as what back-end sources and destinations <br>
> of data exist.<br>
<br>
I agree.<br>
<br>
> <br>
> For a while, that will be done by us “programmers”, but as it gets <br>
> better, it will be done with an increasing amount of input directly <br>
> from users or “analysts” who do that stuff now.<br>
> <br>
> This is going to shift the nature of work we do, but I doubt it’ll <br>
> change things significantly for several years because most people <br>
> cannot think through things in a stepwise logical manner.<br>
> <br>
> Also, most people can’t look at things from a “big picture <br>
> perspective”, which means they’re going to get really annoyed at the <br>
> interview process asking about stuff they think is irrelevant, <br>
> resulting in overly narrow applications that cannot be easily adapted <br>
> to deal with broader needs over time. (Yeah, so what’s new about that, <br>
> right?)<br>
> <br>
> I know that learning to code is being seen as some kind of necessary <br>
> skill today, but they’re a day late and a few dollars short. In a world <br>
> where people can’t balance their checkbooks or track their spending, <br>
> learning to code is never going to be more than a hobby. They’ll be <br>
> turning to ChatGPT.<br>
<br>
When I think about the AI programmer I still see testing analysis and <br>
design and training. I think most of this will eventually be taken over <br>
by machines.... And I am glad I am old. I figure I will retire in <br>
another 10 years.<br>
<br>
There is so much going on right now that the next 10 years should be <br>
very interesting.<br>
<br>
Keith<br>
<br>
> <br>
> We need a “CodeGPT” thingamabob that people can use to make apps.<br>
> <br>
> -David Schwartz<br>
> <br>
> <br>
> <br>
> <br>
>> On Nov 4, 2024, at 10:47 AM, Keith Smith via PLUG-discuss <br>
>> <<a href="mailto:plug-discuss@lists.phxlinux.org" target="_blank">plug-discuss@lists.phxlinux.org</a>> wrote:<br>
>> <br>
>> Hi Alexander,<br>
>> <br>
>> I'm a PHP developer and my audience on YouTube, I would guess, are <br>
>> people wanting to learn PHP.<br>
>> <br>
>> I use Linux to support my PHP programming.<br>
>> <br>
>> I'm wondering if there is some value in not automating so one has to <br>
>> do these tasks over and over. I'm thinking this can help the learning <br>
>> curve.<br>
>> <br>
>> I know I have learned a lot. I last did this stuff on CentOS 6.x <br>
>> maybe 5 or 6 years ago. Ubuntu is similar but different.<br>
>> <br>
>> Your Thoughts?<br>
>> <br>
>> Keith<br>
>> <br>
>> <br>
>> On 2024-10-22 15:34, Keith Smith via PLUG-discuss wrote:<br>
>>> What is the learning curve for that?<br>
>>> On 2024-10-22 15:09, Snyder, Alexander J wrote:<br>
>>>> I think a lot of this could be made a lot easier with Ansible and<br>
>>>> Jinja templates.<br>
>>>> --<br>
>>>> Thanks,<br>
>>>> Alexander<br>
>>>> Sent from my Google Pixel 7 Pro<br>
>>>> On Tue, Oct 22, 2024, 13:39 Keith Smith via PLUG-discuss<br>
>>>> <<a href="mailto:plug-discuss@lists.phxlinux.org" target="_blank">plug-discuss@lists.phxlinux.org</a>> wrote:<br>
>>>>> Thank You Everyone!!<br>
>>>>> Seems the problem was I needed to uncomment "PasswordAuthentication<br>
>>>>> yes". When creating a user with SSH ability.<br>
>>>>> Keith<br>
>>>>> On 2024-10-22 10:46, Rusty Carruth via PLUG-discuss wrote:<br>
>>>>>> ChatGPT gave a more complete answer than I do below (the question<br>
>>>>> was:<br>
>>>>>> This person is using vhost, and thinks he wants to chroot to the<br>
>>>>>> docroot of the vhost when the user logs in. What do you think of<br>
>>>>> that?)<br>
>>>>>> (I never thought I'd be pointing people to an AI for answers! ;-)<br>
>>>>>> On 10/22/24 10:42, Rusty Carruth via PLUG-discuss wrote:<br>
>>>>>>> One thing I don't understand, below.<br>
>>>>>>> On 10/22/24 10:25, Keith Smith via PLUG-discuss wrote:<br>
>>>>>>>> Hi,<br>
>>>>>>>> I appreciate all the feedback. There is more to the story.<br>
>>>>>>>> ....<br>
>>>>>>>> The 3 things I think I need to accomplish:<br>
>>>>>>>> 1) Add a user and configure it to use SSH.<br>
>>>>>>>> 2) Configure each vhost to use PHP-FPM.<br>
>>>>>>>> 3) Limit the User to the docroot of it's virtual host.<br>
>>>>>>>> (ChrootDirectory)<br>
>>>>>>> I don't understand # 3. Let me say what I think you said: you<br>
>>>>> have<br>
>>>>>>> (some number of) virtual machines. Or do you mean that thing<br>
>>>>> that<br>
>>>>>>> allows you to run more than one web address from the same IP<br>
>>>>> address?<br>
>>>>>>> In either case, why do you need to chroot to docroot? You do<br>
>>>>> realize<br>
>>>>>>> that docroot must then have EVERYTHING the user needs - all<br>
>>>>> programs,<br>
>>>>>>> all devices, everything. So you're going to need /dev, /bin,<br>
>>>>>>> /usr/bin, and so forth or the user will be dead in the water with<br>
>>>>> no<br>
>>>>>>> commands - shoot, not even bash will be there to try to type<br>
>>>>> commands!<br>
>>>>>>> If you're doing the chroot already, and its failing, then that's<br>
>>>>>>> probably because bash isn't there, nor is anything else you<br>
>>>>> need...<br>
>>>>>>>> I am using a clone of the LAMP server so I am going to remove it<br>
>>>>> and<br>
>>>>>>>> create another close and start by trying to create a use that<br>
>>>>> has SSH<br>
>>>>>>>> access and a home directory.<br>
>>>>>>> If you are using virtual machines, just clone it in the virtual<br>
>>>>>>> machine - but then, I'm thinking you don't mean virtual machine,<br>
>>>>> you<br>
>>>>>>> mean that other thing :-)<br>
>>>>>>>> Then I think I should work on limiting that user to the vhost<br>
>>>>> that is<br>
>>>>>>>> designated to work with.<br>
>>>>>>> So, if you mean not virtual machine but that other thing, then<br>
>>>>> you're<br>
>>>>>>> either going to have to copy all the stuff I talk about above in<br>
>>>>> to<br>
>>>>>>> the docroot tree (which I still think will cause more problems<br>
>>>>> than it<br>
>>>>>>> will fix), or mount the stuff above inside the docroot, or figure<br>
>>>>> out<br>
>>>>>>> how to change permissions and ownership so that the user can only<br>
>>>>>>> change the stuff in their docroot. Perhaps group ownership can<br>
>>>>> save<br>
>>>>>>> the day here, assuming you want ALL files in ALL web servers to<br>
>>>>> be<br>
>>>>>>> owned by whoever is running Apache, then create 2 or more groups,<br>
>>>>>>> change all group ownership to the NON-User group, then<br>
>>>>>>> change group ownership of all files in your docroot to the group<br>
>>>>> of<br>
>>>>>>> the user (obviously you're going to have to change the user to<br>
>>>>> have<br>
>>>>>>> that group too), then change permissions to something like 770<br>
>>>>> for all<br>
>>>>>>> directories everywhere (or 775, or whatever) and 660 for all<br>
>>>>> files.<br>
>>>>>>> Done, supposedly ;-)<br>
>>>>>>>> Then finish up by installing configuring the vhost to use<br>
>>>>> PHP-FPM.<br>
>>>>>>>> Any thought are much appreciated!!<br>
>>>>>>>> Keith<br>
>>>>>>> ---------------------------------------------------<br>
>>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
>>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br>
>>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
>>>>>> ---------------------------------------------------<br>
>>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
>>>>>> To subscribe, unsubscribe, or to change your mail settings:<br>
>>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
>>>>> ---------------------------------------------------<br>
>>>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
>>>>> To subscribe, unsubscribe, or to change your mail settings:<br>
>>>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
>>> ---------------------------------------------------<br>
>>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
>>> To subscribe, unsubscribe, or to change your mail settings:<br>
>>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
>> ---------------------------------------------------<br>
>> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
>> To subscribe, unsubscribe, or to change your mail settings:<br>
>> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
> <br>
> ---------------------------------------------------<br>
> PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
> To subscribe, unsubscribe, or to change your mail settings:<br>
> <a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
---------------------------------------------------<br>
PLUG-discuss mailing list: <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="https://lists.phxlinux.org/mailman/listinfo/plug-discuss" rel="noreferrer" target="_blank">https://lists.phxlinux.org/mailman/listinfo/plug-discuss</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">James McPhee<br><a href="mailto:jmcphe@gmail.com" target="_blank">jmcphe@gmail.com</a></div>