Thread Merge Successful: Please Delete

In summary, if you're looking for non-fiction books about the engineering field, Zion and The Electric Life of Michael Faraday are both good choices. Zion is more general, while The Electric Life of Michael Faraday is more focussed on Faraday's work in electrical engineering. Both are good choices, and either one would be a good introduction to the field for someone who is not already familiar with it.
  • #1
ZionArbadon
4
0
Please delete

<< berkeman merged two threads >>
 
Last edited by a moderator:
Physics news on Phys.org
  • #2
Anything by Henry-Petroski () or J E Gordon ()

Are well written non-specialist books
 
  • #3
Thank you, I shall look into these. ^-^
 
  • #4
Non-fiction related to my field

I'm entering the Electrical Engineering Tech field, and I'd like some good non-fiction (no textbooks) suggestions.

Thanks a lot :D

Zion
 
  • #6


Well it's not directly electrical engineering but Feynman's "Surely you're joking Mr. Feynman" is an absolute classic regardless.
 
  • #7


Any good biography of Faraday, besides being a pioneer of your field his "rags to riches" story is amazing. Also, Davy, his mentor, was a gas...

Maybe:

The Electric Life of Michael Faraday by Alan W. Hirshfeld
 
  • #8
ugh they merged my thread that i was trying to let drop off because it has an incorrect title. I kept trying to change it to "nonfiction" but I won't change correctly.
 
  • #9


ZionArbadon said:
I'm entering the Electrical Engineering Tech field, and I'd like some good non-fiction (no textbooks) suggestions.

Thanks a lot :D

Zion

Signor Marconi's magic box, by Weightman. About Marconi's quest to develop wireless communication.

Oliver Heaviside, by Nahin. This can get a little mathematical, but you can skip the math(which is mostly in appendices anyway) and still get a lotout of the history. Heaviside developed a lot of the tools used by EEs, and was quite a strange character.

The science of radio, by Nahin. The first half is about the early history of radio. The second half is essentially basic signals and systems, with an interesting slant. If it is too much for you, save it until after you freshman year. This was supposedly written as a textbook, but I am recommending it anyway. Assumes calculus and one year of calculus-based physics.

Player Piano, by Vonnegut.
 
  • #10


jasonRF said:
Player Piano, by Vonnegut.

Oops - player piano is fiction!
 

1. What does "Thread Merge Successful: Please Delete" mean?

"Thread Merge Successful: Please Delete" is a message that is commonly seen in code repositories or version control systems. It indicates that multiple threads or branches of code have been successfully merged together and that the previous threads or branches can now be deleted.

2. How does thread merging work?

Thread merging is a process used in version control systems to combine multiple threads or branches of code into a single thread or branch. This is typically done to incorporate changes or updates made by different team members into the main codebase.

3. Why is it important to delete the previous threads after a successful merge?

Deleting the previous threads after a successful merge helps to keep the code repository organized and prevents confusion. It also ensures that the main codebase only contains the most up-to-date and merged code, reducing the chances of conflicts or errors.

4. What happens if the previous threads are not deleted after a successful merge?

If the previous threads are not deleted after a successful merge, it can cause confusion and make it difficult to track changes to the codebase. It can also lead to conflicts or errors if the same changes are made in multiple threads without being merged together.

5. How can I ensure that thread merging is successful?

To ensure that thread merging is successful, it is important to carefully review and resolve any conflicts that may arise during the merge process. It is also helpful to regularly communicate and coordinate with team members to avoid making conflicting changes in different threads. Additionally, testing the merged code thoroughly before deleting the previous threads can help to catch any errors or issues.

Similar threads

  • Feedback and Announcements
Replies
7
Views
1K
  • Programming and Computer Science
Replies
5
Views
1K
  • Electromagnetism
Replies
8
Views
1K
  • Feedback and Announcements
2
Replies
42
Views
3K
Replies
13
Views
530
  • Programming and Computer Science
2
Replies
50
Views
4K
  • Feedback and Announcements
Replies
20
Views
2K
  • Feedback and Announcements
Replies
10
Views
1K
  • Feedback and Announcements
Replies
4
Views
1K
  • Introductory Physics Homework Help
Replies
4
Views
1K
Back
Top