Create accountLogin

Recent searches

No recent searches

Search options

Only available when logged in.
en.osm.town is one of the many independent Mastodon servers you can use to participate in the fediverse.
An independent, community of OpenStreetMap people on the Fediverse/Mastodon. Funding graciously provided by the OpenStreetMap Foundation.

Administered by:

Server stats:

251
active users

en.osm.town: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#softwareengineering

14 posts12 participants1 post today
Public
PyCon UK

🚨 Tick-tock, tick-tock... the countdown is ON! 🚨

There's less than 2 weeks until the #PyConUK2025 CfP closes! 🗓️

Got an idea for a talk, workshop or Young Coders' event? Share it! 🎤🚀

Not sure how? We've got a whole bunch of info and advice for you here:
👉 2025.pyconuk.org/call-for-prop
👉 2025.pyconuk.org/2025/03/encou

If you've got knowledge and experience that our community would benefit from hearing, don't keep it to yourself! 📣

2025.pyconuk.orgCall for Proposals – PyCon UK 2025PyCon UK Friday 19th September to Monday 22nd September 2025, CONTACT Manchester
#Python#CfP#CallForProposals
Public *
Jack Atkinson

I upgraded archeryutils to use #numpy #typing more 'properly'.
I found the docs and other sources challenging when it came to implementation and examples, so here are my observations and an #ELI5 summary of the bits I felt were missing in the hope it might help others: jackatkinson.net/post/numpy_ty

Comments welcome.
#Python #SoftwareEngineering

Jack Atkinson's Website · Typing in numpyI recently updated my archeryutils package to use numpy typing ‘properly’. Whilst I was already using type checking, it was in a non-ideal fashion for numpy due to a lack of experience/understanding when originally writing the code. I also find the numpy typing documentation hard to read when it comes to practical implementation, so summarise what I found here.
Public
Yuna

🎭 NATS: When Your Digital Child Becomes the Prize in a Custody Battle

Reminder to all companies:
If you build your empire on open-source and contribute nothing back, don't be surprised when the ground starts cracking.

NATS, one of the few messaging systems that actually works without summoning ancient demons, now finds itself torn between its creators at Synadia and its adoptive guardians at CNCF. Like any good custody battle, it’s about one thing: Money. 🤑

As a tiny contributor to NATS, it fills me with childlike glee and existential dread to witness what happens when open source ideals collide headfirst with cold, hard business reality.
It’s a classic story:
A vendor generously donates an open-source jewel… only to demand it back when the math stops adding up.

Synadia, the ever-devoted parent, wants to put NATS under the Business Source License (BSL) to secure its survival. Meanwhile, CNCF holds the project in a loving but legally fortified embrace, refusing to let go.

CNCF, clutching its righteous torch of community ownership, refuses to hand over the toys, reminding Synadia: “You gave it away. There are rules. Also… you signed things.”

As a microscopic speck in this universe of giants, I have one simple emotion: sadness.
Sadness that the best technology can still be crushed under the weight of human greed, misaligned incentives, and tragic irony.

OSS survives because we believe in it. OSS dies when we monetize belief.

Whatever happens, little NATS deserves better than a lawsuit. It deserves a future.

Will I stop contributing to NATS?
No. I'm far too stubborn for that.
Will I trust it the same way?
Ask me again when the lawsuits stop.

⚡ Still contributing. Still dreaming. Still worried.

Sources:
* cncf.io: cncf.io/blog/2025/04/24/protec
* thestack: thestack.technology/we-want-it
* Nats.io: github.com/cncf/foundation/blo
#opensource #natsio #cncf #synadia #foss #techdrama #softwareengineering #NATS #OSS #BusinessSourceLicense #DeveloperLife #SupportOSS #coding #programming

Parents called Synadia and CNCF are fighting for their child Nats.io
Public *
Mark Gardner
Bad vibes, man: https://TheRegister.com/2025/04/12/ai_code_suggestions_sabotage_supply_chain/

#LLM-powered code generation tools can introduce #security risks into the software supply chain by suggesting non-existent software packages, which can be exploited by malicious actors to create typosquatted packages.

#AI #VibeCoding #coding #programming #SoftwareEngineering #InfoSec
The Register · LLMs can't stop making up software dependencies and sabotaging everythingBy Thomas Claburn
#infosec
Public
Dr. Leon Kums
Why We Rewrote All Our Rust Code in Perl and Raku at SBI — And Why It Worked

In a bold move that raised more than a few eyebrows, Dr. K, our visionary CEO at SBI, led the initiative to rewrite all of our Rust codebase in Perl 🐪 and Raku 🦋. Yes, you read that right — Rust 🦀 out, Perl and Raku in.

What seemed unconventional at first turned out to be one of the most strategically sound decisions we’ve made:

Unparalleled Expressiveness ✨: Raku’s powerful syntax and Perl’s mature libraries gave our teams the agility to iterate faster and express complex logic with clarity.

Developer Productivity ⚡: Our engineers experienced a significant boost in productivity. Fewer lines of code, less boilerplate, and highly flexible scripting accelerated both prototyping and deployment.

Legacy Interoperability 🏛️: Perl's vast ecosystem allowed seamless integration with legacy systems, saving us months of re-engineering work.

Community & Support 🤝: While not as trendy, the Perl and Raku communities provided deep, battle-tested solutions to problems we faced.

This wasn’t just about tech—it was about culture. Dr. K reminded us that innovation doesn’t always mean following the newest trend; sometimes it means re-examining the tools we overlook and discovering new potential in them.

The results? ✅ More stable code, ✅ happier devs, and ✅ improved time to market.

Curious about how we made the transition? Let’s connect — I’d love to share what we learned.

#TechLeadership #SoftwareEngineering #Perl #Raku #Innovation #Rust #SBI #EngineeringCulture
#engineeringculture
Public
Kerfuffle

I have now encountered several cases of unintelligible documentation - functional requirements, security measures, technical how-tos - where I had to ask the author for clarification, and getting as a reply "oh I don't know; I just asked #ChatGPT".

Now I can bash #ai tools, but people who produce documentation that they themselves don't understand have always been a blight on #IT. It's irresponsible, unprofessional, and makes work harder for everyone.

#dev#SoftwareEngineering
ExploreLive feeds
About