As someone who spends time programming, I of course find myself in conversations with people who aren’t as familiar with it. It doesn’t happen all the time, but these discussions can lead to people coming up with some pretty wild misconceptions about what programming is and what programmers do.
- I’m sure many of you have had similar experiences. So, I thought it would be interesting to ask.
Can’t fault someone for trying to convert digital information into something tangible to visualize it better. Unfortunately peoples brains aren’t really built to comprehend a newspaper that weighs almost as much as the moon. (rough estimate I pulled out my ass)
If this were my grandma, then sure, I wouldn’t fault her. But if it’s someone making life-altering decisions based on their understanding of it, someone who has been doing so for a very long time, and who has support staff who ostensibly try to make sure that person understands the topic at hand, and yet after all these years of hearing about tech-related topics and deciding on them, the person — who has every ability to retire if the world is moving too fast for them to keep up, but has opted not to — asks a question as absurd as this… I actually am going to fault that person.
That I’m in any way smart or good at math
That just because I’m a programmer that must mean I’m a master of anything technology related and can totally help out with their niche problems.
“Hey computer guy, how do I search for new channels on my receiver?”
“Hey computer guy, my excel spreadsheet is acting weird”
My friend was a programmer and served in the army, people ordered him to go fix a sattelite. He said he has no idea how but they made him try anyways. It didn’t work and everyone was disappointed.
Don’t pretend you suck at these things. You know very well you are fucking equipped to fix this kind of thing when you work with programming. Unless you’re, like a web developer or something ofc
You are part of the problem
Nope
Why should I fix any of those peasant problems if I can order the lowly technician to fix my computer which I use to make crappy SQL queries? 🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐
Because you are a nice person to your relatives???
I used to get a lot of people asking for help with their printer. No, just because I am a software developer doesn’t mean I know how why your printer isn’t working. But, yes, I can probably help you…
Ironically, most of those things are true, but only with effort. We are better than most people at solving technical problems, or even problems in general, because being a programmer requires the person to be good at research, reading documentation, creative problem solving, and following instructions. Apparently those aren’t traits that are common among average people, which is baffling to me.
Sometimes I’ll solve a computer problem for someone in an area that I know nothing about by just googling it. After telling them that all I had to do was google the problem and follow the instructions they’ll respond by saying that they wouldn’t know what to google.
Just being experienced at searching the web and having the basic vocabulary to express your problems can get you far in many situations, and a fair bit of people don’t have that.
And everyone expects you to know how to make phone apps.
Like, I think I know what to google in order to start learning how.
If you know Java or Javascript you can easily build apps.
But like in every other software field, design is often more important.
He said he has no idea how but they made him try anyways.
Uh, I’ve been present when such a thing happened. Not in the military, though. Guy should install driver on a telephone system, despite not being a software guy (he was the guy running the wires). Result: About as bad as expected. The company then sent two specialists on Saturday/Sunday to re-install everything.
My neighbour asked me to take a look at her refrigerator because it wasn’t working. I am a software developer.
-
I’m a programmer, so I must know how to get X done in Y software.
-
I don’t use <social media app> or <messaging system> so I’m some kind of Luddite and can’t possibly know anything useful about computers.
One thing that fascinates me about #1 is that the absolute raw dependency people have on Google doesn’t seem to ever lead to searching for a tutorial.
I live in the second one. On purpose. I’ll never wear my debian tshirt.
Me too.
I found that my 2600 t-shirt keeps them at bay. First, they ask what 2600 is, then they make sure that nobody allows me near their computers.
I’ve lost all faith in tutorials as sources of relevant knowledge. If I’m searching about a specific problem, any from-the-top how-to might as well be Ben Stein reading it aloud at 50% speed, and then a year of my life later, it skips right over the place where something fucked up.
-
Programming and Software Engineering are related, but distinct fields. Programming is relatively easy, Software Engineering is a bit harder and requires more discipline in my opinion.
that programmers make $300-500k/year
I think that non-tech people think that tech just goes. Like you pull it out of a box and turn it on and it just works. They have no idea how much jenk is in everything and how much jenk was eradicated before a user came went anywhere near.
What do you mean by jenk? Is that a specific term used to refer to tech junk?
Jank?
They mean jank:
jan·ky adjective, informal adjective: jank
of extremely poor or unreliable quality. "the software is pretty janky"
I’m not in IT but used to work with a very old terminal based data storage and retrieval system.
If the original programmers had implemented a particular feature, it was very easy to enter a command and have it spit out the relevant info.
But as times changed, the product outgrew its original boundaries, and on a regular basis clients would ask for specific info that would require printing out decades worth of data before searching and editing it to get what the client wanted.
I can not tell you how many times I heard the phrase, “Can’t you just push a button or something and get the information now??”
The thing that infuriated me the most was the idea that somehow we could do that, but didn’t want to, as if there was some secret button under the desk that we could push for our favourite clients. Ugh.
I had some dude here trying to tell me, a mathematician and data scientist who is developing AIs for fun and is a holder of an MA in Visual Effects specializing in procedural design, who has worked on algorithmic video game development, what AIs are or are going to be capable of in procedural/generative/algorithmic game design “because he has played a lot of games” and argued for days with me, cherry-picking everything I wrote attempting to use my words refuting him to support his arguments.
Just… Infuriating.
That it’s mostly sitting behind a computer writing code. More than half my time is spent in the exploration phase: math, research, communication and developing a concept. The actual writing of code is typically less than 1/3.
Also as someone mentioned before, that it’s considered something ‘dry’. I honestly wouldn’t be able to code properly without my intuition. Take for example code smell. I don’t know why the code is bad, I just feel that it’s off somehow, and I keep chipping away until it feels just right.
I really like the word you used, code smell. I often have a hard time expressing to co-workers in code reviews why something feels off, it just does.
People think I can hack anything ever created, from some niche 90s CD software to online services
A friend asked me to atempt data recovery on some photos which ‘vanished’ off an USB stick.
Plugged it in, checked for potential hidden trash folders, then called it a day. Firstly I havenever done data forensic and secondly: No backup? No mercy.
There are tools for that fyi
Well, here’s the important part:
I have never done data forensic
So yeah, I didn’t know that at the time. Anyway: Which tools are you talking about in particular?
Someone else already named some tools, so I won’t repeat. But the reason this works is that even once you clear out those trash files, the OS usually only removes the pointer to where the data lives on the disk, and the disk space itself isn’t overwritten until it’s needed to save another file. This is why these tools have a much higher chance of success sooner after file deletion.
Windows File Recovery, WinfrGUI, Easeus, Aomei, DiskGenius, etc.
The most I read and hear is “you’re a hacker”. And I get labeled as the computer nerd alot in school.
Based on some places I used to work, upper management seemed convinced that the “idea” stage was the hardest and most important part of any project, and that the easy part is planning, gathering requirements, building, testing, changing, and maintaining custom business applications for needlessly complex and ever changing requirements.
- You’re a hacker (only if you count the shit I program as hacks, being hack jobs)
- You can fix printers
- You’re some sort of super sherlock for guessing the reason behind problems (they’ll tell you “my computer is giving me an error”, fail to provide further details and fume at your inability to guess what’s wrong when they fail to replicate)
- If it’s on the screen, it’s production ready
If it’s on the screen, it’s production ready
“I gave you a PNG, why can’t you just make it work?”
I actually get that somewhat often, but for 3D printing. People think a photo of a 3D model is “the model”
Dude, I would just 2d print the png they sent and give them the piece of paper.
If they complained, I would say: “I literally printed the thing you told me to print.”
I’ve had questions like your 3rd bullet point in relation to why somebody’s friend is having trouble with connecting a headset to a TV.
No idea. I don’t know what kind of headset or what kind of TV. They are all different Grandma.
I once had a friend who told me, that he finds it interesting that I think and write in 1s and 0s.
Confuse him with “I used to do that but I’m nonbinary now”
Every Hollywood programmer
That might be true of VHDL / Verilog programmers I guess.
I found it useful when explaining programming to lay people to try to put various programming paradigms in everyday terms.
Imperative programming is like a cooking recipe. You need specific ingredients in certain amounts and you need to perform actions in a very specific order, or the recipe won’t turn out right.
OOP is like a bicycle. Lots of pieces interconnected and working together, hopefully interchangeable and standardized. It can also be used to explain unit testing to juniors. Clock mechanisms or engines can also work but people tend to relate better to bicycles.
Declarative programming (SQL) works like ordering at the restaurant. You still need to know how restaurants work and about meal courses and how to read the menu etc. but you don’t need to know how the sausage was made, only if it’s good or not.
SELECT food FROM menu WHERE name LIKE ‘Fried %’;
Lemme
cat menu | grep Friedreal quickgrep -i fried < menu
grep -i fried menuOf course! It’s amazing how this stuff just flows from the keyboard when you’re typing in a shell window, but feels awkward when typing in a Lemmy comment.
You don’t want to order from the cat menu.
