These are public posts tagged with #programmers. You can interact with them if you have an account anywhere in the fediverse.
Every great developer you know got there by solving problems they were unqualified to solve until they actually did it.
— Patrick McKenzie
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)
#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
My friend @jammcq and I are very different (you’ve heard us together on the #Podcast @RuntimeArguments), though we both do roughly the same thing: we’re both #Programmers. A big difference between us is the kinds of #SoftwareTools we use. I’m constantly trying new things to see if they might help. He generally sticks to the tools that already work for him, and upgrades only when something new is "better enough".
As an example: I use fd, rg, and exa. For him, find, grep, and ls are plenty good enough. And I agree! I get something out of the extra features of these tools, but they’re just not "better enough" to make a difference in his workflow.
Usually the new things I try aren’t even "better enough" for me. His bar is even higher. I have sold him on a few things, here and there. Now he uses #Git, #1Password, and fc; maybe others. We both want the same thing: we want to get more work done. We both project when thinking about the other’s style. He thinks I’m wasting time trying all the things I try. I think he could be going so much faster if he had some of the extra powers these newer tools give me.
It’s hard not to see things through your own lens. A neat thing about our relationship is that I can try things, and then if they pass muster with me they can sometimes become a possibility for him. And every once in a while, they **are** "better enough".
P.S. Some things I’m trying right now are #Zsh, the #HelixEditor, and managing my #SSH (private) keys in 1Password. I’m almost certain Helix is not going to become a part of his workflow! #Xonsh, #Zed, and #Kakoune weren’t better enough for me. I never even considered suggesting them to him!
Get out of the way of your developers or lose them to someone who will.
— Adrian Cockcroft
Here is some preamble boilerplate for #Perl #programmers who want to use features available from 2021 onward 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
.
Also, every one of those use
statements is lexically scoped, so you can adjust them per-file or per-code block too.
Why didn’t I go farther back than 2021’s v5.34? Because you really should use proper exception handling and stop being an animal with eval
and checking @?
.
Minimal try/catch with proper preservation of $@
MetaCPANSo, 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?
#32bit #64bit #devops #coding #programming #programmers #Linux
Ok hear me out #programmers
#Microservices which connect between each other seem to be an antipatern.
Let's think outside the box for a moment.
Throw them out replace with single layer between client and server. Every microservice which you had either needs to be converted into a library or use #Unix domain #sockets to communicate.
The only exception is communication between data-stores. For that you implement separated service.
#AI171 #Boeing 787 #crash—automation #software appears to be the prime suspect, now.
Heads up #programmers!
Enjoy the videos and music you love, upload original…
www.youtube.comhey #Devs #Programmers and #SoftwerEngineers What are the blogs or forums that I need to follow? Please recommend me some of them
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
Looking to expand your technical toolkit? We know it's tough to choose what to learn next, but that's about to get a whole lot easier.
Try your hand at any of 10+ programming languages--from Kotlin to C++ to PHP--with our new Coding for the Curious Humble Bundle.
This lineup is full of practical lessons. No fluff. No filler. Every purchase supports the EFF as they fight for your rights online. Check it out:
https://www.humblebundle.com/books/coding-for-curious-no-starch-books
A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.
— Robert A. Heinlein
A human being should be able to change a diaper, plan an invasion, butcher a hog, conn a ship, design a building, write a sonnet, balance accounts, build a wall, set a bone, comfort the dying, take orders, give orders, cooperate, act alone, solve equations, analyze a new problem, pitch manure, program a computer, cook a tasty meal, fight efficiently, die gallantly. Specialization is for insects.
— Robert A. Heinlein
The Tensors used at home versus the tensors used at work.
#llms #machinelearning #programming #rsi #programmers #devops
To all you beautiful nerds, this episode of Hyperfixed #podcast reaches all of you:
#typedesigners #musicains #programmers #circuitbenders #researchers #engineers
and it even comes with a #FreeFont download!
https://www.hyperfixedpod.com/listen/hyperfixed/little-by-little
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