|
There goes the neighborhood.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
The nerd-rage that's been going on Slashdot since the rumors first surfaced over the weekend is hilarious. That bunch is still comparing the MS of today with the MS of 20+ years ago.
|
|
|
|
|
It's probably the same people - in their teens/20s then, in their 30s/40s/50s today.
|
|
|
|
|
|
I know the 4 pillars of OOD - but my love is for abstraction and encapsulation. Polymorphism is useful, but I've found it confuses many developers. Inheritance results in hemorrhoids and other digestive issues, so unless I have a very, very generic object, I tend to avoid it.
That said, it baffles me to the point of wanting to cut myself why encapsulation is ignored. I'm living in a static global world where we hack away every day... I have a file that contains data. Why would you not write a class to handle it? Every damn tool we have is a C++ compiler. 
I'm thinking that to advance software development to the next level, control c / control v must be banned.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Nothing has happened to OOD; it is still a very powerful design tool. The problem is the severe shortage (and consequent high salaries) of good software engineers. In lieu of decent software engineers, companies hire programmers who are a lot cheaper, are much easier to find, but could not use proper design to save their lives.
Make no mistake; within their limitations, some of them are very good coders. If they were to be exposed to proper design principles (and some decent mentoring), some of them could become decent software engineers. The problem with the more capable ones is that they have no idea that OOD and other design tools even exist!
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
You must be a software guy  of course nothing has happened to OOD.
But your comments are dead on.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Daniel Pfeffer wrote: The problem is the severe shortage (and consequent high salaries) of good software engineers. In lieu of decent software engineers, companies hire programmers who are a lot cheaper, are much easier to find, but could not use proper design to save their lives.
And then said companies tell the remaining few senior devs to dumb down their code so the juniors can understand it, because the code reflects a well thought out design that befuddles those that don't have good design skills!
|
|
|
|
|
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
It is important to apply OOD to any project from the beginning. If you are starting out with a new project, the software architect role is applied and the software design is done in OOD.
Software development is advanced already. Its just maybe that the next generation of coders are learning python , JavaScript etc which may not embody the whole OOD concepts.
Also if you look at the Roadmap to becoming a web developer in 2018[^] , you just need to know a couple of frameworks.Also these days you either code for android or iOS and the cloud (google/aws/........) and are restricted
to the structure they offer in some ways.
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
modified 3-Jun-18 16:15pm.
|
|
|
|
|
Well, I don't do web. I suppose if it was the only thing available I could. I've seen too many people with a passing/functional knowledge of JavaScript call themselves software engineers. The sad thing, I see this all the time from very senior people, but I live in an embedded world, so C and C++ are interchangeable.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
|
 yeah, I hear you.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Expression is confusing when you just start with it. That part I understand. I used it for the first time and I was absolutely confused. I had to really force myself out of desire of reverting back to very familiar reflection classes and methods.
Once I got it, it ended up writing an entire generic, erm, framework(?) to add search functionality in MVC application through one line of code and a JSON file. This source code confused the folks who had to consume it in their applications.
However, using Where and not knowing Any is clear indication of ripping off code from the interwebs with no desire of at least understanding what it is.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
|
I need to watch out for these in my teams code. Can you suggest a C# book that focus on LINQ performance? I have to learn them first!
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
Not a recent book.
There's Pro LINQ by Apress, but that's from 2010 already 
However, you don't really need a book.
If you're working with LINQ-to-Entities I'd use a profiler and check out every SQL query that gets send to the database (I think they're printed in the output window as well, but that's a bit of a search).
For LINQ-to-Objects I wouldn't worry about performance too much, just make sure you keep the non-deferred LINQ operators for last 
Tools like Visual Studio and Resharper can also give you tips, like revert coll.Where(...).First(); to coll.First(...);
|
|
|
|
|
 oh wow LINQ is old. OR, there's so much already packed in, that people are still learning. hehe
thanks!
Starting to think people post kid pics in their profiles because that was the last time they were cute - Jeremy Falcon.
|
|
|
|
|
You can't be serious? That's both hilarious and infuriating.
|
|
|
|
|
Yeah really.
The good thing about this guy was that he knew his shortcomings and acted accordingly (did not invent anything new and when he did he asked a second opinion).
Then I've worked with people who were completely incompetent, but still thought they could tell shout me how to write my code 
|
|
|
|
|
charlieg wrote: I'm living in a static global world
My World is pretty dynamic.
charlieg wrote: control c / control v must be banned
No! I don't want to type that same basic template for model classes again and again. This and other goodies are there in my repository of common things I need in almost every project I work on. And I will copy and paste them. Wow, I am gansta!
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
the control c / control v comment was mostly in jest... mostly. 
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I'm glad I'm not the only one thinking this way 
|
|
|
|
|
charlieg wrote: Inheritance results in hemorrhoids and other digestive issues
Only if applied cluelessly (which I have done in several occasions and hopefully I learned from them though I wouldn't bet on it).
charlieg wrote: I have a file that contains data.
I have several of them.
charlieg wrote: I'm thinking that to advance software development to the next level, control c / control v must be banned.
You'd have fixed 90% of the bugs in our codebase and driven to the mental hospital one of my less favourite coworkers. Motion approved!
When I begin a new project I encapsulate everything, and I do the same when I'm tasked to modify something that exists. The only problem in my environment is that we don't have a single product but about five hundreds of them and growing, all with more or less the same code at different points in time over 20 years but no shared file. Each version has its own copy and the source control is a plain .zip file. This means that I may have to fix the same thing over a dozen of times before it becomes the new baseline for the future - the existing products are still to be maintained with the old code and architecture.
GCS d-- s-/++ a- C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
|
|
|
|
|
I would have agreed with you even still 2 years ago.
Now I am really facing the market reality, and I am less evangelistic about holy code. Actually, getting things done faster and cheaper has superseded the need of quality - alas - and people do not care about quality anymore. Security issues in Facebook due to poor coding ? After a bit of show from Zuckerberg, everybody has already forgotten. Thousands and thousands of bugs in Microsoft products ? People earn money by blogging and youtubing about workarounds.
So if the demand is "please get me this done for yesterday and for no money", then copy & paste code is plain OK.
In my current position, which gets a bit above the boundaries of SW development, management made the choice to get products done and tested in low-cost locations, with a ratio of 3 people designing for 2 people fixing the design mistakes as they pop up in series production. Altogether, these 5 people are still 1/3 the cost of one solid and experienced engineer here and they are processing about 2 to 3 times as much projects, so ... The trend in the industry is to get low-cost locations do rapid-prototyping as product design and rapid-fixing on a case to case demand, since - unless very bis issues - nobody cares about quality. The experience of the designers in low -cost locations grow faster than their cost, so in about 2 to 3 years, we can expect an equivalent design skill as in high-cost locations, but for still half of the price, and the 2 fixing guys can probably be reduced to 1.
The only sacrificed element in all this is a bit of quality, but foremost innovation - future will tell if the business model can survive.
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
