Prompt Engineer's

[Κracus]

I'm seriously thinking about doing a pivot in my career and focusing solely on AI and machine learning. I have an LLM setup at home that I play with, you can download it too at https://sourceforge.net/projects/alpaca-cpp.mirror/ and it's really interesting to see what you can do with this. Beyond that, I'm seeing postings like this one https://jobs.lever.co/Anthropic/e3cde48 ... cab67bd1ed

I'm getting bored of system administration but on the plus side I have broad enough knowledge in various fields that without being an expert on a specific subject I'm still capable of producing expert level results in a variety of different fields. Anyone else looking at the AI field for future careers?

[Ganemi]

gggggg

[Ganemi]

Get into arduinos and 3D printing:

https://www.youtube.com/watch?v=w3q_4_-ZHJ4

When I have time I want to make one of these to play with cats all day.

[Transient]

Prompt engineer's what?

[MKJ]

Prompt engineer's what?

4 days until the intrusive thoughts took over :olo:

[Transient]

I just need to know!

[Κracus]

Check the links in my post Transient.

I was actually playing around with some AI and generated a short clip that's nothing short of amazing. I think I'm gonna do an entire music video using this tech in the near future.

[Transient]

Yes, but prompt engineer is what? :offended:

[Eraser]

It's nothing more than someone typing in commands for some AI to interpret.
Considering the state of ChatGPT and the various image creation AI's I think calling it a "prompt engineer" is hugely overselling it.

[Κracus]

I completely agree yet that's the job title. There is however some nuance to the ability to generate code, instructions or content using prompts though.

Like it's easy to think, hey I can make a powershell script using AI but if you don't know powershell you're going to have a tough time. You sort of need the technical knowledge yourself to get AI to do what you need it to. Otherwise you might wind up with an unsuable piece of code because of a few missing bits of instruction.

[Transient]

I give up. :miffed:

[seremtan]

I'm basically retarded

well thank zeus for that

[Κracus]

I give up. :miffed:

It's all in the link with the job posting. You're asking what's a prompt engineer and the job details are in that link. It's basically someone who has enough expertise in a particular subject to be able to tell an AI to create something specific. The AI does the work but you need to know how to ask it to do it.

For example, say you wanted to create a chat app using javascript.

You could tell chatGPT "Write me a chat app using javascript" and it's going to proceed to spit out a lot of code but in the end, unless you're somewhat familiar with javascript you're going to be missing some things.

A prompt engineer is going to be able to see that certain things are missing. My prompt, for example would be more something akin to "Write me a chat app in javascript that requires a client app to receive messages, ensure each client app has a unique userid. Also create a server app to process the requests and a graphical user interface in C# for both apps that has an open field for typing in messages, a send button and a cancel button that do their respective functions"

I'd then load up something like openAI to create the graphical buttons and UI to be used by the C# app and tie everything together.


They're both the same thing but one requires a little bit of knowledge about how it all works. The thing is that this is one scenario, you could have a similar prompt engineer write music instead of applications and they could be more specialized in their musical knowledge.

[Transient]

No, I was poking fun at you for using the possessive form of the word Engineer instead of the plural form when you typed in the title for this thread.

Engineers = plural
Engineer's = possessive

Protip: Take out the apostrophe and s and replace it with the word "is". Does your sentence still make sense?

[Eraser]

Engineeriss

No that doesn't make any sense at all.

[Transient]

Pedant game recognizes game.

[MKJ]

lol

[Captain]

fucking nerdseses

[seremtan]

fucking Bagginses

[Κracus]

No, I was poking fun at you for using the possessive form of the word Engineer instead of the plural form when you typed in the title for this thread.

Engineers = plural
Engineer's = possessive

Protip: Take out the apostrophe and s and replace it with the word "is". Does your sentence still make sense?

You know, as someone who's primary language isn't english I've always struggled with that one. Maybe I'll get it some day.

[Pext]

I think calling it a "prompt engineer" is hugely overselling it.

I'm not sure on this one yet.

I think it's easy to brush off these LLMs when you think about them in terms of "write one prompt to get a task done".

But take this perspective:

