Comments for Code Simplicity http://www.codesimplicity.com Tue, 27 Dec 2011 03:40:15 -0600 http://wordpress.org/?v=2.8.6 hourly 1 Comment on What Is Overengineering? by John http://www.codesimplicity.com/post/what-is-overengineering/comment-page-1/#comment-2611 John Tue, 27 Dec 2011 03:40:15 +0000 http://www.codesimplicity.com/archives/12#comment-2611 I know the topic is stale, but I must chime in with a tell-tale sign that you're dev's (or yourself) is over engineering when: Code > DataModel When developers are more focused on macro-intricacies of their code VS retaining the integrity of the data model. IE: when you're code is building relationships to form data models VS the data models being normalized entities that I identify their relationships using primary identifiers. Most of the time, this is a result of the "Second System" effect where you need to prove your ninja status by producing the most robust backend operations that utilize every design pattern that the gang-of-four called out. My view: You can always re-factor and redesign shitty code, it's not so easy to roll back transactions after your data model is corrupted and/or fragmented. DataModel > Code Presentation > <b>To customer/user</b> VS mutli-threaded com apartments using a polymorhphic factory pattern. I know the topic is stale, but I must chime in with a tell-tale sign that you’re dev’s (or yourself) is over engineering when:

Code > DataModel

When developers are more focused on macro-intricacies of their code VS retaining the integrity of the data model.

IE: when you’re code is building relationships to form data models VS the data models being normalized entities that I identify their relationships using primary identifiers.

Most of the time, this is a result of the “Second System” effect where you need to prove your ninja status by producing the most robust backend operations that utilize every design pattern that the gang-of-four called out.

My view: You can always re-factor and redesign shitty code, it’s not so easy to roll back transactions after your data model is corrupted and/or fragmented.

DataModel > Code

Presentation > To customer/user VS mutli-threaded com apartments using a polymorhphic factory pattern.

]]> Comment on The Purpose of Software by James http://www.codesimplicity.com/post/the-purpose-of-software/comment-page-1/#comment-2609 James Wed, 14 Dec 2011 12:05:52 +0000 http://www.codesimplicity.com/archives/21#comment-2609 Sorry for resurrecting a really old post (great idea, and great responses on comments) but the Windows version of Solitaire was specifically designed to help people with their mousing skills :) http://en.wikipedia.org/wiki/Solitaire_(Windows)#History Sorry for resurrecting a really old post (great idea, and great responses on comments) but the Windows version of Solitaire was specifically designed to help people with their mousing skills :)

http://en.wikipedia.org/wiki/Solitaire_(Windows)#History

]]> Comment on Developer Hubris by Reilly Sweetland http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2589 Reilly Sweetland Tue, 29 Nov 2011 20:01:53 +0000 http://www.codesimplicity.com/?p=1033#comment-2589 I think there is also a certain aesthetic when a program allows a user to achieve their purpose with as little "program" as possible. In other words, how do you occupy the fewest number of mental cycles for the user to accomplish their purpose? Lots of fun UX discussions come out of this, but I think you nailed the main point here, Max. To a developer or designer, it's tempting to get wrapped up in the mechanics while loosing sight of the big picture. I think there is also a certain aesthetic when a program allows a user to achieve their purpose with as little “program” as possible. In other words, how do you occupy the fewest number of mental cycles for the user to accomplish their purpose?

Lots of fun UX discussions come out of this, but I think you nailed the main point here, Max. To a developer or designer, it’s tempting to get wrapped up in the mechanics while loosing sight of the big picture.

]]> Comment on Readability and Naming Things by Mike http://www.codesimplicity.com/post/readability-and-naming-things/comment-page-1/#comment-2588 Mike Tue, 29 Nov 2011 11:52:59 +0000 http://www.codesimplicity.com/?p=797#comment-2588 I agree!! Code is like poetry in that regard. How it lays on the page is part of the beauty, the art of it! I agree!!

Code is like poetry in that regard.

How it lays on the page is part of the beauty, the art of it!

]]> Comment on Clues to Complexity by Max Kanat-Alexander http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2585 Max Kanat-Alexander Tue, 29 Nov 2011 09:16:53 +0000 http://www.codesimplicity.com/?p=1056#comment-2585 Hey Palo! Thanks for your kind words! :-) Yeah, I agree, "it's too easy to make a mistake" is a very good one. :-) -Max Hey Palo! Thanks for your kind words! :-)

