|
megaadam wrote: If two drunk astrologist argue
Is it two drunk astrologists, or "too drunk astrologist" fighting him/her-self?
Anyway it's uncertain, totally depends on the time and day.
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
Or is it "two too drunk"?
... such stuff as dreams are made on
|
|
|
|
|
Hello
Of Course you have read many books but which one had been more influence in your programing?
Please tell me the books with field of .net programing or SQL Server or design and architecture.
Thank you
SignatureNotFoundException
|
|
|
|
|
|
A very good series of books. I am currently reading this one.
veni bibi saltavi
|
|
|
|
|
Reading the synopses...
The large clear script, the careful choice of words
Doesn't sound like any code I've ever seen*, but this bit did:
The large clear script, the careful choice of wordsthe frequent repetition
Except my own of course 
|
|
|
|
|
I doubt it will help you very much, but it was this one here.[^] It came with my first computer in 1978 and I still have my old copy and sometimes read a chapter, just for fun.
This little book was so influential because it sent me on the way that always kept me close to the processor and gave me a notorious dislike of everything that tries to hide the processor from me, like interpreters and scripting languages.
Edit: let's not forget the great instruction set of the 1802:
0000 90 CLEAR: GHI 0 .. REGISTER 0 HAS 0001
0001 AE PLO 14 .. MAKE RE=0000
0002 BE PHI 14
0003 EE LOOP: SEX 14 .. EACH TIME, R14 IS -1
0004 73 STXD .. D STILL HAS 00
0005 30 BR LOOP .. GO BACK FOR ANOTHER
0006 03
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
modified 12-Jan-17 4:50am.
|
|
|
|
|
I can't narrow this down to a single book so I'll give a couple:
Clean Code by Robert Martin - great for general ideas of how to code in general to create readable, maintainable, and extensible code.
CLR via C# by Jeffrey Richter - excellent book if you're interested in CLR details and how languages use aspects of it.
Threading in C# by Joseph Albahari and C#6.0 in a Nutshell by Joseph and Ben Albahari - great for general knowledge of C# and threading specifics.
There are definitely more books worth mentioning. I plan to get around to reading Code Complete by Steven McConnell soon. For me one of the best resources to further my knowledge has been the internet - specifically MSDN. There is a wealth of knowledge to absorb - just don't take everything at face value and do your due diligence with research 
I never really had a single book that influenced me. The idea of programming and the challenges involved are what really influenced me.
|
|
|
|
|
|
Test the link yourself please I can not redirect.
SignatureNotFoundException
|
|
|
|
|
Works for me!
Check your firewall / antivirus / net nazis.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
The trouble with that book is that people buy it and don't read it ... so they ask for instructions in QA. 
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: The trouble with that book is that people buy it and don't read it ... so they ask for instructions in QA it exists.
FTFY Seriously though, it's pretty bad when SO copy-paste in production code is even a meme. That means it happens way too often
|
|
|
|
|
I have, very occasionally, been running a series called Pete's Book Of The Whatever (PBOTW) where I give a brief view on books that I have found interesting, informative, influential or challenging. Every time I post, I update this blog entry[^] with details and a link back to the original PBOTW.
This space for rent
|
|
|
|
|
These two:
[^]
[^]
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
The first and last one I read from cover to cover was Herb Schildt's Teach Yourself C. That's going back longer than I care to mention - pre-internet days.
These days, I find it easier to learn from on-line articles than books. There are some great resources out there on sites like this and SQLServerCentral and I've rarely felt the need to hit the book shop for IT purposes in the last few years. The last decent coding book I bought was John Skeet's C# in Depth which is great but not for the faint-hearted.
Slogans aren't solutions.
|
|
|
|
|
What! Not the K&R?
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
No, I've probably read all of K&R at some point or other but not in a start-at-the-start-finish-at-the-end kind of way.
The more I think about this topic, the more I realise that reading time is far, far more rewarding when devoted to the adventures of Jeeves and Wooster than it ever could be when looking at coding manuals.
Slogans aren't solutions.
|
|
|
|
|
Terry Pratchett - some good ideas in his books, the tourist in particular had a lot of good items that are actually real now.
Sin tack ear lol
Pressing the any key may be continuate
|
|
|
|
|
I tried him eons ago and wasn't overly taken with him at the time.
He's constantly getting recommended by people with similar tastes to myself, though, so I will give them another go at some point.
Slogans aren't solutions.
|
|
|
|
|
K&R is really a great book. It is even currently ranked #4 at amazon in Programming Languages section - Amazon Best Sellers: Best Computer Programming Languages[^] which is absolutely amazing considering how old that book is.
Also, think about how simple the book is. It just steps through these little programs building the readers knowledge with each page. The programs are so simple really but do some really interesting things. Of course it is all console based so that is interesting too,because the authors didn't have to worry about teaching UI type of layers.
Disclaimer : It may sound as if I'm saying the book isn't good, I'm not. However, it is interesting that a book written like that these days might not be accepted since a lot of readers would complain about all the "missing" parts. 
|
|
|
|
|
I think it was much easier to structure a book in those days because there was a simple entry point at "Hello World" which could be dealt with in the first couple of pages and things could build slowly and steadily from that.
Modern development environments don't really lend themselves to that approach. Make a new partition, install this VM, install that VM, kick your machine around the room, wipe it clean, reinstall everything, swear a lot, get this plug-in, get that plug-in, figure out some license agreement written in gibberish, get the plug-in you missed, swear some more, 'phone your brother because he's never seen a train crash ... before you know it, you're on chapter 96 without a single line of code having been written.
That's not to take anything away from the mighty K&R - quite possibly the best pair of developers who ever lived and pretty darned good at explaining it, too.
Slogans aren't solutions.
|
|
|
|
|
I agree 100%.
While developing my iphone/iPad app I had to install some CocoaPods thing that was simply entirely magic to me.
1. Go to terminal
2. type in command to pull libraries
3. hope
4. try to build...
if anything fails along the way, you don't know if it is a script that pulls the library or what.
We program from _mystery_ these days and have left _mastery_ behind.
|
|
|
|
|
raddevus wrote: We program from mystery these days and have left mastery behind.
That says it perfectly!
Slogans aren't solutions.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
