I’m not sure you realize how “engineering disciplines” operate as crafts.
From the comment you are replying to:
[...] it’s not because what we do doesn’t have an element of craft in it, it’s because the concept of craftsmanship is not enough to explain what we do.
these comments on “operate like an engineering discipline” are mostly sourced from a cargo cult mentality
I have nothing to say to this. Have a nice day.
I'm one of those who think this book is outdated (or at least needs an update remain a "must read" for people working on software). The blog post linked as a top level comments does a good job of pointing out some of the problems. That' not to say it's worthless, but if we are going to recommend books to newcomers, they should reflect the state of the art understanding of the field.
It also reinforces this notion that software engineer has a craft component which really seems to rub some people the wrong way.
When it comes to craftsmanship, I also oppose Uncle Bob. Again, it's not because what we do doesn't have an element of craft in it, it's because the concept of craftsmanship is not enough to explain what we do. Dave Farley does a great job of explaining the reasons in his conference talk: Taking Back “Software Engineering” – Craftsmanship is Insufficient • Dave Farley • GOTO 2022. We are not in the middle ages any longer, we need operate like an engineering discipline.
Kent Beck presents some of the concepts discussed in this book in his conference talk: A Daily Practice of Empirical Software Design (Domain-Driven Design Europe 2023)
I was a bit underwhelmed by the content until part 3 where he delves into the theoretical grounds for planning "tidyings". He leans on economics to discuss when the best time is for making a refactoring. I find making that connection valuable. But the way concepts are explained are not very clear, in my opinion. I didn't think of this book as "well-written" in general. And despite the claims in the beginning of the book, I don't think a senior engineer has much to learn from it (not from the first two parts, anyway). Perhaps, part 3 should have been a separate book. That would be an interesting read with clearer and more detailed explanations, some anecdotes and examples.
Apart from the historical value, the most important part of this article now is the "Note of reflection" added 10 years after it's inception:
If your team is doing continuous delivery of software, I would suggest to adopt a much simpler workflow (like GitHub flow) instead of trying to shoehorn git-flow into your team.
I don't think this work flow is relevant any more even for teams that don't do CD, to be honest. It was a messy work flow to begin with and I haven't seen it applied successfully in practice.
Thanks for the response. It sucks to not have language being set in some implementations of ActivityPub. I think separating the write language settings from the read language settings would help a bit to set the corrent language when writing, at least. But I suspect that needs to be fixed in the core Lemmy (not instance specific).
I believe there is an API to create a local copy, but I'm not sure
Yeah, that's what I meant by non-elegant. I think the way Lemmy assigns IDs to posts and comments should be re-thought. Dictionary lookup is a solution, but not a good one.
I believe there is an API to convert such a link, but detecting that a link is going to a Lemmy instance might be difficult (or non-elegant).
This is great. I think "instance post/comment links" would be a great addition to Lemmy core in general, but don't know how easy it would be to implement. What I have in mind is: when someone provides a link to a post/comment in another instance, it would be converted to a link the person is logged in from. I think it would be OK to leave the link as is but add an icon next to it that goes to the correct URL for that instance.
You will have to ask that to instant admins. I think they have some custom code to display a message at the top.
Wouldn't it be better if the community was called "Programming Challenge" and have challenges for different frequencies (weekly, monthly, etc.). The mods may have some periods where they would change the pace (e.g., advent).
Also, how will this work without a mod?
TL;DR: I think it would be better to leave choosing the frequency to the mods.
Reading the manual? That's cheating!