Show newer

Twitter announces "Blue", a subscription service for a monthly fee, that unlocks a bunch of extra features.

Editing tweets is among them apparently.

Why that is a horrible idea:

Day five of not using my phone: I have read five books and written twelve. I now perfectly understand what Hegel was going off about. I have learned to astral project

Craftsman's Log – 2021.05.30

Keywords: journaling, pair programming, product teams, zines, theory of constraints, productivity, and simplicity.

A reminder that we probably should stop recommending Clean Code (Martin, 2009)…

…and recommend The Clean Coder (Martin, 2011) instead.

Or if Bob's not your uncle, try reading the following for starters:

– Extreme Programming Explained, 2nd Edition (Beck, 2004)
– Software Craftsman (Mancuso, 2014)

Me 13 years old: yay, summer vacation!

Me 33 years old: yay, summer vaccination!

It's not often that I read the macOS system.log. It's written in an interesting tone, polite yet informal and to-the-point.

Pair programming is about mentoring, learning, sharing knowledge, and building social connections. Pair programming is also exhausting, makes you vulnerable, and is often looked down on by managers. Fortunately, through practice and repetition, you can make it work for you.

Read about benefits, pitfalls and practical tips for pairing in my latest blog post.

It turns out, medieval people knew quite a lot about software development. Scope creep and rushing features to production while sacrificing quality was not unknown to them.

Picture from the Book of Job, ca. 1330.

If it involves a couple of hacky tricks, I don't care if your code solves the problem 6% faster.

Hardware scales and will improve over time. The human capacity of understanding and maintaining code does not.

There are always exceptions to the rule, but generally speaking:

clean code > performance.

When the iPhone launched, all the cool apps were on the desktop, and you had to live with shitty web apps on your mobile.

Nowadays all the cool apps are on the mobiles, and you get shitty web apps for the desktop.

“How Apple screwed Facebook - Apple’s iOS 14.5 update has triggered an unstoppable collapse in Facebook’s ability to collect user data”


A good solution is to work in the smallest possible batches and leverage pair-programming. There is no better way to improve the code review process than to review the single line right after it has been written.

Each change should process like so:

Write code – review – test – commit – continue

Couple the approach with test-driven development where it makes sense.

Show thread

We are taught to use pull requests to guard us against unwanted changes. It (sort of) works in open-source development given you have ample time to review.

In business projects, it works the other way around. We are over-worked and over-utilized to the point we don't care about code reviews and easily let any change through. After all, we're always behind schedule.

Show thread

I noticed this pull request in my inbox today. The author states in the title they are refactoring a feature.

This is the best example of how you can smuggle any change you want into a codebase. All you need is to surround it with a diff of several thousand lines.

"I could rewrite curl" - Collected quotes and snippets from people publicly sneezing off or belittling what curl is

Standard Ebooks is a volunteer-driven project that produces new editions of public domain ebooks that are lovingly formatted, open source, free of copyright restrictions, and free of cost


#technology #opensource #ebooks #reading #nodrm

Most of the time, that helpful metadata attached to the logging event (JSON objects and something) are either total garbage, undefined, or strings of "[object Object]".

Show thread

The best thing while implementing error logging into your application is to think:

"This little edge case will only hit me rarely, but better to log it anyway. 😇"

Narrator: "It hurled CloudWatch alerts at your direction ~100 events per minute. 👹"

Always log your errors and see how they scale.

I still can't get over the soundtrack of Once Upon a Time in Hollywood. While the songs themselves are not the best of the 1960s, we should remember the album among the best attempts to capture the decade's spirit (similar to Mad Men) with all its cheesy KHJ tunes.

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!