Interesting piece. I also started programming in 1969. It was on an IBM DOS/360 Model 30 with 32K of memory and an 8 bit data path using Assembler. For the most part I agree with "Uncle Bob" . OJT with good mentoring is far better than formal schooling for producing good programmers. Most of the really bad programmers that I have met had computer science degrees. Whenever I needed to hire a programmer one my first questions had to do with why programming and CS. If the reply included "Money" and did not include "Fun" I would pass on them. Also being a coder is a LOT more fun than being the manager of coders.
In the early days, the best programmers I met got their start making small targeted changes to large complex systems, such as compilers. They had a concise coding style, which I later saw in the JDK 1.0 libraries. And the most energetic and innovative programmers were medical postgrads.
The problem with the db boundary is that it gets bloated every time an application programmer needs yet another query not quite unlike the last one they requested. That's why they want direct access to the db via some kind of high level DAL
Sure!!!!!!!!! ... a lot of this is just common sense.... said everyone "pretentiously" after watching.. i mean do you like the way he presents or do you want to call his presentation some interns 1st day.... Seems to me you are a lot more confused than you understand... i really doubt any of this made common sense to you :P
The arrow with a hollow triangle-head means "implements" -- so in the diagram, the Presenter implements a [Presenter]Boundary. The normal arrow means "contains" or "uses" -- so in the diagram, the Interactor uses or contains inside it a [Presenter]Boundary
Want to create best-in-class applications? Robert C. Martin (Uncle Bob) is here to show you how. In this talk, he explains high-level and practical strategies to clean up your architecture. ua-cam.com/video/HhNIttd87xs/v-deo.html #Agile #Rails #SoftwareDevelopment #SoftwareArchitecture #SoftwareEngineering
I wish "Uncle Bob" would lay off the physics and stick to what he knows. He incorrectly conflates system perturbations caused by observation with The Uncertainty Principle. A principle that is about something completely different, d(x)d(p) ≥ h/2. It stipulates that uncertainty has a minimum area for complementary variables proportional to Planck's constant. A far more mysterious claim than observer perturbation.
Gene Kochanowsky even though that is exactly the equation which i was thinking while uncle bob asked that question... i think we should refrain from nitpicking about our particular domain specific knowledge in the simplified examples of a programming lecture... the point here is to engage the audience in deep thought about how to combine the particle class with the wave class to produce a single objective reality.
Interesting piece. I also started programming in 1969. It was on an IBM DOS/360 Model 30 with 32K of memory and an 8 bit data path using Assembler. For the most part I agree with "Uncle Bob" . OJT with good mentoring is far better than formal schooling for producing good programmers. Most of the really bad programmers that I have met had computer science degrees. Whenever I needed to hire a programmer one my first questions had to do with why programming and CS. If the reply included "Money" and did not include "Fun" I would pass on them.
Also being a coder is a LOT more fun than being the manager of coders.
In the early days, the best programmers I met got their start making small targeted changes to large complex systems, such as compilers. They had a concise coding style, which I later saw in the JDK 1.0 libraries.
And the most energetic and innovative programmers were medical postgrads.
Thanks for the slide overlay. Pretty helpful.
thank you sir! probably saved me from a lot of mistakes I would have done in my future life.
The problem with the db boundary is that it gets bloated every time an application programmer needs yet another query not quite unlike the last one they requested. That's why they want direct access to the db via some kind of high level DAL
At 40:13 there is an error. Where it shows Request Model it should show Result Model.
How is the control object different from the controller? There it is in the middle just like a controller.
He seems to give this talk just about anywhere.
what do you want ??? a cookie ?
a lot of this is common sense, but I like the way he presents. What is this? some student interns day 1 presentation?
Sure!!!!!!!!! ... a lot of this is just common sense.... said everyone "pretentiously" after watching.. i mean do you like the way he presents or do you want to call his presentation some interns 1st day.... Seems to me you are a lot more confused than you understand... i really doubt any of this made common sense to you :P
I'm trying to understand his diagrams but I dont understand the arrows. Can someone point me in the right direction?
The arrow means outer layers of the architecture import (or require) the inner parts of the architecture and not the other way around
The arrow with a hollow triangle-head means "implements" -- so in the diagram, the Presenter implements a [Presenter]Boundary. The normal arrow means "contains" or "uses" -- so in the diagram, the Interactor uses or contains inside it a [Presenter]Boundary
what happened at 52 min?
Want to create best-in-class applications? Robert C. Martin (Uncle Bob) is here to show you how. In this talk, he explains high-level and practical strategies to clean up your architecture. ua-cam.com/video/HhNIttd87xs/v-deo.html
#Agile #Rails #SoftwareDevelopment #SoftwareArchitecture #SoftwareEngineering
not sure Robert C. Martin knows how the guilds worked, he would be a lot less enthusiastic about them
18:18 "Crash a plane" ... very prescient words, given what's gone on and is going on with the 737 Max. :(
I wish "Uncle Bob" would lay off the physics and stick to what he knows. He incorrectly conflates system perturbations caused by observation with The Uncertainty Principle. A principle that is about something completely different, d(x)d(p) ≥ h/2. It stipulates that uncertainty has a minimum area for complementary variables proportional to Planck's constant. A far more mysterious claim than observer perturbation.
Gene Kochanowsky even though that is exactly the equation which i was thinking while uncle bob asked that question... i think we should refrain from nitpicking about our particular domain specific knowledge in the simplified examples of a programming lecture... the point here is to engage the audience in deep thought about how to combine the particle class with the wave class to produce a single objective reality.
"This is 2014 we dont need something in our laptops that actually moves, something mechanical that spins, my god how old is that?"
Fans...
Passive cooling.
Dead code? S.O.L.I.D. seems to create it in spades.