If you could compose a network/pipeline of 1000 interconnected prompts to get a 'program' that automates web development, would it be worth it? (Yes of course).

And so the real task is not: "Write me a prompt to do X" but rather to understand how complex tasks can be achieved by using AI tools in multiple steps. And this would involve proper engineering. For example LLMs are very good when used in combination with DSLs (domain specific languages). And knowing how to find the right DSL for the respective business contexts is a skill requirement that is something genuinely new.

Here's an example (4:57 or something):

[youtube]iO1mwxPNP5A[/youtube]

[Κracus]

This is precisely the problem people who don't know don't realize.

This morning I had it make me a powershell script so I can extract where a certain user has permissions in our share drive. It came up with this.

import os
import csv
from googleapiclient.discovery import build
from google.oauth2 import service_account

# Set the necessary credentials
credentials = service_account.Credentials.from_service_account_file('path/to/credentials.json')
SCOPES = ['https://www.googleapis.com/auth/drive']

# Enter the email address of the user you want to check
user_email = 'user@example.com'

# Enter the shared drive ID
shared_drive_id = 'your_shared_drive_id'

# Connect to the Google Drive API
service = build('drive', 'v3', credentials=credentials)

# Get the list of permissions for the user in the shared drive
results = service.permissions().list(
fileId=shared_drive_id,
supportsAllDrives=True,
fields="permissions(id, role, emailAddress)").execute()

# Create a list to store the locations the user has access to
locations = []

# Iterate through the permissions and filter for the user's email address
for permission in results.get('permissions', []):
if permission.get('emailAddress') == user_email:
locations.append(permission.get('id'))

