3 ms·
As a software engineer who didn't read almost any books about software engineering I have a question: How did reading any books about SWE changed the way you wo
by yoz-y 6y ago
As a software engineer who didn't read almost any books about software engineering I have a question: How did reading any books about SWE changed the way you work?
I found that reading books on other subjects (from non-fiction I've read some biographies, some economics books, the usual suspects like Sapiens and such). I find that knowing a bit about everything is mainly a good way to keep conversations going because it enables you to chip in on many different subjects while otherwise it might be hard to find a common interest.
It also helps to see some issues that one might overlook. An example would be American Kingpin which shows how a good technical idea with no moral oversight might end up creating something that ultimately makes world a little bit worse.
- happy_path 6y agoReading technical books has helped me pass some interviews and improve my programming skills. It also helps me learn new languages (Go) and do some personal projects. No personal project has helped me get a job though... Usually the part of out-of-scope of software is dealt by product managers. Maybe it is a problem of working in a big corporation?
- yoz-y 6y ago> Usually the part of out-of-scope of software is dealt by product managers. Life happens outside of work too, it's nice to be able to talk about other things than coding. Out of scope questions can be also useful when asked the feared "do you have questions?" question during recruitment.