Sijmen Mulder

@sjmulder@bsd.network
241 Followers
208 Following
519 Posts

Programmer. Likes Unix in its various modern incarnations. NetBSD (pkgsrc) developer

#C #pgksrc #NetBSD

Dutch and more about non-tech: @sjmulder

wwwhttps://sjmulder.nl
codeberghttps://codeberg.org/sjmulder
githubhttps://github.com/sjmulder

I got laid off today. Eek!

Looking to hire a senior/staff engineer? I might be exactly what you need.

Keywords: backend / Ruby / Ruby on Rails / Go (Golang) / AWS / Terraform / frontend / Type­Script / React / full-time / remote-first / senior engineer

Some more details on what I offer here: https://denisdefreyne.com/notes/get-me-a-job-2025/

repost = ❤️

#GetFediHired #Ruby

Get me a job in 2025

A note written by Denis

denisdefreyne.com
🤖 AI slop is flooding open source bug bounty programs.
Now #curl and @django are fighting back. Both have published new policies to curb slop security reports.
Full story → https://socket.dev/blog/django-joins-curl-in-pushing-back-on-ai-slop-security-reports #OpenSource #Django @bagder

The final two presentations by Shirley Tarboton and @bert_hubert were nice complementary talks about respectively energy usage caused by our software development methods and actually inefficient software.

Bert had some seriously impressive graphs and examples on 1000x gains that can be made by focusing on making one's software more efficient.

#JoyOfCoding #JoyOfCoding2025

Finally 😍 but there is a problem

#DeathStranding2 #PlayStation5

When a site makes you complete a captcha to prove you are not a bot and then the article is written by one 🤐

We often talk about the scouting rule of “always leave the campsite cleaner than you found it”, or in a software context “always leave the code a little bit better than you found it”.

If you see duplication in the code, then remove that before you leave the method. If you see poor variable names then fix those before you leave.

What we don’t talk about as much is how a culture of branching and Pull Requests (PR’s) actively discourages making small changes for that purpose. If I want to rename a method to make it clearer and know that making that little change is going to require real effort to go through a review process and manual merges, then I’m more likely to decide to just live with the original name, even if it is is poor.

Whereas if I can make that little refactoring and directly check it into mainline then it’s a very low effort change that contributes to the quality of the product. It’s become easy to do the right thing.

How many things do we have like this, that actively discourage us from doing the right thing?

First time seriously using JetBrains Rider on my Fedora KDE Plasma system, and unfortunately not a good experience:

- Very bad font rendering on my mixed-DPI set up. Looks like glyphs are antialiased first, then scaled

- The IDE keeps getting in the way, autocompleting things without explicit intent, stuff that I then have to remove again. All configurable but it's a chore and annoying.

- What appear to be CPU spikes, and ballooning memory usage. Video started stuttering in my browser, eventually the system locked up until the kernel decided to kill the IDE worker process.

#JetBrains #Rider #Wayland

Typing is easy, naming an alias is hard

find . -name Makefile | xargs grep sjmulder | cut -d/ -f2 | sort -u | xargs tig

Seed7 Homepage

Seed7 - The extensible programming language

oh the irony