https://en.wikipedia.org/wiki/Signal_(software)
Android, iOS; chat+call
https://www.bayernkurier.de/inland/11511-frauen-im-islam-menschen-zweiter-klasse
Zwei amerikanische Studien haben schon vor Jahren aufgeschlüsselt, was Muslime in aller Welt über Religion, Politik und Gesellschaft denken – und über Frauen.
gefunden in Leser-Kommentar zu
http://www.zeit.de/2016/11/kamel-daoud-schriftsteller-algerien-islamkritik
https://www.freshdesignweb.com/free-css-tables/ “40+ FREE BEAUTIFUL CSS CSS3 TABLE TEMPLATES”
http://dilbert.com/strip/2016-02-23 Kommentar dort:
Conventional wisdom: "good, fast, cheap -- pick two".
Wally: "bad, slow, expensive -- you're welcome".
http://www.gotw.ca/publications/mill02.htm Herb Sutter, 1998
With that example in mind, I'll propose the Interface Principle:
The Interface Principle
For a class X, all functions, including free functions, that both
(a) "mention" X, and
(b) are "supplied with" X
are logically part of X, because they form part of the interface of X.
http://githubengineering.com/move-fast/ – Ruby library ‘Scientist’ from GitHub: run new code in production parallel to existing code it’s meant to replace; compare the results; user always gets the result of the existing code; devs see the deviations that would occur in a production environment.
via https://blogs.msdn.microsoft.com/dotnet/2016/02/17/the-week-in-net-2172016/
http://martinfowler.com/articles/feature-toggles.html
http://dougseven.com/2014/04/17/knightmare-a-devops-cautionary-tale/
This is the story of how a company with nearly $400 million in assets went bankrupt in 45-minutes because of a failed deployment.
Yes, we've all violated any number of the cardinal rules of programming, the ones that everyone agrees are bad. And we secretly liked it.
[…]
To make matters more complex, sometimes it's better to break the rules. (Shhhh!) The code comes out cleaner. It may even be faster and simpler. The rules are usually a bit too broad, and an artful programmer can improve the code by breaking them. Don’t tell your boss, but sometimes it makes sense to code your own way.
What follows is a list of nine rules that some may consider unimpeachable, but many of us break often, with both success and pleasure.
Zum Schreiben von Blog Posts war Windows Live Writer top. Jetzt hat Microsoft losgelassen und ihn frei gegeben, mit Quellcode! So geht auch Blogger wieder damit.
http://www.hanselman.com/blog/AnnouncingOpenLiveWriterAnOpenSourceForkOfWindowsLiveWriter.aspx
Den Code werde ich mir auch mal anschauen: https://github.com/OpenLiveWriter/OpenLiveWriter
Leaders like Johnson have a special name at Amazon: they’re called HiPPOs, which stands for “highest paid person’s opinion.” HiPPOs are leaders who are so self-assured that they need neither other’s ideas nor data to affirm the correctness of their instinctual beliefs. Relying on their experience and smarts, they are quick to shoot down contradictory positions and dismissive of underling’s input.
Essential complexity
- What is needed to defeat to solve the problem
- Try to find the simplest solution
Accidental complexity
- introduced by the expressions of the solution
- Minimize it by using C++ well
Don’t over-abstract
- Base generalizations on concrete solutions
Hide complexity
- Good interfaces are essential
https://github.com/CppCon/CppCon2014/tree/master/Presentations/Make%20Simple%20Tasks%20Simple