Our great sponsors
-
software-development
Notes and articles on software development. All content is original. Most of the content reflects the way that our current software team operates.
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
sbellware may have more to add, but there isn't a name for it. We focus more on the "it" than the branding of it. We do use the word "continuity" to describe our goal: https://github.com/aaronjensen/software-development/blob/mas...
> The words "equipment log" and "work product" sound pretty unique.
We call them "material logs", as equipment logs are more or less a subset of those. Just think about the sheet in every bathroom at a store that says when it was last cleaned, or the clipboard attached to the factory machine that lists its maintenance record and problems. Or the patient record outside of the patient's door.
"work product" just means, the product of our work. Nothing special about that one, I don't think.
> Are Erl's SOA books and Yourdon's on OOP still relevant?
I haven't read either, personally, though I have Yourdon's book en route. We use the term "structural design" quite a bit, so I'm curious to see Yourdon's take on what they call "structured design". From everything I've read about it, it sounds very similar to a lot of how we think about things as it seems to be the basis for much of the coupling and cohesion thought in our industry.
I'd also recommend studying Lean (not Lean Startup, which has much to do with Lean as non-fat yogurt does).
Conventional commits are great, especially if you add in commit linting.
Being able to programmatically increment semantic versions and automatically generate relevant changelogs is awesome.
It’s also nice to implement Commitizen[0] for a little hand holding until folks get used to the linting.
I used to care a lot about doing things the way that felt right to me, but now I just want some common standard that is easy for everyone to follow, easy to automate, and easy to verify programmatically.
Things like conventional commits and semantic versioning aren’t perfect, but they are quite good and apply broadly to many use cases with common tooling and conventions.
--
[0]: http://commitizen.github.io/cz-cli/
Related posts
- Does it make sense to write commit messages that include notes to yourself on how the project is going?
- How to Git Commit like a professional Developer?
- Experienced programmers...how do you create a meaningful git log on your project?
- Padronize seus commits com Commitlint + Husky + Commitzen
- On Git Commit Messages