Live data from Hacker News

Ask HN: Soliciting critique/feedback for your technical architecture?

news.ycombinator.com

11–14 of 14 posts

Re: Ask HN: Soliciting critique/feedback for your technical architecture?

#11
I like to start with a discussion, rather than a presentation and Q&A. For me, I find that really understanding the problem is the hard part. Once I really know what I need, what my requirements are, the options fall into place.

Today, for example, I'm going to have a whiteboarding session with one of my employees. We're going to whiteboard the problem we're solving, again, and again, until we both can describe high and low level details in our sleep.

Then we'll do a few searches and leverage other people's experiences to pick our technologies.

The also works for pure architectural discussions. You have a queue between your web server and web workers -- why? etc.

Re: Ask HN: Soliciting critique/feedback for your technical architecture?

#12
> Are there any reliable ways to get answers to such questions from people who are experienced?

In my experience, the challenge with soliciting this kind of feedback is in filtering the responses. Opinions are formed for a variety of reasons. Some are well formed from experience, while others are simply dogma:

Authority Figure X says to use Solution Y.

or cargo cult:

Successful Company X uses Solution Y, so you should too.

It's worth considering why authority figures recommend specific solutions, but that informs you as to the reasons why you should use a particular solution, not that you should always use a particular solution.

Giving a good recommendation first requires that the offerer of the opinion have the qualifications necessary to be considered an authority on the problem domain; second, that they invest the requisite time in understanding your unique set of circumstances; and finally, that they are prepared to set aside any dogmatic beliefs they have developed along the way. You must be prepared to filter the opinions you receive in order to avoid incorporating advice affected by these shortcomings.

Rather that solicit advice on your entire infrastructure, you should do two things:

1) You should seek to understand the technologies you're implementing to a depth that allows you to identify potential pitfalls. In other words, understand what a particular solution is good and bad at.

2) Try to hire/work with people who specialize in specific problem domains. A jack-of-all-trades can only have so much depth.

Re: Ask HN: Soliciting critique/feedback for your technical architecture?

#14
I have had need for critique on my architecture. What helps me is, I go to a tech meetup, and talk to a bunch of people. When I am working on a new side project, I will go and tell people about it and show them how I am planning on implementing it to solicit their opinions. I sometimes will ask a few co-workers to go to lunch with me with a purpose to talk about the project. Luckily I have at least one co-worker who loves advising and critiquing on my design decisions. Depending on where you live, I would recommend to join a tech meetup.
Post reply on HN