python-architecture-linter VS architecture_decision_record

>I've found myself manually writing code for finding things in python's AST but a tool like this would be much more succinct

Wow, I also am writing a tool for finding things in the Python AST: https://github.com/Incognito/python-architecture-linter

It does other things too, but one of the key features is reading the AST. It's a bit of a prototype but if you want to jam together on a project I'd be open to it.

There's a fraudulent GitHub account that's stolen my bio and cloned one of my repos. I've reported to GitHub.

I'm seeking HN advice about the technical git aspects, because the fake user has somehow inserted themself as the "author" of many commits, then listed me as the "committer".

What are any ways to help protect from this kind of attack and/or fraud? And bigger picture, what are HN people doing at their companies to protect from this kind of attack and/or verify genuine code?

Here's me and the real repo: https://github.com/joelparkerhenderson/architecture-decision-record

Here's the fake user and the faked commits:

https://github.com/bestsoftwareandcodereviews3/architecture-decision-record/commits?author=bestsoftwareandcodereviews3

Hard disagree. Architecture retrospectives are not "the key" because 1) teams dislike spending time on them, 2) unlike sprint retrospectives, architecture retrospectives turn up issues that are very hard (or impossible) to adjust in real time, 3) retrospectives look backwards, and most teams aren't wired that way.

Instead, the key to getting better at architecting is preparing ahead of time, with slightly-more research and slightly-more teamwork, by using lightweight architectural decision records.

An architecture decision record (ADR) is a document that captures an important architecture decision made along with its context and consequences. When teams try ADRs, the teamwork goes up, the choices get better, and the implementations get more realistic which helps the groups. And if someone later wants to do the retrospective, the predictive information is right there ready in the ADR.

https://github.com/joelparkerhenderson/architecture-decision...

I'm translating the Architecture Decision Record project to more languages. I'm seeking advice and guidance please: how are you all managing translations of git repos of content such as documentation and markdown files?

My experiments so far are here:

https://github.com/sixarm/locale-help

My work-in-progress is to create a top level directory `./locales`, then subdirectories per language using a ISO 639-1 two-letter language code, then content directories, for example:

./locales/en/hello/ (this is in English)

./locales/es/hola/ (this is in Español a.k.a. Spanish)

What do you use to track which content directories correspond to each other across languages?

The Architecture Decision Record repo is now mostly auto-translated into Spanish, French, Welsh, and Korean, in the top level directory `./locales`, using the program `slug-case` to help translate the markdown content file headlines into directory names:

https://github.com/joelparkerhenderson/architecture-decision-record

Link is https://github.com/joelparkerhenderson/architecture-decision...

Hi, article author here, we supplement our architecture diagrams with Architectural Decision Records (ADRs) https://github.com/joelparkerhenderson/architecture-decision... in the ADR we capture:

Architecture decision record by joelparkerhenderson

If anyone wants to see Polar in action on a GitHub issue, I'm experimenting with Polar on my Architecture Decision Record repo:

https://github.com/joelparkerhenderson/architecture-decision...

(I'm on the fence about the value of Polar for this kind of issue... see what you think)

This method is only slightly formalized as ADR (architecture decision record). What I personally like about templates that people share on the interned (https://github.com/joelparkerhenderson/architecture-decision-record) it that if force designed to actually consider cons of selected approach or honestly attempt to analyze alternatives.

The GitHub repo joelparkerhenderson/architecture-decision-record is a good source to get an overview of tools, articles and examples.