Lately I've been dipping my toes into developing in Windows without WSL. To that end, I've found to be particularly nice for installing stuff.

Next, I should learn more about PowerShell and UWP.

you, weak: french press coffee
me, muscular and athletic: bench press coffee

🎉 Announcing: The PHP Foundation


ℹ️ More information at:

iOS Focus Mode is such a great feature. I couldn't go back to a world without one.

I've set up the work focus to only allow notifications from work-related apps and calls from family and coworkers*. Then there is the personal focus for evenings and weekends, which blocks work notifications and allows only family calls. Finally, the sleep focus mutes everything while also handling scheduled alarms.

*) repeated calls are allowed

The Bad Guys continue to win while the Good Guys are off in a corner distracting themselves by bickering about whether it’s problematic to use the phrase “Good Guys”.

FOSSbros being shitty 

I am not a programmer. Despite that, I tried to contribute to an open source project. Big fucking mistake.

Despite making it clear multiple times that this is not My Thing™️, the dude reviewing my PR kept just, skirting around just calling me a fucking idiot. Started saying shit like "stop and learn what a force push is" and "at this point might as well revert everything" and posting screenshots of my commits 🙃

Ended up closing the PR and deleting the branch, as well as crying for a little bit afterwards. Fucking hell why did I ever think this was a good idea

The Fediverse is not an Endlager for your Tweets! 

Autoposts from the birdsite are problematic and may even violate your home instance's guidelines.

- short/tracking URLs
- usernames not/existing in both universes or who are different persons cause confusion
- RTs clutter local/federated timelines
- responses aren't read preventing discussion

- no use of
- content warnings (CWs) for peace of mind
- image descriptions for accessibility
- public/unlisted/followers/direct addressing


If you first pour the liquid metal on a surface and then try to mould it for the desired outcome, you'll burn your hands and end up with something completely different from what you designed.

Show thread

Writing code is like producing steel: you create the mould (tests) first, then pour the liquid metal (implementation) into the mould.

Show thread

For me, this was a great revelation when I was learning .

There are so many obstacles preventing you from writing untestable code, and that's a good thing.

Show thread

With test-driven development, the whole situation gets flipped upside down.

If I now try to write code to make the test pass and find it difficult, it's an obvious sign that I need to take my ideas back to the design board. This saves me precious time as I have likely uncovered a design flaw or a defect early on in the process.

Fixing it now is faster and cheaper as opposed to fixing it after release.

Show thread

When I work the "usual way", I write my automated tests after the production code, which often feels difficult. I tend to judge that it's impossible to write a good test for this particular code. Thus, I skip writing the test.

In this initial version of my software lifecycle guide, I focus on automated tests and documentation. I reserve the liberty to update this guide later.

You can do it too by sending me a pull request via GitHub.

Show thread
Show older
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!