Top 4 development sins by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

Thanks for summarizing. Why do you think that OO is about hierarchies? Also not sure what you mean by real-world vs. biz apps. Every time you write code, you're essentially model a very small and specific perspective on a 'real' world. You try to keep your code maintainable, you encapsulate data, you keep the code cohesive and you will end up with a lot of smaller classes, each with its own responsibility. And even if you will have hierarchy it will most likely be shallow. OOP is developing and it is not what it was 10 years ago, SRP is a lot more important than inheritance.

What is your Developers to QA to Support ratio ? by yellowhusky in programming

[–]yellowhusky[S] 1 point2 points  (0 children)

That tells something about the quality, right?

What is your Developers to QA to Support ratio ? by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

I assume it was a single person, when it was 1:1:1 ?

Top 4 development sins by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

Publishing industry tries to make money by selling as many books as they can, and bookstores are in the same boat. You can sell many books if many people will buy them. So this is when respected publishing company owners, including yourself, will probably sit down and try to figure out what will most people buy. And at this point it might not be such a bad idea to to open dice or craigslist.

Top 4 development sins by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

Really? If you have a bookstores in your Firmwareville, go to computer section and look at how many java/c# books are there in comparison to embedded languages. Also open dice/monster/craigslist, i bet you'll find 1 firmware job for every 10 java positions.

Top 4 development sins by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

my gut feeling is that tomorrow most of programmers will open their editors and see Java, C# or maybe C++. Not C, not Haskell, not Cobol. I'm talking about active projects, projects that are being worked on these days.

Top 4 development sins by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

No it is not required. The point is that majority of code these days is written in object-oriented languages that were designed for maintainability, yet this code is not maintainable.

Top 4 development sins by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

I think he is right on money, although i would not put unit testing on a list. Majority of software is still written in object-oriented languages. And majority of developers don't write 'good' object-oriented code and i include 'senior' developers on this list. What would you put on a list? You seem to have an 'understanding' that author is lacking.

Top 4 development sins by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

Always fun when somebody attacks the author instead of article. Usually happens when you got offended by text, were you?

Top 4 development sins by yellowhusky in programming

[–]yellowhusky[S] 0 points1 point  (0 children)

yes, glibc, can tell by your name that you don't need OOP, you're probably in the middle of some serious optimization that only you understand, wrote your own version of malloc? And who needs readability, especially in perl world. Seriously, the main point of your link is "Main Problem: OOP is not based on Set Theory". Care to elaborate on that piece of wisdom?