Technical books and notes: Difference between revisions

From wiki
Jump to navigation Jump to search
imported>Johayek
(Created page with "== Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates == === Data Science at the Command Line === I want to run the Vagrant VM on some physical...")
 
imported>Johayek
mNo edit summary
 
(14 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Business/Publishing_and_Printing/Publishing/Books/Business/Addison_Wesley ==
=== The Pragmatic Programmer ===
Yet another book on [[Clean Code]].
* …
== Business/Publishing_and_Printing/Publishing/Books/Business/Manning ==
=== Minimal Perl ===
* http://www.manning.com/maher/
* …
== Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates ==
== Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates ==
=== 97 Things Every Programmer Should Know ===
Yet another book on [[Clean Code]].
==== #06: Be­fore You Refac­tor ====
* The best ap­proach for re­struc­tur­ing starts by tak­ing stock of the ex­ist­ing code­base and the tests writ­ten against that code.
* Avoid the temp­ta­tion to rewrite every­thing.
* Many in­cre­men­tal changes are bet­ter than one mas­sive change.
* After each de­vel­op­ment it­er­a­tion, it is im­por­tant to en­sure that the ex­ist­ing tests pass.
* Per­sonal pref­er­ences and ego shouldn't get in the way.
* New tech­nol­ogy is an in­suf­fi­cient rea­son to refac­tor.
* Re­mem­ber that hu­mans make mis­takes.
==== #08: The Boy Scout Rule – by Robert C. Mar­tin (Uncle Bob) ====
criticism: doesn't that violate "never change a running software"?!!
==== #88: The Unix Tools Are Your Friends ====
* mentions BusyBox and Cygwin
=== Data Science at the Command Line ===
=== Data Science at the Command Line ===
I want to run the Vagrant VM on some physical machine somewhere within my LAN,
==== running the Vagrant VM not just locally on some physical machine but … ====
let it have an interface and IP address on the LAN,
* I want to run the Vagrant VM on a strong physical machine attached to my LAN,
it's called ''data-science-toolbox'',
* I want the VM to have an interface (VirtualBox: ''Bridged Adapter'') and its own IP address on the LAN;
and I access it from another machine on my LAN:
* the VM's OS is ubuntu;
* its hostname is ''data-science-toolbox'';
* I want to access the OS from another machine on my LAN, not just from the machine, that hosts the VM:


<pre>
<pre>
$ ssh vagrant@data-science-toolbox
$ ssh vagrant@data-science-toolbox
</pre>
</pre>
If I start the Vagrant VM through its ordinary interface, Vagrant complains about a NAT rule of this names already existing.
But I am starting the VM from the ''Oracle VM VirtualBox Manager'' – that way it works without complaint.
With a entry in $HOME/.ssh/config :
<pre>
# from $HOME/.ssh/config :
Host data-science-toolbox
User vagrant
</pre>
… the ssh command line is even shorter:
<pre>
$ ssh data-science-toolbox
</pre>
==== installing the tools elsewhere ====
Appendix A lists the command-line tools together with their home pages.
== Business/Publishing_and_Printing/Publishing/Books/Business/Prentice_Hall ==
=== Robert C Martin and The Clean Code ===
Yet another book on [[Clean Code]].
== books on Clean Code ==
* [[Technical_books_and_notes#The_Pragmatic_Programmer]]
* [[Technical_books_and_notes#97_Things_Every_Programmer_Should_Know]]
* [[Technical_books_and_notes#Robert_C_Martin_and_The_Clean_Code]]

Latest revision as of 15:32, 24 August 2015

Business/Publishing_and_Printing/Publishing/Books/Business/Addison_Wesley[edit]

The Pragmatic Programmer[edit]

Yet another book on Clean Code.

  • …

Business/Publishing_and_Printing/Publishing/Books/Business/Manning[edit]

Minimal Perl[edit]

Business/Publishing_and_Printing/Publishing/Books/Business/O'Reilly_and_Associates[edit]

97 Things Every Programmer Should Know[edit]

Yet another book on Clean Code.

#06: Be­fore You Refac­tor[edit]

  • The best ap­proach for re­struc­tur­ing starts by tak­ing stock of the ex­ist­ing code­base and the tests writ­ten against that code.
  • Avoid the temp­ta­tion to rewrite every­thing.
  • Many in­cre­men­tal changes are bet­ter than one mas­sive change.
  • After each de­vel­op­ment it­er­a­tion, it is im­por­tant to en­sure that the ex­ist­ing tests pass.
  • Per­sonal pref­er­ences and ego shouldn't get in the way.
  • New tech­nol­ogy is an in­suf­fi­cient rea­son to refac­tor.
  • Re­mem­ber that hu­mans make mis­takes.

#08: The Boy Scout Rule – by Robert C. Mar­tin (Uncle Bob)[edit]

criticism: doesn't that violate "never change a running software"?!!

#88: The Unix Tools Are Your Friends[edit]

  • mentions BusyBox and Cygwin

Data Science at the Command Line[edit]

running the Vagrant VM not just locally on some physical machine but …[edit]

  • I want to run the Vagrant VM on a strong physical machine attached to my LAN,
  • I want the VM to have an interface (VirtualBox: Bridged Adapter) and its own IP address on the LAN;
  • the VM's OS is ubuntu;
  • its hostname is data-science-toolbox;
  • I want to access the OS from another machine on my LAN, not just from the machine, that hosts the VM:
$ ssh vagrant@data-science-toolbox

If I start the Vagrant VM through its ordinary interface, Vagrant complains about a NAT rule of this names already existing.

But I am starting the VM from the Oracle VM VirtualBox Manager – that way it works without complaint.

With a entry in $HOME/.ssh/config : 

# from $HOME/.ssh/config :
Host data-science-toolbox
	User vagrant

… the ssh command line is even shorter: 

$ ssh data-science-toolbox

installing the tools elsewhere[edit]

Appendix A lists the command-line tools together with their home pages.

Business/Publishing_and_Printing/Publishing/Books/Business/Prentice_Hall[edit]

Robert C Martin and The Clean Code[edit]

Yet another book on Clean Code.

books on Clean Code[edit]

Retrieved from ‘https://wiki.jochen.hayek.name/w/index.php?title=Technical_books_and_notes&oldid=1211’