Yeah, I agree, “it’s too easy to make a mistake” is a very good one. :-)

-Max

]]> Comment on Clues to Complexity by Palo http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2584 Palo Tue, 29 Nov 2011 09:02:52 +0000 http://www.codesimplicity.com/?p=1056#comment-2584 Hi Max, I really like your blog posts. Last year I was working on a batch system for computing statistics from large datasets. I order to add a new bussiness rule I had to check and/or modify several non-related places including spring beans, property files and other stuff, all of these were trivial, but it was easy to make a mistake (for example there was a DB2/Oracle decimal/integer issue which no-one got right at the first time). So I think that a system is complex when it's very easy to make a mistake (the consequence is "You feel scared to modify this part of the code") Hi Max, I really like your blog posts. Last year I was working on a batch system for computing statistics from large datasets. I order to add a new bussiness rule I had to check and/or modify several non-related places including spring beans, property files and other stuff, all of these were trivial, but it was easy to make a mistake (for example there was a DB2/Oracle decimal/integer issue which no-one got right at the first time). So I think that a system is complex when it’s very easy to make a mistake (the consequence is “You feel scared to modify this part of the code”)

]]> Comment on The Singular Secret of the Rockstar Programmer by Michael http://www.codesimplicity.com/post/the-singular-secret-of-the-rockstar-programmer/comment-page-1/#comment-2565 Michael Sat, 19 Nov 2011 03:34:10 +0000 http://www.codesimplicity.com/?p=227#comment-2565 While there is an advantage in learning how the computer executes your instructions at a low-level, particularly for systems and microcontroller programming, a skill which the best programmers possess more consistently is the ability to abstract the complexities of a problem away and solve the problem at a higher level. Good programmers make things easy for themselves, because when you have to hold a lot of state in your head at once, you make mistakes which lead to bugs. Providing good abstractions also makes your code easier to maintain and expand by others. As a poster also mentioned, experience matters. I work with the best and brightest in the field (disclaimer: I'm a Software Engineer at Google), and I can't think of a single person here who has been coding for less than a decade. I've been coding myself for 19 years - the majority of my life. There's no substitute for putting in the time and <em>writing code</em>. Reading books isn't a substitute for writing code. Reading other people's code can teach you valuable lessons and give you insights, but they will fade quickly unless you write code using them. Ultimately, coding is an intuitive process. Mastery comes not from learning rules and patterns from books or others, but from internalizing patterns of thought required to solve a problem to the extent that you can devise most solutions without thinking. After a while, you just <em>know</em> how to do it. It's the practice of writing real code and solving real problems which gets you there. While there is an advantage in learning how the computer executes your instructions at a low-level, particularly for systems and microcontroller programming, a skill which the best programmers possess more consistently is the ability to abstract the complexities of a problem away and solve the problem at a higher level. Good programmers make things easy for themselves, because when you have to hold a lot of state in your head at once, you make mistakes which lead to bugs. Providing good abstractions also makes your code easier to maintain and expand by others.

As a poster also mentioned, experience matters. I work with the best and brightest in the field (disclaimer: I’m a Software Engineer at Google), and I can’t think of a single person here who has been coding for less than a decade. I’ve been coding myself for 19 years – the majority of my life. There’s no substitute for putting in the time and writing code. Reading books isn’t a substitute for writing code. Reading other people’s code can teach you valuable lessons and give you insights, but they will fade quickly unless you write code using them.

Ultimately, coding is an intuitive process. Mastery comes not from learning rules and patterns from books or others, but from internalizing patterns of thought required to solve a problem to the extent that you can devise most solutions without thinking. After a while, you just know how to do it. It’s the practice of writing real code and solving real problems which gets you there.

]]> Comment on Clues to Complexity by Raghu http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2559 Raghu Fri, 18 Nov 2011 05:54:52 +0000 http://www.codesimplicity.com/?p=1056#comment-2559 After reading Simon's comment above, I went to the site and found this. http://thedailywtf.com/Articles/Serious-String-Validation.aspx ~raghu After reading Simon’s comment above, I went to the site and found this.

http://thedailywtf.com/Articles/Serious-String-Validation.aspx

