JPDev

joined 1 year ago
[–] JPDev@programming.dev 11 points 3 months ago* (last edited 3 months ago)

just edited to upscale the image

524
Evolution of C (programming.dev)
submitted 3 months ago* (last edited 3 months ago) by JPDev@programming.dev to c/programmer_humor@programming.dev
 
162
Do you know who can help? (programming.dev)
submitted 3 months ago* (last edited 3 months ago) by JPDev@programming.dev to c/programmer_humor@programming.dev
 
 
 
 
 
 
[–] JPDev@programming.dev 25 points 3 months ago* (last edited 3 months ago) (2 children)

git rm -rf is only usable within the scope of the git repository and removes files in the staging area and working directory but doesnt affect untracked files or .git. rm -rf affects everything. For this case rm -rf probably would be the better option

edit: did a quick edit on the meme to change it to rm -rf since it makes more sense

262
rm -rf / (programming.dev)
submitted 3 months ago* (last edited 3 months ago) by JPDev@programming.dev to c/programmer_humor@programming.dev
 
 
 
187
submitted 3 months ago* (last edited 3 months ago) by JPDev@programming.dev to c/programmer_humor@programming.dev
 
[–] JPDev@programming.dev 20 points 4 months ago* (last edited 4 months ago)

Explanation:

That is a the regex string for that sites password field. Regex is a sequence of characters used to see if an input matches a defined pattern to validate the input in code (theres also other uses but thats what being done here). Sites normally dont show the regex pattern since it is pain to parse even if you know how to write things in regex and to people who dont code this looks like a random output. Im assuming a bug exists that prints out the wrong error string so that this shows instead of the human readable one

[–] JPDev@programming.dev 4 points 9 months ago* (last edited 9 months ago) (2 children)

Im just reposting this from another platform but ill check out the community. Been wanting to start playing satisfactory

[–] JPDev@programming.dev 18 points 10 months ago
view more: next ›