Programming

17318 readers

90 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

Mathematicians and software (lemmy.world)

submitted 10 months ago by [email protected] to c/[email protected]

5 comments fedilink hide all child comments

It is often echoed that mathematicians make excellent software engineers, and that their logic-adjacent work will translate efficiently into coding and designing.

I have found this to be almost universally untrue. I might even say the inverse is true.

While I and many of my peers have capacity to navigate the mathematical world, it certainly is not what sets us (at least me) apart when designing clever algorithms and software tricks.

Point being: I dont think the property/trait that makes good programmers is mathematical literacy.

I would love to hear what others experience is regarding this.

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

[–] [email protected] 1 points 10 months ago* (last edited 10 months ago)

Just because you're not writing high performance software doesn't mean it shouldn't be a consideration. Sure, I'm not gonna micro-optimize memory when I'm writing an API in Python, but that doesn't mean I'm not going to write it efficiently.

If I have to store and then do lookups on some structured data I'm gonna use a hash table to store it instead of an array. If I need to contact a DB multiple times I'm only gonna close my connection after the last query. None of this is particularly difficult, but knowing when to use certain DSA principles efficiently falls pretty firmly into the computer science realm.

If you need someone to hyper-optimize some computations then a mathematician might be a better bet, but even those problems are rarely mathematician level difficult. Generally software engineers have taken multivariate calculus/differential equations/linear algebra, so we're decently well versed in math. Doesn't mean we don't hate the one time a year we have to pull out some gradients or matrices though.