~raghu

]]> Comment on Clues to Complexity by Max Kanat-Alexander http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2556 Max Kanat-Alexander Fri, 18 Nov 2011 05:13:45 +0000 http://www.codesimplicity.com/?p=1056#comment-2556 Hahahaha!! WTF indeed!! -Max Hahahaha!! WTF indeed!!

-Max

]]> Comment on Clues to Complexity by Max Kanat-Alexander http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2555 Max Kanat-Alexander Fri, 18 Nov 2011 05:13:31 +0000 http://www.codesimplicity.com/?p=1056#comment-2555 Yeah! Those are pretty good! :-) Although, as far as test-writing goes, I've actually found it pretty common that tests can be larger than code. I think that's probably more an issue of the complexity of the requirements as opposed to the complexity of the code. -Max Yeah! Those are pretty good! :-)

Although, as far as test-writing goes, I’ve actually found it pretty common that tests can be larger than code. I think that’s probably more an issue of the complexity of the requirements as opposed to the complexity of the code.

-Max

]]> Comment on Clues to Complexity by Max Kanat-Alexander http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2554 Max Kanat-Alexander Fri, 18 Nov 2011 05:12:36 +0000 http://www.codesimplicity.com/?p=1056#comment-2554 Hahahaha! :-D Hahahaha! :-D

]]> Comment on Clues to Complexity by Max Kanat-Alexander http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2553 Max Kanat-Alexander Fri, 18 Nov 2011 05:12:26 +0000 http://www.codesimplicity.com/?p=1056#comment-2553 Yeah, those are good! :-) Although I wouldn't say that slow interpretation/compilation or the need for several languages are necessarily indicators of complexity. Some languages just have slow compilers, some projects are just large, and sometimes you have to use multiple tools to get the job done. -Max Yeah, those are good! :-) Although I wouldn’t say that slow interpretation/compilation or the need for several languages are necessarily indicators of complexity. Some languages just have slow compilers, some projects are just large, and sometimes you have to use multiple tools to get the job done.

-Max

]]> Comment on Clues to Complexity by Simon http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2552 Simon Fri, 18 Nov 2011 01:32:50 +0000 http://www.codesimplicity.com/?p=1056#comment-2552 The dependency tree looks like this? http://thedailywtf.com/Articles/Enterprise-Dependency-The-Next-Generation.aspx The dependency tree looks like this?

http://thedailywtf.com/Articles/Enterprise-Dependency-The-Next-Generation.aspx

]]> Comment on Clues to Complexity by Jerome http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2551 Jerome Thu, 17 Nov 2011 20:56:56 +0000 http://www.codesimplicity.com/?p=1056#comment-2551 A few other ones: - Your methods parameter lists grows out of control over time. - You feel the need to comment your control block endings (I call it 'if' inflation) - Writing a good coverage test would require more code than the method you want to test. A few other ones:

- Your methods parameter lists grows out of control over time.

- You feel the need to comment your control block endings (I call it ‘if’ inflation)

- Writing a good coverage test would require more code than the method you want to test.

]]> Comment on Clues to Complexity by John http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2550 John Thu, 17 Nov 2011 20:30:46 +0000 http://www.codesimplicity.com/?p=1056#comment-2550 How about "Management seriously considers hiring more than one manager to manage the developer working on a single class or file" :) How about “Management seriously considers hiring more than one manager to manage the developer working on a single class or file” :)

]]> Comment on Clues to Complexity by Andrew Pennebaker http://www.codesimplicity.com/post/clues-to-complexity/comment-page-1/#comment-2549 Andrew Pennebaker Thu, 17 Nov 2011 20:14:57 +0000 http://www.codesimplicity.com/?p=1056#comment-2549 • The code doesn't play well with other code (weak or no API). • Each function seems to require a custom input type. • Compilation or interpretation is slow. • The project requires several programming languages. • It would be really hard to decouple the project with its dependencies or switch to alternative libraries. • Developers talk about rewriting the whole thing from scratch. • The code doesn’t play well with other code (weak or no API).
• Each function seems to require a custom input type.
• Compilation or interpretation is slow.
• The project requires several programming languages.
• It would be really hard to decouple the project with its dependencies or switch to alternative libraries.
• Developers talk about rewriting the whole thing from scratch.

]]> Comment on Readability and Naming Things by Ricky http://www.codesimplicity.com/post/readability-and-naming-things/comment-page-1/#comment-2548 Ricky Thu, 17 Nov 2011 15:18:25 +0000 http://www.codesimplicity.com/?p=797#comment-2548 To me Readability of code is all about naming things. This sucks: <code> gU(2); </code> This rules: <code> getUserById(2) </code> To me Readability of code is all about naming things.