# Export the locations to a text file
output_file = 'user_locations.txt'
with open(output_file, 'w') as file:
file.write('\

If you don't know, that's not the entire code, I cut it off mid project because I could already tell this isn't what I wanted. It was inserting google api's into the code for some unknown reason and doing it python. I wasn't asking it to do this. so I asked it to remove it and it gave me this. Also, I specified in powershell as i'd forgotten to do so in my first prompt.



# Set the necessary variables
$UserEmail = "user@example.com"
$SharedDriveId = "your_shared_drive_id"
$OutputFile = "user_locations.txt"

# Authenticate with Google Drive API
$CredPath = "path/to/credentials.json"
$Scopes = "https://www.googleapis.com/auth/drive"
$Credential = Get-GoogleOAuthCredential -Path $CredPath -Scope $Scopes
Connect-GoogleDrive -Credential $Credential

# Get the list of permissions for the user in the shared drive
$Permissions = Get-GoogleDrivePermission -Id $SharedDriveId

# Create a list to store the locations the user has access to
$Locations = @()

# Iterate through the permissions and filter for the user's email address
foreach ($Permission in $Permissions) {
if ($Permission.EmailAddress -eq $UserEmail) {
$Locations += $Permission.Id
}
}

# Export the locations to a text file
$Locations | Out-File -FilePath $OutputFile

Write-Host "User locations exported to $OutputFile"


Which again, is not what I wanted as it's importing, still different google API's I'm not interested in for a local share drive.

Eventually I got it to generate something that looked correct but there were syntax errors in the script which I had it correct and finally it came out with this.

$DriveLetter = "C:" # Specify the drive letter you want to check
$User = "DOMAIN\username" # Replace with the user you want to map permissions for
$OutputFilePath = "C:\Path\To\Output\File.txt" # Specify the desired output file path

# Recursive function to get permissions for the specified user
function Get-UserPermissions {
param(
[string]$Path
)

# Get the ACL for the current path
$DriveACL = Get-Acl -Path $Path

# Filter the ACL entries for the specified user
$UserPermissions = $DriveACL.Access | Where-Object { $_.IdentityReference.Value -eq $User }

# Output the permissions for the current path
$UserPermissions | Select-Object @{Name="Path";Expression={$Path}}, IdentityReference, FileSystemRights, AccessControlType

# Recursively process subfolders
$Subfolders = Get-ChildItem -Directory -Path $Path
foreach ($Subfolder in $Subfolders) {
Get-UserPermissions -Path $Subfolder.FullName
}
}

# Invoke the function to retrieve permissions for the specified user
Get-UserPermissions -Path $DriveLetter | Out-File -FilePath "${OutputFilePath}"

Write-Host "Permissions information exported to $OutputFilePath"

Which is currently running on my device through millions of files to extract exactly what I want, I think... I'll see when I get the result but I'm pretty confident it's going to give me what I want.

All that to say that unless you know what you need, it'll give you garbage.

[Transient]

Code: Select all

[size=150]import os
import csv
from googleapiclient.discovery import build
from google.oauth2 import service_account

# Set the necessary credentials
credentials = service_account.Credentials.from_service_account_file('path/to/credentials.json')
SCOPES = ['https://www.googleapis.com/auth/drive']

# Enter the email address of the user you want to check
user_email = 'user@example.com'

# Enter the shared drive ID
shared_drive_id = 'your_shared_drive_id'

# Connect to the Google Drive API
service = build('drive', 'v3', credentials=credentials)

# Get the list of permissions for the user in the shared drive
results = service.permissions().list(
    fileId=shared_drive_id,
    supportsAllDrives=True,
    fields="permissions(id, role, emailAddress)").execute()

# Create a list to store the locations the user has access to
locations = []

# Iterate through the permissions and filter for the user's email address
for permission in results.get('permissions', []):
    if permission.get('emailAddress') == user_email:
        locations.append(permission.get('id'))

# Export the locations to a text file
output_file = 'user_locations.txt'
with open(output_file, 'w') as file:
    file.write('\[/size]

Code: Select all

[size=150]# Set the necessary variables
$UserEmail = "user@example.com"
$SharedDriveId = "your_shared_drive_id"
$OutputFile = "user_locations.txt"

# Authenticate with Google Drive API
$CredPath = "path/to/credentials.json"
$Scopes = "https://www.googleapis.com/auth/drive"
$Credential = Get-GoogleOAuthCredential -Path $CredPath -Scope $Scopes
Connect-GoogleDrive -Credential $Credential

# Get the list of permissions for the user in the shared drive
$Permissions = Get-GoogleDrivePermission -Id $SharedDriveId

# Create a list to store the locations the user has access to
$Locations = @()

# Iterate through the permissions and filter for the user's email address
foreach ($Permission in $Permissions) {
    if ($Permission.EmailAddress -eq $UserEmail) {
        $Locations += $Permission.Id
    }
}

# Export the locations to a text file
$Locations | Out-File -FilePath $OutputFile

Write-Host "User locations exported to $OutputFile"
[/size]

Which again, is not what I wanted as it's importing, still different google API's I'm not interested in for a local share drive.

Eventually I got it to generate something that looked correct but there were syntax errors in the script which I had it correct and finally it came out with this.

[size=150]$DriveLetter = "C:"  # Specify the drive letter you want to check
$User = "DOMAIN\username"  # Replace with the user you want to map permissions for
$OutputFilePath = "C:\Path\To\Output\File.txt"  # Specify the desired output file path

# Recursive function to get permissions for the specified user
function Get-UserPermissions {
    param(
        [string]$Path
    )

    # Get the ACL for the current path
    $DriveACL = Get-Acl -Path $Path

    # Filter the ACL entries for the specified user
    $UserPermissions = $DriveACL.Access | Where-Object { $_.IdentityReference.Value -eq $User }

    # Output the permissions for the current path
    $UserPermissions | Select-Object @{Name="Path";Expression={$Path}}, IdentityReference, FileSystemRights, AccessControlType

    # Recursively process subfolders
    $Subfolders = Get-ChildItem -Directory -Path $Path
    foreach ($Subfolder in $Subfolders) {
        Get-UserPermissions -Path $Subfolder.FullName
    }
}

# Invoke the function to retrieve permissions for the specified user
Get-UserPermissions -Path $DriveLetter | Out-File -FilePath "${OutputFilePath}"

Write-Host "Permissions information exported to $OutputFilePath"[/size]

You can use

Code: Select all

 tags here. ;)

[Κracus]

Well shit. Q3W really was ahead of its time!

Edit: Got the results of the script this morning and it's pretty much exactly what I wanted. I shoulda outputted to a delimited csv though...