Thread by @danieldibswe

It can be difficult getting the experience to become a network architect, but there are many things you can do even if your role today does not involve design. In this thread I will give you some pointers and feel free to add your own.

1/x

The first step is always the fundamentals. You need to have a good level of understanding of the fundamentals. If you don't know OSPF or ISIS, how will you know when to pick one over the other? You have to start with the fundamentals and get some operational experience also. 2/x

Start reading books on network design. Even if you aren't going for a certification, there are books like the CCDE study guide by my friend @CCDE066 There are books for the CCDP as well. You have the excellent The Art of network Architecture by @LadyNetwkr and @rtggeek 3/x

There are also a lot of other great resources such as Cisco Validated Designs (CVD). Many Cisco Live sessions, both on protocols and design. For example some of @nickrusso42518 @Peter_Paluch @eeariass @juangolbez and many others. Other vendors also have these type of docs 4/x

Then you also have other free resources from @nickrusso42518 at his site. Anything you can get from @zig_zsiga My friend @malcolmbooden is also offering training. There are also great resources at @ioshints some posts from @packetpushers etc. 5/x

As an Architect, you need to be comfortable presenting to others. Form a study group. Practice on presenting on technologies and when you would use them. Get uncomfortable. Argue for a protocol that is not your favourite. You will learn a lot from this. 6/x

In the study group you can have conversations on different technologies and when you would use them. Try mixing things up. Change parameters and see if that changes the choice of design. Practice collecting requirements in order to build a design. 7/x

When you have the requirements, see if others went with another solution. Why or why not?

There are many CCDE type scenarios out there. Some are free! Some you have to pay for, but it may still be worth it. Think of what it could do for your career. 8/x

Get very comfortable in comparing and contrasting. Why not blog about it? You will learn, others will learn, you become more known and it might be what lands you a spot at @TechFieldDay or even your future job! Writing skills are important for an Architect... 9/x

Any chance you see on getting involved with design, take it! Can you help with something at work? Does your friends or friends in the industry need some help with design? Just getting involved in discussions will evolve your skills and start changing your mindset. 10/x

You could also volunteer to help smaller orgs or charities with design work. It may not be the coolest environment but it's a good start and it could lead to something much bigger. You have to build the experience somehow. 11/x

Hopefully it's clear that there are many ways of learning design and in the end it's up to you if you are willing to spend the time forming and changing your mindset.

As @ioshints always says, this should probably have been a blog post 😅 I will turn it into that as well.