This sucks:


gU(2);

This rules:


getUserById(2)

]]> Comment on Developer Hubris by Max Kanat-Alexander http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2544 Max Kanat-Alexander Thu, 17 Nov 2011 07:02:11 +0000 http://www.codesimplicity.com/?p=1033#comment-2544 I tend to think that most of this sort of stuff is do-able in a way that's actually great for both power users and new users. I've actually been maintaining a product for many years that has to do exactly that all over its user interface, and I think we've lately been learning how to do it in a way that's actually quite workable for both groups. As far as the pop-ups: the purpose of the developer is not the purpose of the software. Also, history of computing shows that the winner is whoever serves the user the best while also executing well on the business side. Having an excellent product is a perfectly decent way to create brand awareness. I don't see Chrome popping up its name or its logo all over my browser interface, and yet it's gained market share faster than any other browser in history. I generally think that the "brand awareness" argument for harming the user is weak and short-sighted. -Max I tend to think that most of this sort of stuff is do-able in a way that’s actually great for both power users and new users. I’ve actually been maintaining a product for many years that has to do exactly that all over its user interface, and I think we’ve lately been learning how to do it in a way that’s actually quite workable for both groups.

As far as the pop-ups: the purpose of the developer is not the purpose of the software. Also, history of computing shows that the winner is whoever serves the user the best while also executing well on the business side. Having an excellent product is a perfectly decent way to create brand awareness. I don’t see Chrome popping up its name or its logo all over my browser interface, and yet it’s gained market share faster than any other browser in history. I generally think that the “brand awareness” argument for harming the user is weak and short-sighted.

-Max

]]> Comment on Developer Hubris by Max Kanat-Alexander http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2543 Max Kanat-Alexander Thu, 17 Nov 2011 06:58:15 +0000 http://www.codesimplicity.com/?p=1033#comment-2543 Hahahahaha! Yes, I love the doctor analogy! :-D -Max Hahahahaha! Yes, I love the doctor analogy! :-D

-Max

]]> Comment on Developer Hubris by Max Kanat-Alexander http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2542 Max Kanat-Alexander Thu, 17 Nov 2011 06:57:51 +0000 http://www.codesimplicity.com/?p=1033#comment-2542 Hahahaha! I hadn't thought of it, but sometimes it is like that, sure! :-D -Max Hahahaha! I hadn’t thought of it, but sometimes it is like that, sure! :-D

-Max

]]> Comment on Developer Hubris by Ben Morrow http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2541 Ben Morrow Thu, 17 Nov 2011 06:49:49 +0000 http://www.codesimplicity.com/?p=1033#comment-2541 A large contributing factor here is creating brand awareness via notifications. It sucks but most users don't get as far as realizing the notifications suck and associating that negatively with the brand. The hubris is probably ultimately the bigger factor. Man, can you imagine if your doctor kept calling you up in self congratulatory fashion regarding the fact you haven't contracted aids recently before offering you a health insurance upgrade to make extra sure. I'm sorry doctor Norton but I'm changing providers. A large contributing factor here is creating brand awareness via notifications. It sucks but most users don’t get as far as realizing the notifications suck and associating that negatively with the brand. The hubris is probably ultimately the bigger factor.

