There is an inescapable connection between the two. Knowing that stuff is not _equivalent_ to knowing good architecture, but it's hard to imagine what knowing good architecture would look like without being able to "think in code" through quite a few relatively narrow implementation details. Without that, you won't know the shape of the problem and how to architect around it.