|
Clickety[^
Quote: Here are the most important subjects for software engineering, with brief explanations:
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
These are all good things to know and practice - but author knows nothing of them...
4. Really? Since when software developers design critical algorithms? They are implementing them...
5. Happy wasn't eating/drinking while reading... Simply ridiculous...
7. Which of the thousands?
8. But, what if you write OS independent application (web)?
15. ?!?!? The idea is important, but what Hibernate has to do with my project?
18. We all do 90% of local-targeted projects...
20. Why the list that sort...
I can't help, but the feeling is that the author did a nice cut-and-paste job from all over the web without the tiniest clue what all this about...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
There is no one definitive list and no list is ever going to satisfy everyone, and everyone will have things they think are irrelevant or missing. It's just a high level list of useful items from one author's perspective. Everyone's list would be different.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Exactly! So if you (not you, btu the author) are talking about useful items at the global level, than stay at the global level!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Dominic Burford wrote: and no list is ever going to satisfy everyone
Doesn't need to; but if we take all list from CP and average them, you would see that there are a few items that keep coming back, on which we could reach consensus.
Dominic Burford wrote: Everyone's list would be different.
Then why is he presenting them as if everyone should know his list?
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
4. Big-O is extremely important if you want performant code.
5. UML is important if you want to write code from a specification / design
7. A general appreciation and understanding of what they are firstly, then you can deep dive into the many that are available
8. If writing OS agnostic software then fair point
15. ORMs are widely used and an appreciation and understanding of them can be beneficial (but not to all projects as you point out)
18. An important factor when developing multi-language applications
20. A longer list would have simply created more controversy 
As I said, we can debate the merits of any such list. My own list would be different too.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Dominic Burford wrote: 4. Big-O is extremely important if you want performant code.
Not really. Big-O makes a host of assumptions, which may or may not be applicable in an actual application with an actual data set.
I once had a huge argument with an engineer who insisted I replace a Trie algorithm with a BTree. On paper, he was right about insertions, but never understood that we were guaranteed to get the data set already sorted, the data set had to be replaced only twice a day at most and in actual testing the Trie was almost a magnitude faster on lookups. On top of that, the trie code was less than 30 lines of code and absurdly easy to understand.
Recently, I replaced one type of (std) dictionary to another; Big-O "promised" at least double the performance, it never came close to delivering (even when I tried to cheat the benchmarks!)
|
|
|
|
|
Big-O gives you an estimate of the complexity of any given algorithm given its input size. How well the algorithm performs on real data may be different to this estimate.
But that's exactly what Big-O is used for, to give initial estimates which then need to be tested with real data sets.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
Quote: Really? Since when software developers design critical algorithms? They are implementing them...
Since always?
The fact that many developers actually are just a little more than overpaid office workers tasked with menial developing tasks is out of the scope.
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
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
"When you have eliminated the JavaScript, whatever remains must be an empty page." -- Mike Hankey
|
|
|
|
|
So Google's search algorithms was designed by developers? Come on! You should know better...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
Big O notation actually is important in the same way that design patterns are important. It gives you a common language. When I'm in a code review and I say "You should use a Hashset, not a List right there" and the other guy asks "Why?", I'll tell him in big O notation.
|
|
|
|
|
Yes, actually it was and is. Of course, there's a difference between a mere coder and a developer. But I don't know any of the former who last very long on the job.
Decrease the belief in God, and you increase the numbers of those who wish to play at being God by being “society’s supervisors,” who deny the existence of divine standards, but are very serious about imposing their own standards on society.-Neal A. Maxwell
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
I like how their explanation of big O is completely wrong.
|
|
|
|
|
What is the correct explanation, IYHO? Sincere question.
Decrease the belief in God, and you increase the numbers of those who wish to play at being God by being “society’s supervisors,” who deny the existence of divine standards, but are very serious about imposing their own standards on society.-Neal A. Maxwell
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Big O notation characterizes functions according to their growth rates. It can be used to classify algorithms according to how they scale with changes in input size, but that (famously) does not predict the actual performance of a real implementation on realistic (or even worst case) input.
|
|
|
|
|
Thanks. Ah, so sort of the difference between theoretical (design) and reality (implementation).
Decrease the belief in God, and you increase the numbers of those who wish to play at being God by being “society’s supervisors,” who deny the existence of divine standards, but are very serious about imposing their own standards on society.-Neal A. Maxwell
You must accept 1 of 2 basic premises: Either we are alone in the universe or we are not alone. Either way, the implications are staggering!-Wernher von Braun
|
|
|
|
|
Quote: 6.Software processes and metrics: Software enginnering is not a random process.
I dont believe that - we have a bunch of PMs 
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
Any list that doesn't explicitly include "Know how to debug" is worthless.
|
|
|
|
|
Code.org, a non-profit that seeks to make coding more accessible, has launched a Star Wars-branded kid JavaScript program that stars Rey and BB-8. Midichlorians not required
|
|
|
|
|
Kent Sharkey wrote: Midichlorians not required
But helps 
Patrice
“Everything should be made as simple as possible, but no simpler.” Albert Einstein
|
|
|
|
|
Step 14 is wrongly defined/designed...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
This sounds like a winner
I got my BB8 about 3 weeks ago, and he was getting lonely
Best,
John
-- LogWizard Meet the Log Viewer that makes monitoring log files a joy!
|
|
|
|
|
Microsoft’s new facial recognition tool is out to judge your facial hair. The machine learning-based project comes just in time for Movember. Uhm. Happy Movember? (Apparently I don't have a face to analyze mine)
|
|
|
|
|
Extortion is just the latest in a series of weapons being used to terrorize computer users and technology companies. Welcome to the big leagues, Linux
|
|
|
|
|
The year of linux!!!
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