Man, can you imagine if your doctor kept calling you up in self congratulatory fashion regarding the fact you haven’t contracted aids recently before offering you a health insurance upgrade to make extra sure. I’m sorry doctor Norton but I’m changing providers.

]]> Comment on Developer Hubris by Vladimir Dzhuvinov http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2540 Vladimir Dzhuvinov Thu, 17 Nov 2011 06:48:38 +0000 http://www.codesimplicity.com/?p=1033#comment-2540 Max, are you alluding to one of the more widely used PC environments? ;) Max, are you alluding to one of the more widely used PC environments? ;)

]]> Comment on Developer Hubris by John P http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2539 John P Wed, 16 Nov 2011 17:15:57 +0000 http://www.codesimplicity.com/?p=1033#comment-2539 Different users though want different things. While one (perhaps an occasional user) may appreciate text labels with icons to easily find functionality, another (heavy daily user) may resent the extra screen space they take up. What attracts attention by its absence for the one, does so with its presence for the other. Mind you, I don't think there are many users who actually want intrusive pop-ups advertising program's presence at start-up. On the other hand, if they're successful in increasing awareness of the producer's brand, then they are serving a purpose to those who created them and will probably continue to exist. Different users though want different things. While one (perhaps an occasional user) may appreciate text labels with icons to easily find functionality, another (heavy daily user) may resent the extra screen space they take up. What attracts attention by its absence for the one, does so with its presence for the other.

Mind you, I don’t think there are many users who actually want intrusive pop-ups advertising program’s presence at start-up. On the other hand, if they’re successful in increasing awareness of the producer’s brand, then they are serving a purpose to those who created them and will probably continue to exist.

]]> Comment on Developer Hubris by Max Kanat-Alexander http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2537 Max Kanat-Alexander Wed, 16 Nov 2011 09:08:17 +0000 http://www.codesimplicity.com/?p=1033#comment-2537 That seems like a sensible and valid point. :-) I'm sure we all would agree that one must be careful with how many preferences one adds, though, but that is all caught up in making the preferences themselves simple. -Max That seems like a sensible and valid point. :-) I’m sure we all would agree that one must be careful with how many preferences one adds, though, but that is all caught up in making the preferences themselves simple.

-Max

]]> Comment on Developer Hubris by Tony Mechelynck http://www.codesimplicity.com/post/developer-hubris/comment-page-1/#comment-2536 Tony Mechelynck Wed, 16 Nov 2011 05:48:25 +0000 http://www.codesimplicity.com/?p=1033#comment-2536 I'll add something: Yes, your program should be transparent («go on unnoticed») and do, as much as is possible, what the user expects. But there are users with different preferences and different expectations. If ever one particular user finds that the program runs "contrary to expectations" (maybe because he has unusual expectations) the way to change configuration settings should be obvious (require little searching) and easy (need few user actions per changed setting). I’ll add something: Yes, your program should be transparent («go on unnoticed») and do, as much as is possible, what the user expects. But there are users with different preferences and different expectations. If ever one particular user finds that the program runs “contrary to expectations” (maybe because he has unusual expectations) the way to change configuration settings should be obvious (require little searching) and easy (need few user actions per changed setting).

]]> Comment on What Is A Computer? by Mary http://www.codesimplicity.com/post/what-is-a-computer/comment-page-1/#comment-2534 Mary Fri, 28 Oct 2011 04:54:32 +0000 http://www.codesimplicity.com/?p=47#comment-2534 What is computers anyway? I need answers, the clearer one... you see I'm working on research works about computer.. I have a hard time usually understanding it too.. What is computers anyway?

I need answers, the clearer one…

you see I’m working on research works about computer..
I have a hard time usually understanding it too..

]]> Comment on The Equation of Software Design by George Kalfopoulos http://www.codesimplicity.com/post/the-equation-of-software-design/comment-page-1/#comment-2533 George Kalfopoulos Tue, 25 Oct 2011 10:57:22 +0000 http://www.codesimplicity.com/?p=463#comment-2533 Quite a fascinating reading. A few days ago I wrote a more generic article on the value of software (can be found here if anyone cares http://softwaredev2k.com/2011/10/understanding-the-value-of-software/) which I updated today to link to this post for the more mathematically inclined. Great work indeed! Quite a fascinating reading.

