(via https://chaos.social/@isotopp )
2025 on Tumblr: Trends That Defined the Year

No title available
YOU ARE THE REASON
AnasAbdin
Peter Solarz

Product Placement
trying on a metaphor
Show & Tell
hello vonnie

★

if i look back, i am lost

JBB: An Artblog!
Misplaced Lens Cap
Sade Olutola
art blog(derogatory)

#extradirty

shark vs the universe
One Nice Bug Per Day
tumblr dot com
Cosimo Galluzzi

seen from United States

seen from Türkiye

seen from Singapore

seen from Germany

seen from Spain
seen from Türkiye

seen from United States
seen from Malaysia
seen from United Kingdom
seen from United States

seen from Canada
seen from United States
seen from United Kingdom

seen from Türkiye

seen from United States
seen from United States
seen from United States

seen from Türkiye

seen from Germany

seen from United States
@fooyeahcode
(via https://chaos.social/@isotopp )
via IDEA is a series of nonverbal algorithm assembly instructions
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
So much complexity in software comes from trying to make one thing do two things.
Ryan Singer
“Hip, Hip, Hurrah! - Year long project runs flawlessly in production”
Peder Severin Krøyer
1888
Oil-on-canvas
what a great tumblr
keyboard for golang programming via https://twitter.com/jxxf/status/959490034163269632
via https://twitter.com/thecoderlife/status/934501994479472642
via https://twitter.com/casheeew/status/935418697434435584
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.
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’
Volkswagen detects when your tests are being run in a CI server, and makes them pass.
Classic development cycle
by misterjposts
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!
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!