software-development VS Iosevka

The thought feels weird, but DHH is not the first one to utter it.

A recent HN submission [0] links to a post in a series about reducing development friction. I do recommend reading the whole thing, but one post is specifically about not using CI [1].

0 - https://news.ycombinator.com/item?id=38831991

1 - https://github.com/aaronjensen/software-development/blob/mas...

Totally agree that it has lost its meaning. We call things “incomplete work” that are, well, incomplete work.

https://github.com/aaronjensen/software-development/blob/mas...

sbellware may have more to add, but there isn't a name for it. We focus more on the "it" than the branding of it. We do use the word "continuity" to describe our goal: https://github.com/aaronjensen/software-development/blob/mas...

> The words "equipment log" and "work product" sound pretty unique.

We call them "material logs", as equipment logs are more or less a subset of those. Just think about the sheet in every bathroom at a store that says when it was last cleaned, or the clipboard attached to the factory machine that lists its maintenance record and problems. Or the patient record outside of the patient's door.

"work product" just means, the product of our work. Nothing special about that one, I don't think.

> Are Erl's SOA books and Yourdon's on OOP still relevant?

I haven't read either, personally, though I have Yourdon's book en route. We use the term "structural design" quite a bit, so I'm curious to see Yourdon's take on what they call "structured design". From everything I've read about it, it sounds very similar to a lot of how we think about things as it seems to be the basis for much of the coupling and cohesion thought in our industry.

I'd also recommend studying Lean (not Lean Startup, which has much to do with Lean as non-fat yogurt does).

There’s another way that feels totally unnatural at first, but puts the subject (the most important part) of the commit message first. It makes the commit about the change and the code, rather than the author. This is how we do it in all of our projects. I fought it at first, but I was wrong and it’s a lot better.

Example:

EntityStore build method records the specifier argument when given

Article about it: https://github.com/aaronjensen/software-development/blob/mas...

> 80 should be fine for most single lines of good code in most languages.

C++ with even a modest template will flow over 80 without much effort.

I'm now using the condensed width font Iosevka font [1] with 160 chars as my max width in clang-format and indents at 1.

After a few days of using it, I'm converted. It was a bit odd looking at first, but I guess that's brain plasticity at work.

1. https://github.com/be5invis/Iosevka/releases

iosevka

https://github.com/be5invis/Iosevka is the best

Sadly I think that because of that flag it does not enable ligatures.

I was able to see ligatures and text healing in vim running in a patched st* though. I really like it thanks! The text healing only moves the line subtly as I type and when I cursor over there are no droppings from the widened 'm' for example. It's well thought-out for code.

If I could ask for a feature it would be to select some variants, like angular 0 with reverse slash or to leave the ! in the != ligature. To see what I mean: https://github.com/be5invis/Iosevka/blob/main/doc/stylistic-...

* https://st.suckless.org/patches/ligatures/

Iosevka is a fantastic open-source font that's fully customizable. I have replaced the fixed font on all of my devices and apps to a custom Iosevka build I made, and I don't think I'll ever turn back.

https://github.com/be5invis/Iosevka

Misremembered about Iosevka: I requested support for a few other BQN characters after noticing it already had the double-struck ones (https://github.com/be5invis/Iosevka/issues/870). The other three were requests or contributions (drew 3270's 𝕏 myself!) explicitly in connection with BQN.

Nothing beats Iosevka (https://github.com/be5invis/Iosevka) for me. It's narrow yet super readable, making great use of screen real estate. Lots of customization, ligatures, weights, and a nerd font patch for terminal.

> Monospace Iosevka contains various stylistic sets to change the shape of certain characters

That's what's on display at the linked URL (if anyone else was confused)

You can also select variants for specific characters: https://github.com/be5invis/Iosevka/blob/main/doc/character-...