(Part 2) Best products from r/SoftwareEngineering

Since your thinking about putting some time and learning material and concepts that will help improve yourself, I recommend reading this one:
Make It Stick: The Science of Successful Learning https://www.amazon.com/dp/0674729013/ref=cm_sw_r_other_apa_1x21AbKZZ3XGE

I'm an embedded software engineer and I don't do much calculus. I do mess around with polynomials (which is just simple algebra) quite frequently. Polynomials are great ways to represent a nonlinear set of values for modeling analog sensors. My background is in electrical engineering so understanding Fourier analysis is really useful too but I haven't used it much which reminds me I probably should do a quick refresher on that soon.

I recommend this book to any software engineer no matter their level. It was an amazing read and gives you some insight on core methodologies to problem solving and just learning in general

https://www.amazon.com/Mind-Numbers-Science-Flunked-Algebra/dp/039916524X/ref=mp_s_a_1_3?adgrpid=57601891578&gclid=CjwKCAiAqqTuBRBAEiwA7B66hQSRttqQ90P0z_Eir5lDL0JXaHGw9w8HIcB-ePqxeHtD6LJffZe-MxoC7GYQAvD_BwE&hvadid=274722315593&hvdev=m&hvlocphy=1014452&hvnetw=g&hvpos=1t2&hvqmt=e&hvrand=13061966951674896290&hvtargid=kwd-295392791902&hydadcr=15176_9602975&keywords=a+mind+for+numbers&qid=1573500656&sr=8-3

Clean Code Books:

• Clean Code: A Handbook of Agile Software Craftsmanship https://www.amazon.com/dp/0132350882/ref=cm_sw_r_cp_api_i_2k80CbD4F4QHJ
  
• The Clean Coder: A Code of Conduct for Professional Programmers https://www.amazon.com/dp/0137081073/ref=cm_sw_r_cp_api_i_Ml80CbREG48TD
  
  Design Patterns:
  
• https://sourcemaking.com/design_patterns
  
  And of course, good ol’ practice.

>The word engineer has been hijacked in various job titles such as software engineer, systems engineer and even sales engineer. But none of these positions are actually engineers at least not in how we use to use the word.

I fail to see how these job titles "hijack" the word engineer. I think the biggest problem is that there isn't a good understanding of what engineering is or what an engineer does, and part of that comes from the fact that there's very little published about engineering outside the context of a particular engineering discipline. We know that not all engineering disciplines are the same - I think most people would agree that a chemical engineer and a civil engineer and a mechanical engineer are all definitely engineers, but the things they do and how they do them are radically different. Even within a discipline, there are a broad variety of ways to do work. I'd highly recommend reading Billy Vaughn Koen's Discussion of the Method: Conducting the Engineer's Approach to Problem Solving. Koen also has an earlier paper - Definition of the Engineering Method - that is an early draft of the first 3 or so parts of the book, and the PDF full text of that is available.

​

>My reason for asking is now that I work in a country where software engineer title doesn't exist and is actually software developer instead.

That's generally the choice of the company. Unless all use of the title "engineer" is regulated by the government, companies are generally free to choose their own terms and titles.

​

>I'm wondering what software engineer means to you?

I'm pretty much in line with a lot of what Koen writes about, so I'd check out his paper or book. Using his definitions, I'd say that software engineering is the use of heuristics to cause desired changes in an unknown or uncertain environment or situation within the constraints and available resources. Koen defines a heuristic as "anything that provides a plausible aid or direction in the Solution of a problem but is_ in, the final analysis unjustified, incapable of justification, and fallible". Anyone who does this is conducting software engineering. However, I also think that in engineering, there's a side of professional responsibility and ethics. Koen doesn't get into this, but I believe that people who call themselves engineers also have obligations to the stakeholders in the things that they create or maintain or design, to other members of the profession, and to themselves.

Maybe a bit too much to start with but I really like https://www.amazon.co.uk/Clean-Architecture-Craftsmans-Software-Structure/dp/0134494164

Read Head First design patterns and really understand what encapsulation means.

Looking for something a bit more full stack.

Tried Beginning ASP.NET for Visual Studio 2015 a few years back and while the topic was what I am looking for, the book was full of errors and was essentially unusable