Asklemmy

43148 readers

2049 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
[email protected]: a community for finding communities

~Icon~ ~by~ ~@Double_[email protected]~

founded 5 years ago

MODERATORS

[email protected]

What bizarre misconceptions do people have about your field? (lemmy.ml)

submitted 1 month ago by [email protected] to c/[email protected]

97 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 10 points 1 month ago (1 children)

That you can quickly pick up coding with a few courses.

Can you learn it? Sure why not. Just keep in mind that you'll never stop learning, so it has to fit into your lifestyle.

Further, you'll have to be patient and be able to deal with stress well. If you can't adjust yourself to work in a team, you'll have difficulty finding work.

Another misconception is that coders stay alone at home in a dark room all the time. Coding is just one part of your life and people do all sorts of stuff.

[–] [email protected] 4 points 1 month ago

Yeah lots of people who aren't in tech think of coding as a solitary job, but it's a very social-skills-dependent job.

Social skills required to be a coder (at least; probably forgetting many):

Communicate complex concepts which have never been discussed before
Deliver things on time
Understand the tradeoffs of others' jobs well enough to make good decisions about when it's worth it NOT to deliver something on time (or be able to figure it out by communicating with whom you're delivering to)
Know the balance between asking for help and trying to figure it out yourself, including the short- and long-term tradeoffs of the two approaches
Know whether a problem you're encountering is your own lack of skill, your own lack of knowledge, your own lack of care, or someone else's any of those, and then communicate with others on the basis of being unsure of this
Deal with antisocial coworkers who can hide their shenanigans in the complexity of the code. I.e. if they're smart enough they can screw with your work, making you look bad, in a way that is extremely difficult to explain to non-technical management (and hence get support for)
Have the emotional stability and the hutzpah and the finesse to call things like this out when they do happen, and make those complicated explanations or deliver their abstract form
Understand and feel the pain of users when their systems break

As an autistic person, I struggled mightily with the social skill requirements of being a coder on a team. I ultimately failed. I'd like to go back and try again, after doing some really basic shit to improve my own character.