Note: A previous submission of this story by another user was deleted (not just flagged). Free speech is good, until you criticize the zionist actions.
Ultimately, coding font preference is subjective. For me, it's been JetBrains Mono since it was released several years ago. There's something about it that makes it so clean and pleasant to read.
I wish software had recipes for architecture. Design patterns are not the answer IMO. The problem with such approaches is that they tend to focus on the patterns themselves. Great software architecture emerges from modelling the problem itself, rather than trying to shoehorn the problem into a predefined set of patterns.
Start with deeply understanding the problem and let it guide you to choosing the right abstractions, dependencies, and arrangement of the various pieces into a system. It's more of an art than science: learn how to use a brush and mix colors then follow your vision, rather than using a set of cookie cutters that tend to produce something that obscures the obvious, and usually simpler, solution to the problem.
I disagree, especially if you are building software with other developers. Patterns help everyone get on the same page more easily and build better software. This is an engineering aspect that is often missing in software development because we tend to invent solutions based only on our own perspective
Mirrors my own experience, especially with Rails codebases: it's hard to navigate and find where something is declared due to the "convention over configuration" model.
One could, but the primary motivation to use AI to generate text is because it is fast and easy. You could spend an hour elaborately pretending to write something yourself, or you could simply write it yourself.
Linux started at the peak of Unix, but also when Unix was getting fragmented across vendors and mired in lawsuits. At the same time, PC hardware was getting better and faster, making the timing great for a PC-level Unix-like OS. Also remember that Linux didn't win in a short period of time. It would take over a decade (I'd say maybe two) for it be taken seriously.
I've come to the conclusion that technical superiority doesn't matter much. What matters is grit, perseverance over a long horizon, building an ecosystem (especially hardware drivers), accepting collaboration (be kind, not necessarily nice), and fostering a welcoming community.