|
Yes. This.
I'm normally in agreement with him, but he's making some strange assumptions here that are not really obvious.
For example:
1. Who says that these experiments are slowing people down? Some people are slowed down, the majority isn't.
2. If those people would be concentrating on a handful of languages, would they agree on anything? Or would you just have more different frameworks for less languages?
3. He's not taking taste into account. People work faster in frameworks/languages they like. So programmers who don't like Bob's chosen 5 are out of luck?
Also, some people (like me) like learning new languages. Why take our fun away?
|
|
|
|
|
While the old and seasoned side of me agrees with this, I don't think it's a waste of time to challenge the norm. It's how we evolve. I'm a slow-to-move dinosaur myself, for those very reasons he mentioned. I didn't even care about .NET for years until I had to for work... because what's the point? I could do what I needed to do already.
Libraries like React are fantastic IMO. Thinking it's the next holy grail however is immature and silly. The pros know this, which is what the article suggests as well. But, I for one am glad someone decided to give it a go and make a lib that improves upon something.
I totally understand the "shiny new button syndrome" by newbs. But, every now and again, change is warranted.
It's the information age man. Too much clutter and not enough content. But sometimes there's content. Ya know.
Jeremy Falcon
|
|
|
|
|
I think the point Uncle Bob was making is the point you are making also.
He's saying, "Dont' just throw out the old stuff because it is old."
Instead, see it as a foundation of work that allows us to build further.
We probably couldn't have gotten to a good functional programming without going through and learning OOP.
However, don't believe that OOP is just old stuff now either. It is a foundational element to software development.
I think he is also attempting to say that there is a foundation of good software development methodology (the marketized names screw it up in most people's heads though) and we should gather those and use them throughout even as new technologies are born anew.
|
|
|
|
|
Well to that extent I agree. Personally, I still think C is a viable language for certain projects, and I'd never want to throw it away. But, C is also one of my favorite languages with a special place in my geek heart; so I'm already biased towards it.
I have no desire to use COBOL, even though I'm sure decades ago the same thing was said of COBOL as we're saying about OOP right now. I'm sure it has its merits too and served a purpose as well an evolutionary step towards the next. Doesn't mean I'd use it today though.
Not that I'm anti-OOP, can't be in this day in age. Guess it's all about balance. Don't change for change's sake, but change for something that's genuinely better. Unfortunately, that's not always the case and some folks get caught up in the hoopla of new buzzwords and changing because it's cool - not necessarily prudent. So, I totally get it, but not to the extent we become a dinosaur and thus the next generation of COBOL guys who aren't relevant anymore.
Jeremy Falcon
|
|
|
|
|
Great discussion and I agree with what you are saying. I really love C too and have been writing embedded AVR-C for Atmel (ATMega328) chips just recently.
Jeremy Falcon wrote: So, I totally get it, but not to the extent we become a dinosaur and thus the next generation of COBOL guys who aren't relevant anymore.
Totally agree with this too. Some people hang on to the past just because they don't want to change.
Balance is key. 
|
|
|
|
|
Jeremy Falcon
|
|
|
|
|
Exactly this. Chimps who don't have any analytical skills rush toward the next new thing because "It's new! It will solve all our problems!" instead of actually analyzing whether it is better.
At the same time, dinosaurs stick in the mud and can hack something together using an antiquated framework.
I'm not sure where the line is, but we need to keep pushing forward, while at the same time, only introducing new tools when they make sense for our project, not just because.
|
|
|
|
|
It's been true for years.
The only places where there can be gain are in applications and in libraries/frameworks for handling new requirements (e.g. for working with 3D moving images, and the like, when the technology for displaying it becomes available).
I've hardly ever seen new languages as increments in technology. Whenever they've contained something new, it could invariably have been added to an existing language at much less cost (of time and effort in learning to use it).
OO? Sure, it works, but I was coding objects in COBOL more than 30 years ago, without having to change anything about the language. I was ordered to read Booch, so that we could migrate -- at Huge expense -- to some new language (I don't even remember which one, now, but it wasn't SmallTalk or Pascal), and the entire book got no more than a "meh" out of me.
So I knocked up a presentation to show how we'd already been doing it for years, but without having given it a mysterious aura, and showed the costs of the two learning curves involved (one curve for ripping out what we were using and learning everything from scratch, and the other for memorising a handful of different names for the structures and processes we were already using).
Linear, object, functional, kabibbifuffle -- they're all just ways to massage the ones and zeroes; they can all do it all.
An improved IDE is worth a hundred times more than any new language, as is any library/framework that reduces the level of detail that you have to delve into.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: OO? Sure, it works, but I was coding objects in COBOL more than 30 years ago, without having to change anything about the language.
This is the voice of experience speaking. I remember thinking something similar for my C projects. Took me a while to jump unto the OOP bandwagon being so awesome it cures cancer. Just like it's gonna take people a while these days to jump onto the next thing.
Change is slow.
Mark_Wallace wrote: An improved IDE is worth a hundred times more than any new language, as is any library/framework that reduces the level of detail that you have to delve into.
Agreed. Although, having gotten used to some newer languages (in web dev at least) it's rough to go back.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: Change is slow.
There's the rub.
Change that doesn't really change anything, but only adds a few shortcuts, isn't real change, so why bother? If the very same shortcuts can be added to just about any language, with a Lot less effort than getting everyone to learn the p!ssballing intricacies, foibles, and shortfalls of a new one, then you've saved enough to pay for everyone's Christmas bonus.
Jeremy Falcon wrote: having gotten  used to some newer languages (in web dev at least) it's rough to go back
So use 'em!
The language doesn't make a blind bit of difference to the user/customer/visitor, so twiddle with the ones and zeroes in the way that's most efficient for you!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: Change that doesn't really change anything, but only adds a few shortcuts, isn't real change, so why bother? If the very same shortcuts can be added to just about any language, with a Lot less effort than getting everyone to learn the p!ssballing intricacies, foibles, and shortfalls of a new one, then you've saved enough to pay for everyone's Christmas bonus.
I agree, which is what I was speaking about earlier in this thread. Not all change is warranted or justified, but there times when it is. Turning a blind eye to change is called growing old and not adapting to the current world. Living in yesterday. So, it doesn't mean it can be dismissed altogether.
Mark_Wallace wrote: The language doesn't make a blind bit of difference to the user/customer/visitor, so twiddle with the ones and zeroes in the way that's most efficient for you!
You're preaching to the choir. I agree. My point with this though is sometimes your environment changes, and for the better. Refusing to think there is another way that may be more beneficial is just a foolish as the new shiny button chasing. It's about balance. Sometimes things need to be questioned. Sometimes not. But then sometimes so.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: growing old
Hey! I just had my 17th birthday, a few days ago*!
* Who the Hell wants to be an adult?
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Mark_Wallace wrote: Hey! I just had my 17th birthday, a few days ago*!
Oh wow, well happy birthday man.
Mark_Wallace wrote: Who the Hell wants to be an adult?
It comes in handy when you want to buy alcohol, and you learn stuff. Wisdom and all that. Only downside is you die.
Jeremy Falcon
|
|
|
|
|
Jeremy Falcon wrote: It comes in handy when you want to buy alcohol
Luckily, I'm 17 that looks like 57, so I can get away with it.
The fact that calendars say I'm actually 57 is bollocks. I don't live by Gregorian calendar rules; they're way to old to take seriously.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Ah I see, well in leap years, you're like what 14? Getting younger every day.
Jeremy Falcon
|
|
|
|
|
How many years have you been celebrating that 17th birthday (again)?
|
|
|
|
|
I remember the same thing in the early '90s when they were talking about CASE tools, and that they would make everything simple and programmers superfluous.
I have no idea how many times I have been asked to develop a product using a "new technology", only to recognize that a lot of what I needed to learn was based on some early tech I was acquainted with. It brings to mind the saying, those who forget the past are condemned to repeat it....
|
|
|
|
|
The problem is not we have or have not, or how much the progress is...The problem is that with far too many poorly educated 'professional' in lot of cases we sanctify the tool and not the solution...(A good solution is a good solution not matter what was the language/technology stack we used to create it)
With that attitude we created a fashion-driven culture (just like with almost everything else)...We no morce choose toolkit based on knowledge only, but also how shiny it is...And when it comes to justify it (for instance to move from C to Go), we call it progress...
For a most concrete example - I should take over a pro-bono project, developed using Angular as a SPA...I fill very bad about it, because that SPA contains over 200! actual pages tossed into one! file!!!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
To this I totally agree. Comparing it to fashion being very apropos... yay the shiny new button syndrome.
Jeremy Falcon
|
|
|
|
|
Kornfeld Eliyahu Peter wrote: A good solution is a good solution not matter what was the language/technology stack we used to create it
That's true. No matter what language you used to compile a program, it's still just small voltage variations being clocked through logic circuits in the end.
if (Object.DividedByZero == true) { Universe.Implode(); }
Meus ratio ex fortis machina. Simplicitatis de formae ac munus. -Foothill, 2016
|
|
|
|
|
I think that it happens mostly because it's more fun to gripe about languages and tools than it is to really understand your users and create what they need.
Also, to steal a line from Battlestar Galactica: all of this has happened before, and all of it will happen again. I used to hate waiting for Maven to download half the internet when first firing up a semi-complex Java on a new machine. So I'd go and gripe about how Java sucks, Maven sucks, and JS is awesome because I can write code that just works without needing a billion dependencies.
Now, if I clone a semi-complex React or Angular project and run 'npm install', I have to wait for NPM to download half the internet before I can do anything.
|
|
|
|
|
Every year. though we apply massive effort, we make less progress than the year before; because every year we get closer and closer to the asymptote.
No, every year we get new newbie asses. 
Marc
|
|
|
|
|
Uncle Bob has become that cranky old guy who yells at kids to get off his lawn.
Sorry, but we haven't actually got it all figured out yet. This is a silly rant from someone who doesn't want to adapt.
He sounds like a "communist" dictator. There will be no dissention! You will not try to create a better way to solve a problem! You will use the things we have always used! Our grandparents built houses with nothing but a hammer and some handmade nails, and so shall you!
Actually newer things are sometimes better. Maybe not all of them, maybe not always, but if you never try, then you'll still be building houses with nothing but a hammer and some handmade nails forever. And it's actually fun in the meantime, even if we spend a little time exploring new ideas. Every shiny new thing he derides is probably used successfully by millions of people.
Frankly the only reason I am still a software developer is because of new things. Who wants to bang out the same code in exactly the same way year after year?
|
|
|
|
|
I'm not a great fan of Uncle Bob's preaching but he is right here, but perhaps not quite for the reasons he puts.
Roughly the software development field turns over new technology every 5-10 years. What I learned as an Informix developer, or C/C++ developer or VB developer is more or less useless as far as building an applications goes. Sure, I've got some general principles to apply across all languages and technology stacks but there is also a hell of a lot of specific stuff that just doesn't transfer. Especially the raw, tested and proven code that I would recycle into other applications.
This means just as I'm getting really good at something (5+ years), say Linux/EsqlC/Informix I've got to dump that experience and re-tool. Hand on heart, can anyone really say we're 'experts' in anything? Even if I dusted down a language I used 10 years ago, there's a lot of stuff I've forgotten about it.
This sort of pace of change doesn't happen in other professions (say legal, accounting or medical) and in this context it shouldn't really come as a surprise that we struggle as a profession. I'm fairly sure, but can't prove, that one reason why the success of a project is such a crap shoot is because of the relative inexperience of the developers using a specific technology stack.
|
|
|
|
|
If a hippopotamus calls another one fat, is it just being hippocritical?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
