This weekly roundup thread is intended for all culture war posts. 'Culture war' is vaguely defined, but it basically means controversial issues that fall along set tribal lines. Arguments over culture war issues generate a lot of heat and little light, and few deeply entrenched people ever change their minds. This thread is for voicing opinions and analyzing the state of the discussion while trying to optimize for light over heat.
Optimistically, we think that engaging with people you disagree with is worth your time, and so is being nice! Pessimistically, there are many dynamics that can lead discussions on Culture War topics to become unproductive. There's a human tendency to divide along tribal lines, praising your ingroup and vilifying your outgroup - and if you think you find it easy to criticize your ingroup, then it may be that your outgroup is not who you think it is. Extremists with opposing positions can feed off each other, highlighting each other's worst points to justify their own angry rhetoric, which becomes in turn a new example of bad behavior for the other side to highlight.
We would like to avoid these negative dynamics. Accordingly, we ask that you do not use this thread for waging the Culture War. Examples of waging the Culture War:
-
Shaming.
-
Attempting to 'build consensus' or enforce ideological conformity.
-
Making sweeping generalizations to vilify a group you dislike.
-
Recruiting for a cause.
-
Posting links that could be summarized as 'Boo outgroup!' Basically, if your content is 'Can you believe what Those People did this week?' then you should either refrain from posting, or do some very patient work to contextualize and/or steel-man the relevant viewpoint.
In general, you should argue to understand, not to win. This thread is not territory to be claimed by one group or another; indeed, the aim is to have many different viewpoints represented here. Thus, we also ask that you follow some guidelines:
-
Speak plainly. Avoid sarcasm and mockery. When disagreeing with someone, state your objections explicitly.
-
Be as precise and charitable as you can. Don't paraphrase unflatteringly.
-
Don't imply that someone said something they did not say, even if you think it follows from what they said.
-
Write like everyone is reading and you want them to be included in the discussion.
On an ad hoc basis, the mods will try to compile a list of the best posts/comments from the previous week, posted in Quality Contribution threads and archived at /r/TheThread. You may nominate a comment for this list by clicking on 'report' at the bottom of the post and typing 'Actually a quality contribution' as the report reason.
Jump in the discussion.
No email address required.
Notes -
Could you give more detail? In my (biased) experience, they're normally competentish (if given to trends and overcomplicating things). Generally they've been developing for a decade+ before taking the role, from what I've seen. There are however many PMs or such who misrepresent/get overly stuck to diagrams and i've met some people who managed to become architects without coding at all. At my work, I make architectural mvps with seniors with chunks of the functionality and low effort piping, then tell other juniors how to make everything production ready while seniors work on hard parts we aren't quite sure about.
But fundamentally it's an organizational issue. 10 experts alone could very well be better (and in some projects, I'm able to give parts each to domain experts who write their parts in a week and it's all done (waterfall can work!)). But engineers are normally at the behest of non-tech people coming up with stupid features, who change their minds, or the domain space isn't even properly explored with exploratory test models (so we can't do good engineering practices). But this can be justified, since the tech is supposed to automate away concrete tasks and processes, for people who are paying for it. Path of least resistance etc.
So I'm referring to software architect types who probably are competent, but also aren't doing a lot of coding anymore. The net result is grand plans that often fail, or succeed but overbudget, due to a lot of stuff just getting bogged down in bad ergonomics and day to day tasks that are harder than they should be. As a concrete example, I once worked on an ETL task run by a high level architect plus a bunch of fairly junior folks.
ETL tasks just dragged on, took forever, had lots of errors. One of the biggest errors was simply importing stuff to the wrong column, because the developer actually mapping json -> SQL had to manually map "input field_name -> integer column position in CSV file -> SQL loads the CSV". After about a year of delays due to transposing columns (
return [...20 columns...row['foo']['bar'], row['baz'][0]...]when it should have beenreturn [...row['baz'][0], row['foo']['bar']...]), a clever (new) junior dev finally figured out developers should just doreturn { 'foobar': row['foo']['bar'], ...}and wrote the system to translate 'foobar' -> column 23 by just checking the column order in SQL. Another example would be days added to any ticket just because setting up a testing env is a lot harder than it needs to be.The key point here is that in neither case did the architect actually spend much time actually doing the task that was dragging on and slowing the project. If they spent a month doing that, they probably would have just fixed it without much notice. And once we got that one clever guy, it did get fixed.
As it relates to this example, from what I've read, GRRM is actually good at the details of writing. But since he's retired from writing, he's put into the "clueless architect" role, and the actual people doing the implementation are just not able to actually fill in the details.
More options
Context Copy link
I have only very rarely worked with an architect who is competent. Most of the time, it's someone with little to no experience actually doing the technical work, who gives these high-level pie in the sky statements like "the system will take in lead, and output gold" with no indication whatsoever of how it should do that. Then they dust their hands off, go "OK your turn now" and leave it to the technical people to figure out how to actually make that happen.
I'm not saying competent architects don't exist, I've actually worked with some! But they are very much not the norm in my experience.
More options
Context Copy link
More options
Context Copy link