4 ms·
From an architecture standpoint I'd agree that most of the author's points are lamentable - if indeed there are people that call themselves architects who exhib
by aldente 11y ago
From an architecture standpoint I'd agree that most of the author's points are lamentable - if indeed there are people that call themselves architects who exhibit those traits.
But I'd also say that several aren't really valid criticisms - (class vs functions, tail-call optimization, trouble with git reset, ...) as they don't really seem to be aspects/tasks that I would expect from an architect.
They look more like things that overblown software developers might do.
And on that last point "written software that people enjoy using" - I don't think that is a good qualification for being an architect. There are plenty of people who can write software that end users love - but that is a total shitshow behind the browser.
- yodsanklai 11y agowhat's the problem with "git reset"?
- kasey_junk 11y agoWell I know lots of great developers who haven't used git (but have been using version control systems for 30 years), so using a particular command of a single version control system as a qualification for whether someone can architect something is inane.
- Blackthorn 11y agoI know that every time I have to use it (which isn't very often) I have to look up WTF each switch does in the manual because there's no way I'll ever remember what "hard", "soft", and "mixed" are supposed to mean.
- metral 11y agoIn https://git-scm.com/blog https://git-scm.com/blog, scroll down to "The Role of Reset" - it's always helped me remember how reset moves up the various tree roles. I will say, I personally rarely use --soft, it's either the default --mixed, or --hard in a more 'severe' case, so it's a bit easier for me to remember the roles and the relation to the flags.
- aldente 11y agoNothing other than it is totally irrelevant to architecture
- deleted 11y ago[deleted]