Show newer

I'm compiling a collection of software engineering principles. The idea is to have them in a document with longer explanations and examples. Other than that, they're meant to be cited as justifications for this or that choice we make and left as comments in code or in conversations. Some are special cases or consequences of more generic principles. Here's what I have so far:
- simplicity
- least surprise
- separation of concerns
- design for the worst-case scenario
- explain the intentions behind any piece of code
- minimize future maintenance efforts
- minimize time to fix future problems
- no code duplication
- fail early

Note that this list is limited to "technical" principles in the sense that they're valid even for a team of one. There are more principles and guidelines for the interactions between team members but here I'm limiting myself to what could be or should be written down as part of a code base.

*my interpretation assumes a continuously ascending path from the imaginary sea level to the mountain top. I believe it's almost always the case in practice.

A counterexample is a peak within a crater.

Show thread

I find the definition of the prominence of a mountain peak very interesting:

"The prominence of a peak is the minimum height of climb to the summit on any route from a higher peak, or from sea level if there is no higher peak. The lowest point on that route is the col."

It's the peak's height minus how much the sea level would have to rise to make this peak the highest on its island.

For intuition, see the examples at en.wikipedia.org/wiki/List_of_

Does anyone understand what Elton John says in the song Sacrifice? It sounds like a made-up tongue to me except for a few phrases here and there.
youtube.com/watch?v=NrLkTZrPZA

Years ago, I was in a web company whose business was people search. The biggest takeaway from this particular industry is that people love to find details about others but hate to have their details available to others.

Xu Hongming exhibit at Qualia in Palo Alto. I recommend seeing this in person if you have a chance. It's huge.

@dragonarchitect interesting. I've been doing surprisingly ok in California with only knowing this incomplete and approximate table:
32°F = 0°C (freezing)
70°F =~ 20°C (human-friendly)
100°F =~ 37°C (body)
(212°F) = 100°C (boiling)
350°F = (175°C) (oven)

The values in parentheses are those I had to look up for this post.

Don't read my toots if you're easily offended. My favorite American comedy is Ghost World (2001).

Tony Hawk: I'd like to turn myself in for murder.

Cop: Are you Tony Hawk?

Tony Hawk: Yes.

Cop: If you're Tony Hawk where's your skateboard?

Tony Hawk, holding up a blood-soaked skateboard: It dug right into his skull. I am a monster

Cop: You look a little old to be Tony Hawk

And Jesus said: "Let's block whole online communities in the name of tolerance. That will teach them m***********s."

<video of a guy who raised a baby bass in increasingly large aquariums>

Commenter: It's time to release Gerald* back into the wild where he belongs!
Me: Why don't you release your kids?
Commenter: I don't have kids.
Me: Good for them!

*his real name was changed to protect his privacy

Réponse de la devinette 

Dans une bouteille de Klein !

Show thread

Une devinette que nous envoie René D.:
J'y pisse donc j'y suis. Où suis-je ?

Seriously.

- What does it mean to be intentional with your work?
- It's to show that you're in control. It's an essential component of macho culture.

Show older
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.