fooyeahcode

When I am programming, I am at a nexus. My thoughts become concrete. My ideas transform illusion into reality. The structure of existence is remade before my very eyes. I become a vessel for the creative force of the universe. I am carried aloft as if on the wings of dragons. Why should I care if nobody knows my name? The Hacker Ethic

[fooyeahcode]

(via https://chaos.social/@isotopp )

[fooyeahcode]

via IDEA is a series of nonverbal algorithm assembly instructions

[fooyeahcode]

Your domain model is not your object model. Your domain model is not your abstract data type model. Your object model is not your abstract data type model.

Now inheritance is easy again.

via Why inheritance never made any sense

[fooyeahcode]

So much complexity in software comes from trying to make one thing do two things.

Ryan Singer

[classicprogrammerpaintings]

“Hip, Hip, Hurrah! - Year long project runs flawlessly in production”

Peder Severin Krøyer

1888

Oil-on-canvas

[fooyeahcode]

what a great tumblr

[fooyeahcode]

keyboard for golang programming via https://twitter.com/jxxf/status/959490034163269632

[fooyeahcode]

via https://twitter.com/thecoderlife/status/934501994479472642

[fooyeahcode]

via https://twitter.com/casheeew/status/935418697434435584

[fooyeahcode]

me: sits through yet another mandatory hours-long meeting where the loudest two developers one-up each other to find the best hypothetical solution to the most convoluted problem they can imagine as it relates to the urgent, critical problem we currently face whose simple, plain solution goes entirely ignored and where no decision is made.

[fooyeahcode]

I call it my billion-dollar mistake. It was the invention of the null reference in 1965. At that time, I was designing the first comprehensive type system for references in an object oriented language (ALGOL W). My goal was to ensure that all use of references should be absolutely safe, with checking performed automatically by the compiler. But I couldn’t resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years.

Tony Hoare - The inventor of ‘null’

[fooyeahcode]

Volkswagen detects when your tests are being run in a CI server, and makes them pass.

[devopsreactions]

Classic development cycle

by misterjposts

[fooyeahcode]

[fooyeahcode]

People who don’t understand how currying and partial application work often use lambdas where they are not necessary.

Learn You a Haskell for Great Good!

[fooyeahcode]

The Zen of Python

Beautiful is better than ugly.     Explicit is better than implicit.     Simple is better than complex.     Complex is better than complicated.     Flat is better than nested.     Sparse is better than dense.     Readability counts.     Special cases aren't special enough to break the rules.     Although practicality beats purity.     Errors should never pass silently.     Unless explicitly silenced.     In the face of ambiguity, refuse the temptation to guess.     There should be one-- and preferably only one --obvious way to do it. Although that way may not be obvious at first unless you're Dutch.     Now is better than never.     Although never is often better than *right* now.     If the implementation is hard to explain, it's a bad idea.   If the implementation is easy to explain, it may be a good idea.   Namespaces are one honking great idea -- let's do more of those!

[fooyeahcode]

[fooyeahcode]