Every great developer you know got there by solving problems they were unqualified to solve until they actually did it.

— Patrick McKenzie

Last weekend we had a #teambuilding event next to lake #Balaton. Contrary to all forecasts, we had a beautiful weather. There were also #programmers with us, so a #rubberduck was also enjoying the view

Types of #Programmers in #CS and #IT:

• Theorist—seek new discoveries in computability theory, complexity theory, and type theory (Church, Turning, Kleene, Cook, etc.)
• Inventor—design, analyse, prove, and publish an original algorithm (Knuth, Dijkstra, Karp, Tarjan, etc.)
• Engineer—devise a correct, efficient implementation of a published algorithm (implementers of DSP, DIP, etc.)
• Translator—convert an algorithm's mathematical description directly into a programme (CS undergraduates)
• Cobbler—cobble together APIs into a programme that might, or might not, work (senior IT practitioners)
• Cutter—cut and paste existing bits of code into a programme that just might do something unexpected (mid-level IT practitioners)
• Cleaner—clean up senior team members' messy, buggy code, while leaving the existing bugs intact and adding a few new ones (junior IT practitioners)
• Generator—ask AI to write direct-to-production code that no IT practitioner in the team could be bothered to read (senior IT managers)

#Firefox is fine. The people running it are not
#TheRegister article: https://www.theregister.com/2025/07/08/firefox_isnt_dead/

"#Mozilla's management is a #bug, not a #feature"
"#Dominance does not equal #importance, nor is dominance the same as #relevance. The #snag at Mozilla is a #management layer that doesn't appear to understand what works for its #product nor which parts of it matter most to users."
"Don't #blame the #app, and don't even blame the #programmers. That is, the ones who still have #jobs, after years of #engineer #layoffs. Don't even blame the whole #organization – blame the #management. Steven himself has pointed this out before, early in 2024. So have I. In 2023, I said that Mozilla was asleep at the wheel."

Programmers are as emotional and irrational as normal people.

— Douglas Crockford

When I'm trying to assert something and it gives me failure.

https://www.youtube.com/watch?v=3cunKaj7ZxA

...and then I realise it was a typo on the code.

My wife has a samsung phone. A new update changed the function of the side button into a gemini button. We had to search the internet in order to find out how to restore the function of this side button as she was not able to shut down her telephone. In the end we found the solution. It happens often, that programmers think they are clever enough to decide what is good for users. Let people decide for themselves. So utterlyannoying!
#google #gemini #stupid #programmers

#PROGRAMMERS !!! now that I have your attention. Please read and heed: https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ and https://github.com/kdeldycke/awesome-falsehood #Programming

JOKE: How many programmers does it take to change a light bulb?

None, that's a hardware problem.

Falsehoods #programmers believe about #aviation:

https://flightaware.engineering/falsehoods-programmers-believe-about-aviation/

My favorite one:

"Nobody will ever set their flight identification to weird things like NULL"

(thanks @ascherbaum)

Get out of the way of your developers or lose them to someone who will.

— Adrian Cockcroft

As of this writing, IMHO this is decent preamble boilerplate for #Perl #programmers who want to use most modern features while ensure compatibility with the Perl available via recent #Unix and #Linux operating system distributions, including #macOS and #WSL2:

#!/usr/bin/env perl

use v5.34;
use warnings;
use experimental qw(isa signatures try);

Don’t be scared by experimental; those features were accepted into subsequent versions of Perl.

Season to taste. For example, your codebase might be using something like Try::Tiny for exception handling syntax, in which case you’d leave out try. Every one of those uses is lexically scoped, so you can adjust them per-file or per-code block too.

So, apparently, some Linux distros, and library maintainers, are considering, or even in progress of, to drop support for 32-bit architectures? Here's an honest, and quite restrained question: what shit-for-brains decision maker came up with that brainfart?

Are you worried about addressing space? CPU performance? Bus performance? Too many #ifdefs ... What? Let's hear the golden arguments for this clever line of thinking?

Dear #programmers, please add a fistful of leading zero before the version number of your program.

The programmer, like the poet, works only slightly removed from pure thought-stuff. He builds his castles in the air, from air, creating by exertion of the imagination. Few media of creation are so flexible, so easy to polish and rework, so readily capable of realizing grand conceptual structures.

— Frederick P. Brooks

#Programmers that think #AI is #magic or is impossible to know how the AI works are the same that say that #maths are unnecessary to create software. At the end of the day AI is a kind of algorithm and algorithm is maths, the different is that AI uses complex maths so that's the reason some people thinks AI is magic. Also I know that the CEO of Antropic have said that AI could be an entity or they don't know how AI works. Of course this is marketing, they want to get money They have business.

A happy programmer is a productive programmer. That's why we optimize for happiness and you should too. Don't just pick tools and practices based on industry standards or performance metrics. Look at the intangibles: Is there passion, pride, and craftmanship here? Would you truly be happy working in this environment eight hours a day?

— 37Signals