Once upon a time in 2005 I attended my first #Linux symposium in #Ottawa. It was interesting to be surrounded by so many fellow geeks, most of whom made me feel wholly inadequate but that's beside the point. It's a real shame the event eventually failed. If I were better with faces I would tag people but I'm just not that guy. #geeks#hackers#programmers
*Use /search for search (/search?query=something)
*Move account secrets to a dedicated table (and encrypt it?)
*Add a way for the user to select which languages they understand
*Allow admins to configure instance favicon and logo
*Allow searching for hashtags in admin UI
*Convert Redux state to Typescript #MastoAdmin#devops#Programmers#dev.
Almost every practising horologist, luthier, or craftsman takes delight in his work. He takes pride in mastering the tools and techniques of the field. He makes it a point to study the history and background of the field, the tools, the techniques, and the thought leaders.
As #programmers, it behooves us to follow suit. We must know the languages, the algorithms, and the exponents of our field.
Most #IT#coders have never heard of Curry-Howard isomorphism between type theory and proof theory (type (\equiv) proposition, programme (\equiv) proof), which #programmers in #Maths and #CS have exploited for decades.
Knowing the techniques is well and good, but understanding the theories matters, at least as much.
Potential niche in YouTube or other educational sites for #programmers who like to teach:
Refresher courses designed for people who have basics of computer languages behind them and also people who already know the language but forgot it through disuse.
Basically, doesn't start off with explaining variables and loops and stuff, but assumes you know what those are and just spends a few minutes explaining gotchas and syntax for that language. It introduces you to conventions, and libraries & 1/2
I just had to give my #Windows 11 machine a page file. It has 64GB of DDR5 RAM and for some reason, it's all being grabbed by #Firefox plugins, Explorer, and tools like #Snagit in 1GB chunks.
It seems like #programmers these days are thinking "I'll just grab 1GB and commit it, doesn't matter if I don't use it...".
Programmers these days are mostly arseholes who did a 4-day online course though, so I am team #AI on this one.
#FORTRAN and #COBOL are dead.
Long live Fortran and Cobol.
Modern Fortran is indispensable for high-performance, scientific computing, like weather simulation on supercomputers. Modern Cobol is indispensable for high-throughput, business computing, like financial transaction processing on mainframes.
But Fortran and Cobol suffer from the image problem. Young #programmers will not devote their careers to these seemingly dead languages. As such, many Fortran and Cobol shops are desperately trying to "modernise" their codebases by translating into C++, Java, Python, etc.
This is a mistake. A weather forecast that takes a couple of hours for a Fortran implementation that runs on a 1000-CPU supercomputer will take months for a Python version that runs in an enterprise cloud. Analogous examples abound for Cobol. These niche systems are cloud-proof—they will not bend to the charms of cloud computing.
New language features and implementation techniques are continuously, albeit gradually, being integrated into Fortran and Cobol, and new supercomputers and mainframes are still being designed and manufactured. Yet, there is no injection of new programmers into these specialised domains.
A sensible approach, then, is this. Instead of converting pieces of code written in 60yo languages into those written in 30yo languages, design brand new languages—with dependent type system, algebraic types, type inferencing, memory safety, and other accoutrements of modernity—that target standardised Fortran and Cobol, much like TypeScript and ReScript target standardised JavaScript to "modernise" web development. And if these new languages become established, retarget them to binary.
hhhmm... so #programmers if you've ever made software and get feedback or ratings from customers/clients, i'm sure you can relate to the recipe author when they read this.
Just updated to current IOS and love that the swipe/delete in mail is now zippy, no longer laborious. Makes a big difference with daily spam. Thanks to programmer(s)/team and/or whoever made this unsexy tweak a priority!
Any other #programmers that can help me find motivation? At work it’s easier to set and achieve goals in a siloed environment. At home there’s too many options and idk what to do. Game design really intrigues me but I lack artistic creativity #coding#python
For fans of Code Girls and Hidden Figures, PROVING GROUND is the untold, WWII-era story of the six American women who programmed the world's first modern computer.
Se in un programma in C voglio chiamare l'indirizzo "http: //10.2.1.1/cm?cmnd=Power%20Toggle" (per accendere una luce con Sonoff) cosa mi consigliate di usare nella funzione system()?
Con lynx funziona:
system("lynx http: //10.2.1.1/cm?cmnd=Power%20Toggle");
ma vorrei qualcosa di più basso livello ancora, senza bisogno di dover scomodare troppi programmi.
The mind of a software engineer has two edges; one with which we interpret incomprehensible systems to wield them, and the other which makes us unable to empathize with users who must also comprehend these systems.
Before I say what it is, I am NOT posting this as clickbait (which is how it's often used)! 😂 I'm posting this as a Maths teacher who knows this topic inside-out and wants to help people to understand it better. There are MANY mistakes that people make and get the wrong answer, and I'm going to cover them in bite-size chunks each week for a few weeks
5/10
So all calcs bar one agree on the way to do this problem (and who on Earth knows why that one brand is doing something different - if you're going to allow people to enter a factorised expression then you have to make sure you obey The Distributive Law, as they are the reverse of each other).
Now, e-calculators (listen up #Developers#Programmers). I gave #Google a second chance, to see if it at least obeyed FOIL (i.e. expanding adjacent brackets), and... it doesn't (sigh)...
10/10
So #Developers#Programmers if your app/library isn't correctly parsing a(b+c) and/or (a+b)(c+d), preferably start by getting the latter working, by doing something like ((a+b)(c+d)) if needed, then changing the former to (a)(b+c) should also work. You could also turn a(b+c) into (a(b+c)). Never(!) add any other brackets or any other multiplication symbols anywhere else (that's the exact problem we have already - sigh).