A few days ago I wrote a more generic article on the value of software (can be found here if anyone cares http://softwaredev2k.com/2011/10/understanding-the-value-of-software/) which I updated today to link to this post for the more mathematically inclined.

Great work indeed!

]]> Comment on The Equation of Software Design by Understanding the value of software | Software Dev 2k http://www.codesimplicity.com/post/the-equation-of-software-design/comment-page-1/#comment-2532 Understanding the value of software | Software Dev 2k Tue, 25 Oct 2011 10:53:50 +0000 http://www.codesimplicity.com/?p=463#comment-2532 [...] recently discovered this post by Max Kanat-Alexander which attempts to create a mathematical formula on how to determine if [...] [...] recently discovered this post by Max Kanat-Alexander which attempts to create a mathematical formula on how to determine if [...]

]]> Comment on What Is Overengineering? by Thomas http://www.codesimplicity.com/post/what-is-overengineering/comment-page-1/#comment-2516 Thomas Thu, 22 Sep 2011 06:51:50 +0000 http://www.codesimplicity.com/archives/12#comment-2516 Great Post! Thank you :) Great Post! Thank you :)

]]> Comment on The Fourth Law of Software Design: Complexity vs. Ease of Maintenance by How to Manage Complexity and Simplify Your Life | Manilla Blog http://www.codesimplicity.com/post/the-fourth-law-of-software-design-complexity-vs-ease-of-maintenance/comment-page-1/#comment-2515 How to Manage Complexity and Simplify Your Life | Manilla Blog Mon, 19 Sep 2011 20:18:26 +0000 http://www.codesimplicity.com/archives/23#comment-2515 [...] software, you know that your complexity is out of control when it becomes harder and harder to make changes as the size of the code base grows. In music, complexity is out of control when your piece becomes [...] [...] software, you know that your complexity is out of control when it becomes harder and harder to make changes as the size of the code base grows. In music, complexity is out of control when your piece becomes [...]

]]> Comment on Why Programmers Suck by Calvin Froedge http://www.codesimplicity.com/post/why-programmers-suck/comment-page-1/#comment-2512 Calvin Froedge Tue, 13 Sep 2011 06:12:14 +0000 http://www.codesimplicity.com/?p=274#comment-2512 You, sir, are an idiot. I happen to know a professional programmer who writes programs that run extensive, highly complex assembly lines. He most certainly answers "yes" to all of those questions, as well as money others. There are some who are not content with mediocrity, even if you may be. You, sir, are an idiot. I happen to know a professional programmer who writes programs that run extensive, highly complex assembly lines. He most certainly answers “yes” to all of those questions, as well as money others.

