Dieter Rams' design principles applied to software engineering
1–10 of 63 posts
Re: Dieter Rams' design principles applied to software engineering
#2> 8. Good software is thorough down to the last detail
That's my approach. It tends to earn me a bit of scorn, but I do it anyway.
Re: Dieter Rams' design principles applied to software engineering
#3Re: Dieter Rams' design principles applied to software engineering
#4E.g. tell me how many times you've read an article about Jony Ive versus about an important software engineer at Apple.
Re: Dieter Rams' design principles applied to software engineering
#5Love that! > 8. Good software is thorough down to the last detail That's my approach. It tends to earn me a bit of scorn, but I do it anyway.
Re: Dieter Rams' design principles applied to software engineering
#6Love that! > 8. Good software is thorough down to the last detail That's my approach. It tends to earn me a bit of scorn, but I do it anyway.
Most people seem to be content with good enough and that is fine too. Diversity makes it fun somehow, there would be way less to discover and learn if we were all alike.
Maybe striving for greatness instead of perfection might be a way?
P.S.: Bookmarked your stuff last time you commented about testing harnesses and stuff. Haven't done iOS work in years and may never need it. I treasure a work ethic like yours, keep it up.
Re: Dieter Rams' design principles applied to software engineering
#7 > 3. Good software is aesthetic
>
> Take a moment to step back and look at your code.
> It should look beautiful to you.
> ...
It's not that the code quality doesn't matter, but this is just apples to oranges.Re: Dieter Rams' design principles applied to software engineering
#8Funny! I wrote the same article 6 years ago: https://www.dein.fr/2015-10-01-10-principles-for-good-code.h...
Spot on, intel immediately comes to mind. Will playing it safe always lead to mediocrity though? Depends i guess, heard that a good poker player loses less often.
(edit) Enjoyed reading the rest of the article too. In the environmental impact section i missed the idea of using more efficient languages though.
Loved your article "Learnings from six months as a first-time engineering manager" too. I was instantly reminded of the documentary on Michael Schuhmacher on Netflix i watched yesterday. I couldn't care less about Formula 1, but still think that it is an amazing movie and great role model for good leadership. He was asked over radio after he won the championship: "How do you feel?" There are several seconds of silence. He answers: "Ross you are the best. You guys are all great. We did it." I thought: "Wow, he puts the others before himself. A great example of a good King after the theory of archetypes by C.G. Jung"
Re: Dieter Rams' design principles applied to software engineering
#9Love that! > 8. Good software is thorough down to the last detail That's my approach. It tends to earn me a bit of scorn, but I do it anyway.
Re: Dieter Rams' design principles applied to software engineering
#10Funny! I wrote the same article 6 years ago: https://www.dein.fr/2015-10-01-10-principles-for-good-code.h...
> Companies that stay successful are the ones which don’t fear to constantly disrupt themselves through technological innovation. Spot on, intel immediately comes to mind. Will playing it safe always lead to mediocrity though? Depends i guess, heard that a good poker player loses less often. (edit) Enjoyed reading the rest of the article too. In the environmental impact section i missed the idea of using more efficie…