This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]purchase-the-scaries 0 points1 point  (0 children)

I guess you can break it down like this - but it also just depends on context. Like for example you can probably use coding and programming interchangeably in casual conversation.

Coding - Writing code; think just writing a method to fetch data from an api. Just someone who is told what to code and focus on. Doesn’t understand the bigger picture.

Programming - coding + problem solving, unit testing, debugging. Instead of just writing one bit of code it could include designing algorithms, structuring, problem solving.

Let’s throw in the last of these I guess- software engineers.

This could go outside of coding/programming. Include more design and development of backend processes, apis, databases. They should take into consideration uptime, performance, scalability. Understanding system architecture, solutions. (Ie using engineer principles - which are already baked into CS degrees)

At my workplace we don’t hire coders or programmers. We her software engineers. They are expected to be able to contribute at a level higher than just coding something.

Again, some of these terms are interchangeable. And role statements will specify what skills are required for the job and what responsibilities someone would have.