Fair point - there are two kinds of overengineering. FizzBuzzEnterpriseEdition satirizes abstraction for abstraction's sake (AbstractStrategyFactory etc). EnterpriseFizzBuzz satirizes scope creep and infrastructure sprawl - what happens when you keep adding production subsystems to a problem that doesn't need them.
The subsystems aren't just alternative FizzBuzz implementations. The blockchain records FizzBuzz evaluations in a cryptographically linked ledger. The Paxos consensus reaches distributed agreement on whether 15 is FizzBuzz. The compliance framework creates a genuine regulatory paradox: GDPR demands deletion of records that SOX requires to be immutable and the blockchain can't remove. The on-call rotation formula (epoch_hours // 168) % 1 has returned "Bob McFizzington" for every rotation since 1970.
You're absolutely right! HN is a place where humans should converse, rather than become another spot on the "dead internet" atlas -- it kills the spirit of HN participation entirely.
Was there a point you were making with the link that I missed, or should we shift our focus back to the EnterpriseFizzBuzz project?
This is tracked as ADR-008 (Architectural Decision Record). The Hyphen Evaluation Subsystem requires a dedicated Unicode normalization pipeline, a locale-aware hyphenation engine (Knuth-Liang is under consideration), and a compliance review to determine whether the hyphen constitutes a data processing event under GDPR. Bob McFizzington has been assigned as the sole reviewer. His current availability is limited.
> our profession is not respected and has no social status
I'm going to disagree. I'm also going to assume there's a bit of hyperbole here. While the profession doesn't carry the same clout as a doctor or lawyer, people will generally think you are intelligent and educated when you tell them you are a software developer. Also if you work at a well-known company, and especially if you work on a well-known project, people will look up to you.
The profession itself is mid-tier, but there are plenty of opportunities within the field to have a high status position.
Stack Exchange sites depending on the topic (I'm just going to assume they generally don't have the toxicity of StackOverflow).
Also look around for smaller, more specific subreddits. As a general rule, the bigger the subreddit, the more moderated it will be.
Discord has been recommended. I'm backing it up. Same principle about moderation and size apply.
It wouldn't hurt to look at the comment section of a related blog post or even a YouTube video. The latter is scraping at the bottom of the barrel though.
I love stackexchange, but it is rather hostile to discussions. It is the best at asking questions, and getting them answered, but a discussion is cut short by the rules.
Couldn't agree more. And with tools such as Photoshop, it's much more efficient to learn as you go after being able to understand enough to navigate around the tool and its basic associated terminology.
I thought similarly about those books. But I was proven wrong after I read Scott Kelby's Lightroom book. The added value was understanding one author's workflow and also knowing what all features exist. Of course, one might say we can just google for all the features of Lightroom - but I personally never did that and book helped me learn all the superset of features. After that, I never referred to the book - I just google about specific things, now that I know what is out there.
There was once a discussion about reading programming books and similar point was made about learning on the go. One HN'er pointed out that reading end to end helps to know what all exists. It resonated strongly with me and since then, when I start on a new topic - I make sure to read at least one book end to end.
Agreed. Any sufficiently complex tool needs a good explanation of it's workflow. I was using Photoshop occasionally for years, but when I saw how people use it in real life (the photoshop guys episodes were great) a lot of stuff clicked and made much more sense so it was way easier to use.
Definitely if it's not your job and it's just a hobby. Just like how a hobbyist coder can get by without reading any books or learning about design patterns, etc.
But if it is your job to use photoshop on a daily basis it's worth going deep into that tome.
It wasn't my intention to speak ill of good books on photoshop. I was just trying to think of an example. I'm aware that there are probably great books on Photoshop, and that probably most are.
I also use Obsidian, and paired with a handwriting keyboard for Apple Pencil support (e.g. mazec; Apple's built-in scribble feature is too finnicky), it's been my Goldilocks note-taking method for the past few months.
reply