4 ms·
97 Things Every Software Architect Should Know. Hands down. I just came across A Philosophy of Software Design and it looks good, but I haven't finished it yet.
by Desafinado 2y ago
97 Things Every Software Architect Should Know. Hands down. I just came across A Philosophy of Software Design and it looks good, but I haven't finished it yet.
My experience has been that 'programming' is largely about learning best practices, single responsibility, modularity, writing efficient, clean code. There are no real special books necessary for this, just read the industry standard recommendations.
But if you want to set yourself apart from others you need to study software design and architecture, and follow the big industry names on social channels. Designing software is more of an art and figuring out how to do it isn't immediately obvious or easily attainable from books. It takes years of experience and wide reading, and a lot of what I've learned about it has come from social media, not books.
- 0xperke 2y agothank you for your point of view! Which big industry names on social media would you recommend following?
- Desafinado 2y agoOne good way to do it is to follow Kent Beck on Linkedin. He's constantly reacting to other software influencers, and if you like the point of view of the other influencers, follow them too. Over time follow who you like, unfollow who you don't like. I'd also recommend following Jason Gorman. And sign up for a Mastodon instance and create a software list. These people are much more candid there than they are on Linkedin.