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.
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.
My first attempt to talk in front of people after Covid went well. Here is a video of my session where I explore the missing #fun at work as #programmers.
When I was a wee lad entering #software development (in the 1980s), most of us came from #EE and #CS backgrounds. And it was a common practice that each of us had small, pet projects—signal processing, image processing, hardware simulators, computer graphics, graph algorithms, networking protocols, programming languages, operating systems, chess engines, approximate polynomial algorithms for NP-complete problems, etc.—that we used to hone our theoretical and practical skills. These were toy problems, for sure; but they had heft, nonetheless. And we didn't just hack up the code; we studied the underlying theories, before we implemented these toy projects. And we didn't clone existing ones.
This was what I was referring to, when I posted earlier about "daily practice routine" for #programmers. I've tried to inculcate this good, life-long habit in my younger colleagues, without success.
These days, most software practitioners see themselves as mere coders, not programmers, and they feel no need to improve themselves, since they've already mastered JavaScript or Python syntax. This attitude is detrimental to the longevity of their careers.
These kids are swamped with having to maintain millions of lines of buggy code that their predecessors had cobbled together off StackOverview. There is no requirements, no specifications, no design, and no one person who understands the entire system.
Furthermore, their non-technical managers are always pounding them to keep raising their "commits", which is now the key metric used in promotion and pay rise.
As such, in just a couple of months of starting employment, eager youngsters turn into jaded code-pasters who experience no fulfilment in programming.
Every #musician has a personalised #practice daily routine. The experienced ones create their own, and novices follow the routines prescribed by their instructors. Naturally, the routines evolve with experience and skill. But even the retired professional musicians continue to practise their daily routines.
But we #programmers do not have a daily practice routine.
I'm talking about programming as a mathematical activity, not a mere mechanical coding task, like katas and koans that someone else published. I'm certainly not talking about learning to use database API, AI framework API, UI framework API, GPU API, and other mundane, job-related stuff, for there exists no opportunities to improve one's intellect in blindly following the dicta of an API. And not every aspect of life needs be seduced and induced by pecuniary interests.
By "daily practice routine", I mean a self-created, personalised routine that one performs daily for the rest of one's life, like a ritual, for at least an hour a day. This routine continuously evolves to target one's currently weakest skills, be they proof techniques, recursion, data structures, algorithms, computability theory, category theory, complexity theory, whatever.