Book lists for software engineers and architects

I came across this excellent article recently and while the target audience is Software Architects, in my view this is a great book list for anyone who is looking to grow their software engineering skills in general. I often talk to software engineers about reading books as part of their professional development plan (I’ll over this is in a post soon).

What I really like about this list is that it is actually planned with an approach of building on previous books. So you don’t have to follow this exact list, but what you might think about is the importance/value of having a planned set of books/references to build upon rather than just have a random set of books to read.“

I particularly like the approach of introducing the DDD books later in the path.The foundational aspects of the initial books sets up DDD really well.

https://haitham-raik.medium.com/books-for-great-software-architect-34c81fc70e12

Advertisement

Junior Developer Meetup Canberra 14 September

Meetup #3 – CODE and TELL

Thursday, Sep 14, 2017, 5:30 PM

Xero Canberra
Level 2, 10 Rudd Street Canberra, AU

12 Members Attending

We’ll have another exciting meetup – this time feel free to come along with something you’d like to show or talk about (maybe its something you are working on at the moment, ┬ácan you just contact [masked] or [masked] so that we get an idea of how many people will be doing a code and tell)

Check out this Meetup →

Great Article on Interviews for Software Engineers

Really excellent article for anyone thinking about a new job and in particular interviews.

http://www.c-sharpcorner.com/article/rock-your-technical-interview/

I want to highlight some very important points raised by the author:

1.PREPARE AND USE THE INTERVIEW AS AN EXPERIENCE

“Study Technical Questions – Basic Questions, Rehearse Difficult Questions, White Board, Write Down Missed Questions
  • Every time while going for any interview be prepared with basic questions, research some difficult questions with the answers prior to it.
  • After coming back from an interview, write down the missed questions.”

Prepare, Prepare, Prepare. This is an important event. Treat it like a really hard exam.

Also, learn from the experience. Keep a record of questions in a doc.

2.GETTING THERE ON TIME

  • “Dress appropriately. Be on time. Arriving 30 minutes early is good
  • Take two forms of maps: Because sometimes you will get traffic on any road; you have to know another road. Also, sometimes if you have taken a photograph into mobile and unfortunately the battery of your mobile gets discharged, in these cases, you have to carry a print out of the maps with the detailed address.”

OK, that might seem very straightforward but rushing or being late to an interview.

Great article on writing clean C# code

This is just gold. For any newbie touching C# please read this document – covers some really simple yet very important guidelines:

http://www.c-sharpcorner.com/article/tips-for-writing-clean-and-best-code-in-c-sharp/