Okay sure but would you say software is not about code? Yes of course people skills matter I get it but the baseline is still code, no? Isn't it then weird to say software is not about it but rather people?

▲

mjr00 a day ago | parent | next [-]

Yes but also no I guess? Like would you say being a manager or in marketing is about writing, or that being in sales is about talking? Those are the main methods of accomplishing what those roles are meant to do, but it's not like they're about writing and talking.

▲

altmanaltman a day ago | parent [-]

What do you mean being a manager or in marketing is about writing? Like that statement makes no sense and is wildly vague. The main role of being a manager is to write? The main role of being "in marketing" is to write? I think you're doing a lot of reducing in that and framing the wrong abstract "write". Same mistake as the article.

In fact, my entire point of the critisim is that you can apply the concept to every profession and it will still be valid hence its a banal weird thing.

Saying being a manager or in marketing is about people makes 100x more sense than to say its about writing. Almost all jobs involve people so it applies universally.

But that doesn't mean software is not code. that is still a weird thing to say and wrong.

	▲	mjr00 a day ago \| parent [-]
		Yes, I mean you've basically explained it without realizing it; "being a manager is about writing" and "being a software developer is about coding" are equally overly reductive statements.

▲

riknos314 a day ago | parent | prev [-]

The code is the "how", the problems that people need solved are the "why". The code is merely an implementation detail.

For most problems solvable in code, there are literally infinite valid code representations of possible solutions (at least in higher-abstraction languages, the space is much more bounded at the assembly level). If you consider the subset of those representations that result in sufficiently performant execution, does it really matter which one is running? This is where most programmers will start mentioning clean abstractions and readability and maintainability, but those are concerns of making the code understandable for people reading and modifying that code. The people are still the driving force.

I'm not arguing for slop here - I definitely care about code quality - but it's important to stay grounded in the reason that it matters: people.