There are some who are not content with mediocrity, even if you may be.

]]> Comment on The Purpose of Software by The Singular Secret of the Rockstar Programmer | 有心故我在 http://www.codesimplicity.com/post/the-purpose-of-software/comment-page-1/#comment-2490 The Singular Secret of the Rockstar Programmer | 有心故我在 Fri, 26 Aug 2011 16:18:47 +0000 http://www.codesimplicity.com/archives/21#comment-2490 [...] all the laws of software, before the purpose of software, before the science of software design itself, there is a singular fact that determines the [...] [...] all the laws of software, before the purpose of software, before the science of software design itself, there is a singular fact that determines the [...]

]]> Comment on The Singular Secret of the Rockstar Programmer by Rongqi Fan http://www.codesimplicity.com/post/the-singular-secret-of-the-rockstar-programmer/comment-page-1/#comment-2477 Rongqi Fan Fri, 19 Aug 2011 14:22:32 +0000 http://www.codesimplicity.com/?p=227#comment-2477 But this article don't tell us how to understand problem.I think the most important thing is the way to understand problem efficiently. But this article don’t tell us how to understand problem.I think the most important thing is the way to understand problem efficiently.

]]> Comment on The Singular Secret of the Rockstar Programmer by wangmeng http://www.codesimplicity.com/post/the-singular-secret-of-the-rockstar-programmer/comment-page-1/#comment-2474 wangmeng Tue, 16 Aug 2011 15:52:49 +0000 http://www.codesimplicity.com/?p=227#comment-2474 it's truth ! i like this article it’s truth ! i like this article

]]> Comment on The Fourth Law of Software Design: Complexity vs. Ease of Maintenance by Simplicity « The real-time embedded software baseline http://www.codesimplicity.com/post/the-fourth-law-of-software-design-complexity-vs-ease-of-maintenance/comment-page-1/#comment-2472 Simplicity « The real-time embedded software baseline Mon, 15 Aug 2011 02:04:51 +0000 http://www.codesimplicity.com/archives/23#comment-2472 [...] of a system is inversely proportional to the complexity of its individual pieces.” (Max Kanat-Alexander) – This principle is also confirmed by my experience and data where I see a clear correlation [...] [...] of a system is inversely proportional to the complexity of its individual pieces.” (Max Kanat-Alexander) – This principle is also confirmed by my experience and data where I see a clear correlation [...]

]]> Comment on The Singular Secret of the Rockstar Programmer by 成为编程巨星的唯一秘诀 | 众里寻“她” http://www.codesimplicity.com/post/the-singular-secret-of-the-rockstar-programmer/comment-page-1/#comment-2471 成为编程巨星的唯一秘诀 | 众里寻“她” Fri, 12 Aug 2011 01:39:35 +0000 http://www.codesimplicity.com/?p=227#comment-2471 [...] 本文是从《The Singular Secret of the Rockstar Programmer》这篇文章翻译而来。译文来自外刊IT评论《编程巨星的唯一秘诀》。 [...] [...] 本文是从《The Singular Secret of the Rockstar Programmer》这篇文章翻译而来。译文来自外刊IT评论《编程巨星的唯一秘诀》。 [...]

]]> Comment on The Singular Secret of the Rockstar Programmer by 外刊IT评论:编程巨星的唯一秘诀 | 重剑无锋 http://www.codesimplicity.com/post/the-singular-secret-of-the-rockstar-programmer/comment-page-1/#comment-2469 外刊IT评论:编程巨星的唯一秘诀 | 重剑无锋 Wed, 10 Aug 2011 05:56:54 +0000 http://www.codesimplicity.com/?p=227#comment-2469 [...] The Singular Secret of the Rockstar Programmer [...] [...] The Singular Secret of the Rockstar Programmer [...]

]]> Comment on The Singular Secret of the Rockstar Programmer by 编程巨星的唯一秘诀 - 神仙岛 http://www.codesimplicity.com/post/the-singular-secret-of-the-rockstar-programmer/comment-page-1/#comment-2467 编程巨星的唯一秘诀 - 神仙岛 Mon, 08 Aug 2011 02:39:30 +0000 http://www.codesimplicity.com/?p=227#comment-2467 [...] 八 8 业界科技 本文是从 The Singular Secret of the Rockstar Programmer [...] [...] 八 8 业界科技 本文是从 The Singular Secret of the Rockstar Programmer [...]

]]> Comment on The Singular Secret of the Rockstar Programmer by 编程巨星的唯一秘诀 – The Singular Secret of the Rockstar Programmer « huanghuangde http://www.codesimplicity.com/post/the-singular-secret-of-the-rockstar-programmer/comment-page-1/#comment-2466 编程巨星的唯一秘诀 – The Singular Secret of the Rockstar Programmer « huanghuangde Mon, 08 Aug 2011 00:42:32 +0000 http://www.codesimplicity.com/?p=227#comment-2466 [...] I won’t lie to you–it sometimes is a long path. But it is worthwhile. And at the end of it, you may find yourself suddenly the amazing senior engineer who everyone comes to for advice. You may be the incredible programmer who solves everything and is admired by all his peers. You might even come out a “rock star” with millions of dollars and a fantastically successful product. Who knows? I can’t tell you what to do or what to become. I can only point out some information that I’ve found to be truthful and valuable. What you do with it is up to you. (Source) [...] [...] I won’t lie to you–it sometimes is a long path. But it is worthwhile. And at the end of it, you may find yourself suddenly the amazing senior engineer who everyone comes to for advice. You may be the incredible programmer who solves everything and is admired by all his peers. You might even come out a “rock star” with millions of dollars and a fantastically successful product. Who knows? I can’t tell you what to do or what to become. I can only point out some information that I’ve found to be truthful and valuable. What you do with it is up to you. (Source) [...]

]]> Comment on The Purpose of Software by 编程巨星的唯一秘诀 – The Singular Secret of the Rockstar Programmer « huanghuangde http://www.codesimplicity.com/post/the-purpose-of-software/comment-page-1/#comment-2465 编程巨星的唯一秘诀 – The Singular Secret of the Rockstar Programmer « huanghuangde Mon, 08 Aug 2011 00:33:33 +0000 http://www.codesimplicity.com/archives/21#comment-2465 [...] all the laws of software, before the purpose of software, before the science of software design itself, there is a singular fact that determines the [...] [...] all the laws of software, before the purpose of software, before the science of software design itself, there is a singular fact that determines the [...]

]]>