|
Maximilien wrote: I don't have electronic shifting on my bike
oh, so you're a luddite as well (wrt bikes) seriously, I have a Di2, it doesn't need charging very often, and I'm doing 100km a week at the moment
I think you forgot a 'drone' to attach the go-pro to, to get aerial pics
Have fun, sounds nice, pls try not to fall OFF anything - mountain, bike, ..
|
|
|
|
|
Why not install Kindle on your laptop or phone, or both?
|
|
|
|
|
Maximilien wrote: 1 cycling computer, 1 phone, 1 watch, 1 laptop, 1 external drive (*) , 1 real camera, 1 gopro (I'm trying that), 1 kindle, 1 card reader
Don't forget to take your bike.
|
|
|
|
|
I was at B&N recently (I wore a mask) and I was looking at the O'Reilly book, C# 8.0 In A Nutshell[^] Flipped it over and noticed it lists at $79.95. Wow!!!
Not sure how B&N stays in business and why they don't simply match the Amazon price ($50.99) (at least).
Anyways, APress books has an electronic bookshelf which is on sale Apress[^] and you get all of their content via downloadable books for 1 year for $79 (normally $99)*.
I hemmed and hawed about it but finally pulled the trigger and I've been reading, Pro ASP.NET Core 3 (Develop Cloud-Ready Web Applications Using MVC 3, Blazor, and Razor Pages)[^].
The author, Adam Freeman, is fantastic. This is one of those rare tech books quite like The Petzold Programming Windows 3.1.
Quote from the book:
Putting Patterns in Their Place
Design patterns provoke strong reactions, as the emails I receive from readers will testify. A substantial proportion of the messages I receive are complaints that I have not applied a pattern correctly.
Patterns are just other people’s solutions to the problems they encountered in other projects. If you find yourself facing the same problem, understanding how it has been
solved before can be helpful. But that doesn’t mean you have to follow the pattern exactly, or at all, as long as you understand the consequences. If a pattern is intended to make projects manageable, for example, and you choose to deviate from that pattern, then you must accept that your project may be more difficult to manage. But a pattern followed slavishly can be worse than no pattern at all, and no pattern is suited to every project.
My advice is to use patterns freely, adapt them as necessary, and ignore zealots who confuse patterns with commandments.
Also, his Chapter 5 : Essential C# Features is a great read that clears up many of the confusing items like
Quote:
** Managing null values - Use the null conditional and null coalescing operators
** Extending the functionality of a class without modifying it --> Define an extension method
** Expressing functions and methods concisely / Use lambda expressions
** Modifying an interface without requiring changes in its implementation classes --> Define a default implementation
** Performing work asynchronously --> Use tasks or the async/await keywords
** Producing a sequence of values over time --> Use an asynchronous enumerable
*I'm not affiliated with APress or get anything from this. I just read a lot and books are way too expensive.
|
|
|
|
|
I agree with him: patterns are generally a mistake. They are a "hammer" for most of the people who use it: every problem "looks like a nail", or can be twisted and bent to resemble a nail enough to apply the pattern.
They can be useful - but more often they are misapplied and that makes them worse than useless as far as I'm concerned.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Just like the earth follows a certain pattern around the sun
|
|
|
|
|
I agree. A lot of patterns are just band-wagon jumping. However, the CTO I currently work for has a great grasp of the entire GoF Patterns book and yet balances that with real usage.
The one thing I think is interesting related to patterns is the communication advantage you get.
When discussing design of parts and the you say, "Yeah, I'll apply an Adapter here etc."
Makes discussions quite a bit faster.
I think Freeman nails it though about the zealots out there though.
|
|
|
|
|
But doesn't a factory of factories always solve all your design problems???? /s
|
|
|
|
|
No, containers and microservices are the silver bullet that solve all problems
|
|
|
|
|
Why not both?
|
|
|
|
|
Only if you move it all to the cloud at the same time.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
My problem with most of the pattern enthusiasm is that folks gets so wrapped up in implementing the abstraction that they forget to do the actual job.
Instead of turtles, it's templates all the way down.
Software Zen: delete this;
|
|
|
|
|
Design patterns seem to be misunderstood as prescriptive, when they are actually intended to be descriptive. My understanding of them is that they (mostly) provide a shared vernacular around some common solutions to common programming problems. Essentially they're just a shorthand way of communicating broad aspects of software design.
|
|
|
|
|
A great summary of the problem of patterns and real purpose of them.
|
|
|
|
|
I had only started reading about patterns years after I finished college and had a decade+ worth of experience after that. My initial reaction has pretty much always been, "Oh, that? I've done that before...it has a formal name?"
|
|
|
|
|
Invaluable comment, especially the Apress subscription link. Thank you very much!
|
|
|
|
|
Thanks for the heads up about APress.
My wife would find it hard to knit without patterns.
In fact knitting patterns are probably amongst the earliest examples of programming instructions. 8-)
|
|
|
|
|
AndyChisholm wrote: In fact knitting patterns are probably amongst the earliest examples of programming instructions. 8-)
|
|
|
|
|
The Earth revolves around the Sun!
This may upset some people who think it revolves around them.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
But what does the Sun revolve around?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
The gravitational center of the Milky Way.
|
|
|
|
|
...and the next obvious question is, what does the Milky Way orbit?
...to which the simplified answer appears to be, it doesn't orbit anything.
Emphasis on "simplified", because the longer answer is left as an exercise to the reader...
|
|
|
|
|
The Milky Way does not literally orbit anything. It is a member of a galaxy cluster named the Local Group. Right now the Milky Way is falling towards Andromeda and the two galaxies will collide in about 3 billion years.
The difficult we do right away...
...the impossible takes slightly longer.
|
|
|
|
|
Richard Andrew x64 wrote: The Milky Way does not literally orbit anything
Don't count on that: Great Attractor - Wikipedia[^]
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
Yeah...I pretty much left the rest of the discussion "as an exercise to the reader". This pushes the boundaries of what I know about / I'm interested in further reading up on.
Beyond this, I'll just take what Neil deGrasse Tyson tells me for granted and nod approvingly.
|
|
|
|