Explore >> Select a destination
|
You are here 
|
solmaz.io | ||
| | | | |
arnorhs.dev
|
|
| | | | | I agree with everything about this: The shift from procedural to OO brings with it a shift from thinking about problems and solutions to thinking about architecture. Thats easy to see just by comparing a procedural Python program with an object-oriented one. The latter is almost always longer, full of extra interface and indentation and annotations. The temptation is to start moving trivial bits of code into classes and adding all these little methods and anticipating methods that arent needed yet but might be someday. via prog21: Dont Distract New Programmers with OOP. There's also a great discussion on the topic on Hacker News: https://news.ycombinator.com/item?id=2334939 | |
| | | | |
blog.hulacorn.com
|
|
| | | | | A recyled post blew up on reddit and then got picked up on Hacker news, what it looks like. | |
| | | | |
www.blog.montgomerie.net
|
|
| | | | | From a link on Hacker News (the occasionally interesting "Reddit for Erlang, Lisp and Haskell using proto-entrepreneurs"), this 2006 ACM Ubiquity article:Every programmer with a few years' experience or education has heard the phrase "premature optimization is the root of all evil." [...] Unfortunately, as with many ideas that grow to legendary status, the original meaning of this statement has been all but lost"I would not agree with all the proposed solutions to the problem, but I do agree with most of the observations. | |
| | | | |
avelino.run
|
|
| | | Discover how business metrics elevate the career of senior engineers and why they are essential for technical leadership roles | ||
