The story of #Gradle

https://youtu.be/UuD00hoe-Yo?si=neokHZKXb4_Kty6t

Two often-overlooked Python string methods are startswith() and removeprefix(). @treyhunner covered them with nice examples. Remembering these can help you write cleaner and more readable code.

https://www.pythonmorsels.com/prefixes-and-suffixes/

Question for any software developers who use AI code generation tools (Cursor, Github Copilot etc). I know that some devs like it, while some find it irritating. That's fine.

However, I'm curious: what - if any - rules has your organisation put around the usage of these tools - more testing, stricter code reviews, more documentation? Something else? Nothing at all (since ultimately the developer is responsible)?

I really have to write a #blog post titled "I hate rebase-merge workflows"

Making fun of #AI's mistakes to make yourself feel smart is the new making fun of juniors' mistakes to make yourself feel smart.

I liked Objective-C’s YES and NO, while simultaneously acknowledging the only reason it probably existed was every other possible boolean was already used by some other thing in C/C++. #SoftwareDevelopment

The biggest bottlenecks in the software lifecycle have nothing to do with code. They’re people problems: communication, persuasion, decision-making.

How do you reliably get the right people in the right place, at the right time, talking about the right things? Is there a transfer protocol or infrastructure-as-code tool that works on human beings?

As it happens, yes.

My latest byline:

https://stackoverflow.blog/2025/08/20/documents-the-architect-s-programming-language

Our very first post here!

We are JDriven, a team of software engineers and consultants from the Netherlands.

Expect updates on our blogs and events, always with a focus on software craftsmanship and knowledge sharing.

Happy to be part of this community!

Lisp in 99 Lines of C With TinyLisp - As one of the oldest programming languages still in common use today, and essentia... - https://hackaday.com/2025/08/19/lisp-in-99-lines-of-c-with-tinylisp/ #softwaredevelopment #lisp

My latest blog post discusses how divergent thinking can open up better solutions and save you from wasted effort.

https://henko.net/blog/why-divergent-thinking-leads-to-better-software/

Oh I'm now exploring new local R&D tech related projects btw! Share around to anyone who may be looking for an oldie 20yr polygot engineer, product manager, and unabashed team cheerleader. Bonus if it involves AI applied in novel ways to new domains.

Simple Techniques, Applied Consistently

https://videos.devteams.at/w/rN5KRLwkAycaGaFaU4Txnm

"API documentation writers don’t just write content. We’re liaisons between client developers and in-house developers. I often say “we’re paid by the company but work for our clients.” Many think that in-house developers automatically empathize with the client developers. After all, they’re all developers, right? Right? Well, no. A surprising number of times, in-house developers are actually out of touch with clients. Why else would we be talking about having clear field names? They get tunnel vision or become myopic while in the code. This is not unique to developers. All professions have this risk. That’s our job to make sure that clarity is there for the clients. We can’t do it completely by ourselves. We need developer’s buy in. That means, one of two things.

We can push back on the in-house developers. When we see a meaningless, poor, or bad field names, for example, we have the right, if not obligation, to get it changed. Some developers may disagree. That’s OK. The truth is, the code doesn’t belong exclusively to in-house developers. It’s the client’s code. They’re the ones intended to run the code, to know which fields to pass in, with which values, and to read the response JSON. That makes it our code, too. We not only have to run the code but also to explain this to clients. We have a say in the matter."

https://robertdelwood.medium.com/writing-for-humans-an-api-documentation-writer-writes-3c51a6ea87a5

The legacy code struggle is real: https://mastodon.cloud/@jasongorman/115037036868661424

Watch my personal #FrOSCon retrospective!

https://youtu.be/E75lYd4tK0Y

I updated my post "Do I need a Lisp Machine comeback?". I have added the new information I've found with chatting with folks on lisp IRC channels.

https://far.chickenkiller.com/computing/do-i-need-a-lisp-machine-comeback/

Seems like I was looking for was "residential style development" or something. Dunno yet what does it mean. But for sure I am digging something out of grave!

hey community! this looks amazing!

FITS 2025
Feminist IT 2 the Sky

A whole day of feminist engagement with diverse IT topics, for FLINTA* folks, taking place at the TU Wien, on Saturday 27th September 2025.

The registration form will be linked here https://fits.diebin.at/ some time in the second half of August.

#wien #flinta* #IT #Coding #SoftwareDevelopment #Linux & #OpenSource #EthicalHacking

congrats to @diebin
Edit: praises to @jackie and others around the feminist linux meetup vienna!

This weekend’s "final boss" wasn’t in a video game—it was my #Perl build. Dist::Zilla and I stepped into the ring… and left as allies.

(No Pacific Rim cities were harmed in the making of this release.)

#programming #coding #SoftwareDevelopment #SoftwareEngineering

https://phoenixtrap.com/2025/08/17/kaiju-boss-battle-a-distzilla-journey-from-chaos-to-co-op/?utm_source=mastodon&utm_medium=jetpack_social

Recto: In Case Programming isn’t Hard Enough - There’s long been a push to stop writing code as a sequence of lines and go to som... - https://hackaday.com/2025/08/17/recto-in-case-programming-isnt-hard-enough/ #softwaredevelopment #visualprogramming #softwarehacks #lisp